Wan 0.0.0.0 after working fine at old house



  • Hello, I'm sorry this is probably somewhere in the forum but without internet it's been difficult to find: I have been running a great pfsense setup on a barebones at my apt for years. I just moved into a house and in anticipation I basically cloned the setup onto a Dell r210. I tested it thoroughly at the the apt and it worked perfectly. Now I'm at the new house and having issues. I can connect to the internet straight through the modem, but when I plug in the pfsense box I'm not getting any internet (and accessing the GUI is pretty slow). Obviously my isp assigned ip address has changed but I really thought that wouldn't be an Issue and don't know what settings to change to get this to work. Accessing the GUI directly gives an IP address of 0.0.0.0 which I assume is indictive of the issue. Can someone please point me in the right direction, I'm losing my mind here and a bit out of my depth.



  • https://docs.netgate.com/pfsense/en/latest/routing/connectivity-troubleshooting.html

    I'm running through this troubleshooting but am stuck at the first step that asks if the wan address is right, which is not set in Interfaces>WAN. Pretty much everything is default install, ie there is nothing entered in Interfaces>WAN


  • LAYER 8 Rebel Alliance

    What is your ISP and connection type?
    Same ISP in the old apt and new house?

    -Rico



  • I had Comcast Business at my old apt and Comcast Residential in my new house.



  • @Rico said in Wan 0.0.0.0 after working fine at old house:

    What is your ISP and connection type?
    Same ISP in the old apt and new house?

    -Rico

    As for connection type, I guess I just don't fully understand the question but it's cable. I'm using a Motorola surfboard sb6141 I think



  • Is there some setting on the modem that's needed? In the past I've made no changes in the modem interface


  • LAYER 8 Rebel Alliance

    So when you plug your PC directly to the modem the internet access works?
    Using Windows? Can you show the output of ipconfig /all in cmd?
    And show your pfSense WAN Config (screenshot).

    -Rico



  • So it's a Mac and screenshots are a little difficult without internet access but I'll try my best


  • LAYER 8 Rebel Alliance

    I'm no Mac User but since it's some kind of Unix ifconfig should do. ;-)

    -Rico



  • Oh of course. Might do a picture from my phone :/



  • Here are some screenshots of the ifconfig -a output, as well as the WAN settings and Dashboard of pfsense and thank you so much for taking an interest!

    https://imgur.com/a/hVIDlNW


  • LAYER 8 Rebel Alliance

    Hmmm no IPv4 on your Mac either. Seems like there is no DHCP Server running.
    Can you get to your Modems WebIF? Default IP is 192.168.100.1 AFAIK.
    What happens when you configure your pfSense WAN to static IP 192.168.100.2 with Gateway 192.168.100.1?

    -Rico



  • @Rico said in Wan 0.0.0.0 after working fine at old house:

    Hmmm no IPv4 on your Mac either. Seems like there is no DHCP Server running.
    Can you get to your Modems WebIF? Default IP is 192.168.100.1 AFAIK.
    What happens when you configure your pfSense WAN to static IP 192.168.100.2 with Gateway 192.168.100.1?

    -Rico

    So i ran the ifconfig when I was directly attached to the modem, hence, i think, no dhcp? did you want me to run ifconfig when the modem is connected to the pfsense box and then the mac connected to the pfsense box?

    And I can connect to the modem WebIF, did you want something from that?

    I'm not exactly sure how to set my phsense WAN to a static IP, but I would assume it's in that screenshot and can figure it out, only issue is I have a 3rd interface set up for access to the modem when pfsense is up and running (which was working fine before, and to clarify, my subnet was 10.10.10.x and i was still able to point my browser to 192.168.100.1 and see the modem interface, and I did that by assigning a 192.168.1.2 to....something...in that interfaces settings...)



  • Well I tried and got this error (after needing to disable the modemaccess interface)

    https://imgur.com/a/QsdsbWe


  • LAYER 8 Rebel Alliance

    I really don't know your ISP or Modem, but some more Ideas:

    • Cold boot your modem again, wait some minutes and restart pfSense.
    • Swap your network cards, means make your LAN to WAN and vice versa. Maybe your problem migrate to LAN so you know there is a problem with this one network card.
    • Take a Backup of your pfSense config, Factory Reset and start running through the wizard again with basic settings.

    -Rico



  • Here's ifconfig -a when connected through pfsense

    https://imgur.com/a/oamHMg2



  • @Rico said in Wan 0.0.0.0 after working fine at old house:

    I really don't know your ISP or Modem, but some more Ideas:

    • Cold boot your modem again, wait some minutes and restart pfSense.
    • Swap your network cards, means make your LAN to WAN and vice versa. Maybe your problem migrate to LAN so you know there is a problem with this one network card.
    • Take a Backup of your pfSense config, Factory Reset and start running through the wizard again with basic settings.

    -Rico

    Is there info from the modem webui that would help?

    I've done so many different power cycles I'm pretty sure it's not that but it has helped my Mac catch a connection once or twice so I'll try again.

    Woof swapping nics sounds pretty hard. I do have the old pfsense back at my condo and may grab that to see if slotting that in would work. And I COULD start from scratch but it's relatively stock already. Really feels like a little collision setting I haven't thought of but I may end up there.



  • So despite running the cloned pfsense on the Dell r210 for weeks without issue that specific client seems to be the issue. I broke down and grabbed all my old networking equipment from my old condo, including the previous barebones install of pfsense. low and behold, that booted up working. So I guess it's back to the old drawing board with the Dell r210. Thanks for your help, looks like I was barking up the wrong tree.


  • LAYER 8 Rebel Alliance

    Glad you have it working now. ☺

    -Rico



  • Well I'm up and running on my old install, but even after a fresh install (and restore of a new backup) I still get 0.0.0.0 from the WAN IP address on the new Dell install. What should my next trouble shooting step be? Switch the interfaces or can I check something with the DHCP?



  • So I did a Packet Capture and these are the results
    Screen Shot 2019-04-17 at 8.45.15 PM.png

    Can anyone help me decipher this? The lights are active on that ethernet port, i'm really hoping the nic isn't shot, but I'm a bit out of my depth on how to get the WAN to grab an IP address



  • @RickyBaker

    You never mentioned the model of modem you are using..



  • @chpalmer said in Wan 0.0.0.0 after working fine at old house:

    You never mentioned the model of modem you are using..

    Oh I'm sorry, Motorola MB7621



  • @RickyBaker said in Wan 0.0.0.0 after working fine at old house:

    Motorola MB7621

    That is a great modem. Its actually made by Zoom Telephonics and marketed under the Motorola name. I have multiple of the MB model line in place all over the place including at least two in Comcast areas with no issues.

    I know you have already proven that but figured Id mention it.

    Are you able to try a different interface on your R210? Im curious if a crossover cable would make a difference though I actually doubt it. Most equipment in the last decade should not need that.. But to verify that you could put a dumb switch between the modem and the Dell box and try that..



  • I'm sorry @chpalmer I don't quite understand. Is your suggestion to plug the modem into an unmanaged switch and than an ethernet cable from the unmanaged switch into the WAN port? I don't think i even have a crossover cable thought I suppose I could try to make one. The fact that this exact Dell worked before I moved it to the new house, leads me to believe that prob won't work. fwiw there's some life: the WAN reads N/A when no ethernet is plugged and and quickly displays 0.0.0.0 when the modems ethernet cable is plugged into the WAN port. and the attached Monitor displays life as well:

    IMG_20190419_204909.jpg



  • well- crossover cable or unmanaged switch would accomplish the same thing with normal straight through cables..

    Im trying to see if your interfaces are fighting each other. Different modem than the last house?

    There are some people that were having issues with the cable ISP doing something strange regarding MTU and DHCP that was causing them issues.. It was not to long ago so a quick search might turn up something. If I find it Ill post..



  • @chpalmer said in Wan 0.0.0.0 after working fine at old house:

    . Different modem than the last house?

    yes! I switched from Comcast business to residential (so not much of a change there) but I DID change the modem. I went from a Motorola 6141 to the MB7621. However the older PFSense install on a zotac connected immediately when plugged into the MB7621.

    Yes please! I haven't found anything but I'm admittedly a bit out of my depth (have to google MTU for instance). Someone on another thread suggested spoofing my old pfsense boxes mac address so I'm gonna try that tonight. Do you still think i should put a switch between the Modem and the Dell pfSense?



  • Yeah so this got solved with a power cycle of the modem. That I SWEAR i'd done 1000 times in myriad different orders of operation. I did refresh and renew the dhcp under Interfaces->WAN before the the refresh/renew had seemingly done nothing (still had 0.0.0.0). So I'm up for now at least...


Log in to reply