Member Avatar for steverino365

My DSL Westell 6100 modem is connected to the DSL line using PPPoE and works great as long as I connect directly to the modem via ethernet cable plugged into my PC.

I want to connect a Linksys WRT45SG wireless router to the DSL Modem to create a hotspot. Using the Linksys default setting does not provide connectivity, even after resetting the boxes.

My question is - do I need to command the DSL modem to manually disconnect the PPPoE connection, then use the PPPoE function in the LinkSys router to get the router to connect to the DSL line? Is there a simpler way?

  • 3 Contributors
  • 4 Replies
  • 537 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by techsheaven

Dani AI

Generated

described a Westell 6100 using PPPoE that works when a PC is plugged straight in; adding a Linksys WRT45SG failed. and made useful points. The note below adds practical diagnostics and low-risk fixes that clarify which device should terminate PPPoE, how to detect IP overlap, and a few gotchas that commonly block connectivity.

Begin with a short diagnostic sequence: connect a PC to the Westell and run ipconfig /all (Windows) or check the interface IP on the PC — a public (non‑RFC1918) address usually means the modem is passing the PPPoE session; a 192.168.x/10.x/172.16.x address means the modem is already routing/NATing. Then connect the Linksys and examine its WAN status page: a public WAN IP shows the router successfully got a PPPoE lease; a private 192.168.x WAN IP shows it is behind the modem. If PPPoE authentication fails, re‑check credentials, try the Linksys "MAC Clone" option, and use the power‑cycle order below to clear any MAC‑bound session.

Practical setup alternatives and consequences: make the Westell pure bridge/pass‑through and configure PPPoE on the Linksys for a single NAT and straightforward port forwarding; or keep the Westell as router and convert the Linksys into an access point (disable DHCP, connect via a LAN port, and assign it an unused management IP on a different subnet) to avoid overlap and double NAT. If both devices must route, move the Linksys LAN to a different subnet (for example 192.168.2.1) or place the Linksys WAN in the Westell DMZ so services work predictably.

Final cautions and tips: use this power sequence — power off both devices, connect the router, power on the modem and wait for sync, then power the router — to ensure the modem hands the session to the router. Some ISPs bind PPPoE to the first device MAC, so cloning or a modem power cycle may be required. Avoid running two DHCP servers on the same subnet and check the Linksys WAN IP and the Westell status page when verifying success.

Recommended Answers

All 4 Replies

Member Avatar for JorgeM

My question is - do I need to command the DSL modem to manually disconnect the PPPoE connection, then use the PPPoE function in the LinkSys router to get the router to connect to the DSL line? Is there a simpler way?

You cannot have both devices trying to establish the PPPoE connection at the same time. The easiest way is to have the router connect via PPPoE. configure the settings on the router. Disconnect from the modem.

Member Avatar for steverino365

Thanks for the quick answer - will try this tomorrow. I was not sure about changing the DSL modem connect state but this is a simple test. I will connect to the DSL modem at 192.168.1.1 then go to the connection page and select disconnect from the internet. Then I will plug the Linksys router into the DSL modem and power it up. The Linksys router will be preset to auto-connect using PPPoE with the DSL user/passwd. Does this sound correct?

Member Avatar for JorgeM

Sounds like that should work as long as your modem is acting like a bridge, no routing.

Member Avatar for techsheaven

You simply have an IP conflict; both devices are on 192.168.1.1. Just change one device to 192.168.1.2, and your conflict will be gone. You need to have one of the devices correctly authenticate, or you will have intemittent/no sync issues!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.