Mountaineer1
Big WVU Fan
Premium,MVM
join:2002-01-12
Universe
 ·AT&T Yahoo
2 edits | reply to Eleo
Re: Problems with WRT54G v6, lost connection.
This gives you access to the GUI of the modem,through the router »/faq/amfaq/2.2···em#12670 and from this FAQ I quote" NOTE:192.168.1.64 is a private IP address that leads one to believe some NAT / NAPT is used. But this private IP address is as open to the internet just like a public IP address is. The modem will perform NAT / NAPT on any other 192.168.X.X IP address." Also when the WAN and LAN share the same IP address range,this will confuse the router's NAT logic. Most of the time,the router will freeze-up,and the only way to get it working again is to powercycle the router.
--
I'm just a Material Handling Tech.If it's too heavy,get a Forklift. |
|
Eleo
join:2004-06-28
Cleveland, OH
| reply to Mountaineer1
Mtneeer, I'm wondering, why is this way in particular necessary? I get why I would want PPPoE on the modem instead of the router, but the rest of the guide I don't understand.
Why can't the router have the real IP address (instead of 192.168.1.64)? Why switch from 192.168.1.x to 192.168.2.x? By default the router assigns WAN IPs starting from 192.168.1.100, so it shouldn't collide with the 192.168.1.64 IP of the router. Why "Use Static IP Address" when it seems like "Automatic configuration - DHCP" accomplishes the same ends? But my biggest question is how/why your setup prevents disconnects...
I have it set up differently and am wondering if my setup messes stuff up. |
|
