Router - EchoLife HG612: Difference between revisions

* Change the HG612's IP address (under "Basic -> LAN" in the web interface) to be an unused address on your LAN. e.g. if your LAN is 192.168.1.0/24, with your router using 192.168.1.1 you could change the HG612 to use 192.168.1.2.

* 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

A more elegant solution is to enable access to the HG612 over the existing connection between LAN1 and the WAN port on your router. This is done as follows:

* 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

* Under "Basic -> WAN" on the HG612, ensure both "Port binding:" checkboxes are unticked and press the Submit button to save the

* 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).

To fix this, we need to add a static route ("Advanced -> Routing" in the HG612's web interface) from the HG612 back to your main LAN. e.g. if your LAN is 192.168.1.0/24 and the router's WAN interface is 192.168.2.1 then you would create the following route:

Destination network address: 192.168.1.0 Subnet mask: 255.255.255.0 Default gateway: 192.168.2.1 (remember to also tick the checkbox) Interface: LAN/br0

You should now be able to access the HG612's web and telnet interfaces from any device on your LAN, over the WAN/LAN1 cable. Note that