Router - EchoLife HG612: Difference between revisions
Appearance
Content deleted Content added
| Line 102: | Line 102: | ||
* Connect a cable between the LAN2 port on the HG612 and your LAN switch (or an unused LAN port on your router). |
* Connect a cable between the LAN2 port on the HG612 and your LAN switch (or an unused LAN port on your router). |
||
* You should now be able to access the HG612 from any device on your LAN by visiting http://192.168.1.2 |
* You should now be able to access the HG612 from any device on your LAN by visiting http://192.168.1.2 |
||
| ⚫ | |||
| ⚫ | |||
* In your router, configure the WAN interface with a private (RFC1918) address in a different subnet to your main LAN. e.g. if your main LAN is 192.168.1.0/24 then configure the WAN interface with the address 192.168.2.1/24 |
* In your router, configure the WAN interface with a private (RFC1918) address in a different subnet to your main LAN. e.g. if your main LAN is 192.168.1.0/24 then configure the WAN interface with the address 192.168.2.1/24 |
||
* Change the HG612's IP address (under "Basic -> "LAN" in the web interface) to be any address in that second subnet - e.g. 192.168.2.2/24 |
* Change the HG612's IP address (under "Basic -> "LAN" in the web interface) to be any address in that second subnet - e.g. 192.168.2.2/24 |
||
* Under "Basic -> WAN" on the HG612, ensure both "Port binding:" checkboxes are unticked and press the Submit button to save the |
* Under "Basic -> WAN" on the HG612, ensure both "Port binding:" checkboxes are unticked and press the Submit button to save the |
||
change. This step enables LAN access via LAN1. |
change. This step enables LAN access via LAN1. |
||
* At this point, your router knows where to send packets from devices on your main LAN to the HG612, but the HG612 doesn't know where to route responses (it can't be configured to have a default route via your router). |
* At this point, your router knows where to send packets from devices on your main LAN to the HG612, but the HG612 doesn't know where to route responses (it can't be configured to have a default route via your router). |
||