What's new

WAN IP not passing through to Merlin FW on CenturyLink fiber

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

avrignaud

New Around Here
Hi folks,

Just dumped Comcast (yay!) and shifted over to CenturyLink's overpriced gigabit fiber (boo?). Previously on Comcast, I had no problems getting the cable modem's WAN address to be seen by the router. Once I changed to CenturyLink's modem, however, I have found that I am not getting a real WAN address, but instead an IP address from the modem's subnet.

The modem is at 192.168.0.1, with my router at 192.168.1.1. Problem is the router insists that the WAN address is 192.168.0.4 — and external access fails. I have also set the DMZ on the modem to point to 192.168.0.4, but that doesn't work either.

Screenshot snippet attached, showing the issue. Really appreciate any ideas anyone can share... slowly driving me insane!

AV
 

Attachments

  • Screenshot 2015-07-01 15.24.50.png
    Screenshot 2015-07-01 15.24.50.png
    78.7 KB · Views: 647
Your modem needs to be bridged, so that DHCP requests from the router are sent to the ISP.
 
Hi folks,

Just dumped Comcast (yay!) and shifted over to CenturyLink's overpriced gigabit fiber (boo?). Previously on Comcast, I had no problems getting the cable modem's WAN address to be seen by the router. Once I changed to CenturyLink's modem, however, I have found that I am not getting a real WAN address, but instead an IP address from the modem's subnet.

The modem is at 192.168.0.1, with my router at 192.168.1.1. Problem is the router insists that the WAN address is 192.168.0.4 — and external access fails. I have also set the DMZ on the modem to point to 192.168.0.4, but that doesn't work either.

Screenshot snippet attached, showing the issue. Really appreciate any ideas anyone can share... slowly driving me insane!

AV

Merlin is correct (of course); your modem needs to be put into bridge mode. You may be able to do this yourself via the modem's interface, or CenturyLink may have that locked down, making you have to call them to put it into bridge mode remotely.

However, you also seem to be confused about the IP addresses (forgive me if I am incorrect). Your WAN address is actually 192.168.0.4. It is getting that address via the DHCP server in the modem (putting the modem in bridge mode turns off the DHCP server in the modem and just lets the modem pass the real WAN IP to your router's WAN interface). Your modem's address is 192.168.0.1; have you tried putting that address into your browser to see if you can reach the modem's GUI? If you have tried this and you cannot reach it, it is likely because your LAN address range is in the same subnet as your modem (I may be wrong about my understanding/terminology of this - I am not an expert - I only know about this because I have run into the same issue). Try changing your router's IP to 10.0.0.1 and make sure your router's DHCP server updates to sending out IP's in the 10.0.0.2 - 10.0.0.254 range. Once you do that , try reaching the modem's GUI again at 192.168.0.1. I have a feeling it will work.
 
Hi folks, just wanted to respond back to say thanks. The issue was indeed that I needed to enable the "transparent bridge" option on the modem (located at 192.168.0.1), and then set the router to log in using PPPoE. Just had never hit this issue before, but Merlin's response and a bit of Googling got me up and going.

Thank you again!
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top