said by tpanc13:About 3 weeks ago I installed Yahoo DSL ISP with Speedstreem 5100 modem. All went well.
About 2 weeks ago I installed Home Network for the first time using a LINKSYS BEFW11S4. It took a while, but all worked and the host and client PCs could both get to Internet. At this time the 5100 modem Lights that were solid green included Ethernet, DSL, AND Internet.
However, I have been having Internet Disconnect problems randomly, such as next day it wouldn't work, or sometimes during a session it would slow done and stop. After several searches through LINKSYS Forum, I implemented a fix that enabled PPPoE on the router. No problems in last 2 days so far.
BUT, I am using the Internet and the Speedstream Internet light is OFF. Yet, both host and client have access w/o problems. Today I thought I'd once again check Yahoo SBC account and tried to get to 192.168.0.1. It FAILED. Can also not PINH it. Yet, Internet works and Light is off.
Do I have a real problem or not?
When the router is initiating the PPPoE session, the packets are encapsulated for transport on the router; they will never reach the modem Ethernet port because they are no longer recognized as TCP packets. Also, you wont get a green Internet light on the modem because the modem is not running the PPPoE session.
I have an SS4100, which is supposedly equivalent in function to the SS5100B. I have tested my modem three ways; all three work.
I tried "PPP is on the modem, use private IP address." I then set the router (Netgear FR114P) to use a static IP address on the WAN port. I set up the router ports as:
IP address - 192.168.1.1
Subnet mask - 255.255.0.0
DNS server - 192.168.0.1
The LAN port is:
IP address - 192.168.102.1
Subnet mask - 255.255.255.0
Gateway - 192.168.0.1
DNS Server - 192.168.0.1
In this mode I could reach the modem by entering 192.168.0.1. However, all ports were "stealth" (with the computer requesting the probe in the DMZ; which should have shown the ports not blocked by SBC as "closed"), and the modem has no provision to forward specific ports for specific services. I would recommend this setting for Windows computers which are directly connected to the modem. I would not recommend this setting for routers connected to the modem.
Next I tried "PPP is on the modem, use private IP address". I then set the router WAN port to "obtain IP address from ISP". The router status page would then display:
IP address - 192.168.1.64
Subnet mask - 255.255.0.0
DNS server - 192.168.0.1
The LAN port is:
IP address - 192.168.102.1
Subnet mask - 255.255.255.0
Gateway - 192.168.0.1
DNS Server - 192.168.01
In this mode I could reach the modem by entering 192.168.0.1. With the computer requesting a port probe in the DMZ, those ports not blocked by SBC show up as "closed". This mode should be fine for a router connection; indeed, if you have any thought to use port forwarding, this mode is necessary. I don't recommend this mode for connecting a Windows computer because it does not have the benefit of NAT blocking of unsolicited packets; it is the DMZ for the router hidden within the modem.
Last I set up the modem for "PPP is on the modem, use public IP address." I then set the router WAN port to "obtain IP address from ISP". The router status page would then display:
IP address - nnn.nnn.x.xx
Subnet mask - 255.255.0.0
DNS server - 192.168.0.1
The LAN port is:
IP address - 192.168.102.1
Subnet mask - 255.255.255.0
Gateway - 192.168.0.1
DNS Server - 192.168.01
This is the method that I am using; it is the factory default setting for the modem. As with "PPP is on the modem, use private IP address", with the modem's DHCP assigned private IP address, this should be fine for a router. Again, with the computer requesting a port probe in the DMZ, those ports not blocked by SBC show up as "closed"; so I don't recommend this mode for connecting a Windows computer because it does not have the benefit of NAT blocking of unsolicited packets.
The distinction of the subnet mask is important; the subnet mask on the LAN side
must be larger (more contiguous MSB (Most Significant Bits) set), or the router will think that the IP address is on the local segment, and it will not pass packets to the WAN.
Other important points:
The modem should be set to either "Smart keep alive" (for a router connection), or "Always attempt to connect" (for either a router, or a directly connected Windows computer).
If you have an Ethernet adapter which responds to power management by shutting down, disable this feature.
If the router has a setting for always staying connected, use it. This can be an explicit "stay alive" setting, or it may be a specified period of time, with some specific period designated for the function.
For the LAN IP address, I did use 192.168.102.1 for the router, with subnet mask 255.255.255.0. I have an unrelated reason for this; any decimal value from '1' to '255' should work in place of '102'.
I have tested the three configurations, and all allow Internet access to the computers behind the router, and also allow connection to the modem at 192.168.0.1 through the router.