The simplest and cheapest method of accessing the modem GUI through a router is explained here: »Ameritech - SBC FAQ »Modem GUI access thru a router ; however, sometimes there can be disadvantages to allowing the modem to make the PPPoE connection such as problems with some on-line games or P2P traffic.
An alternate method of accessing the modem's GUI when a router makes the PPPoE connection can be set up by inserting an inexpensive five-port switch (or hub) between the modem and the router. This works because the PPPoE-encapsulated traffic "tunnels" directly from the router through the switch to the modem without problems, but any other non-PPPoE-encapsulated traffic on the the 192.168.0.x subnet will be directed by the switch to the modem's GUI. Note: That this arrangement with appropriate IP adjustments can also be used for modem models other than the 5100b/4100.
So what other type of ethernet connections can be made to the switch to access the modem?:
Method 1: A computer off the LAN and dedicated to the collection of modem stats could be set up.
Method 2: A computer on the LAN, but with a second NIC set to the 192.168.0.x subnet could be connected to the switch.
Method 3: A second router in parallel with the primary router that bridges the 192.168.0.1 traffic.
This secondary router can be an old unused unit or it could be a wireless router that also adds wireless connectivity to the LAN. Both routers are assigned IPs on a subnet that isn't 192.168.0.x or 192.168.1.x. The DHCP function on the second router must be disabled. A patch cable connects a LAN port on the primary router with a LAN port on the secondary router.
In the following diagram, the primary router is set to make the PPPoE connection. The secondary router should be set to "Obtain an IP automatically" if the modem is in "PPP on the computer" mode or set to the static IP of 192.168.1.64 as per this FAQ: »Ameritech - SBC FAQ »Modem GUI access thru a router if the modem is in the "Bridged Mode".
From the command prompt, you must then run the following command for each LAN computer that is to access the modem GUI:
route -p add 192.168.0.1 mask 255.255.255.255 A.B.C.Y metric 5
The "-p" option make this routing persistent even after a computer reboot. The A.B.C.Y IP is the secondary router's IP. This command line could also be placed in a BAT file to be run as necessary.
The command: route delete 192.168.0.1 will erase the routing from the computer permanently if needed.
The background for this portion of the FAQ was derived from the discussions in this thread: »Viewing Modem Stats? Thanks to Bill_MI  for the router set up details.
Method 4: A connection from the router's switch to the five-port switch without the secondary bridging router.
The router is set to make the PPPoE connection. A patch cable connects a LAN port on the router with a port on the five-port switch. The computer's NIC is set to a wider mask than the typical 255.255.255.0 mask. The diagram shows it set to 255.255.0.0, but this could be restricted to 255.255.252.0 if there is some need to do so such as to allow connections through a VPN to other 192.168.x.x subnets.
Note: This method should only be used with static IPs on the LAN or with the modem in the bridged setting. Unintended routing results occur if the router is set up as a DHCP server without bridging the modem. For example, a DHCP client device on the LAN will end up with the 192.168.1.64 address issued by the modem's DHCP server.
Although this method requires less equipment than the other methods, it does produce slightly more traffic activity on the LAN. All the LEDs on all the equipment that show ethernet activity will blink simultaneously and the router logs might show false "intrusion" attempts on the WAN from the computer and modem broadcast traffic.
The method was modified from the discussions in this thread: »switching to dslextreme - question on setup. Thanks to sded for the ideas.
 feedback form
 feedback form
by d_l
last modified: 2008-05-10 09:14:17 |
