SG-1100 suddenly stopped working - no IP from WAN
-
My SG-1100 has been working beautifully for close to a year and then, this morning my internet went down… It first slowed down to a crawl and then stopped working completely.
I checked all the cables, modem, etc. one by one to make sure the problem comes from my router, then I used
Diagnostics → Factory Defaults
and went through the wizard to reset everything.When I first bought the device, everything worked out of the box. Not this time… I'll be honest, I don't really know what I'm doing, but I can usually figure out what I need to research. This time, I don't even know where to go from here.
Everything seems ok on the LAN (although it does take forever for pfsense to load at 192.168.1.1). The things I can notice that I'm guessing have to do with my problems:
- The
dpinger
Gateway Monitoring Daemon service won't start - Status → Gateways both
WAN_DHCP
andWAN_DHCP6
have a "pending" status - System → Routing → Gateways → WAN_DHCP has an IP of
98.37.144.1
but if I connect directly to my modem, my computer says my modem's IP is98.37.72.1
and when I click on "edit" there is no way to update that IP, it just says "dynamic"
Could it be that the IP is not updated for some reason? I didn't change any of the WAN DHCP Client Configuration since the wizard said the default was good in most cases (and it's been working great until today).
If you need any additional info, logs, or anything else, to be able to help, let me know… It worked out of the box until now, so I'm basically a noob with this stuff
SG-1100 + 21.02-RELEASE-p1 (arm64)
- The
-
Hi,
Use the setup that worked already for a year.
Reboot the syste properly (that is : not be removing the power - as that is very bad).
Follow the entire boot process from the console access.When WAN is down, DNS is down, and the GUII access can be somewhat slow to react, that's 'normal'.
When the system booted correctly, can you Status > Interfaces and remlase the WAN IP ?
Wait some seconds, and then reconnect.
What does the DHCP logs tells you ? -
@gertjan I followed your directions: loaded my backup config and used
Diagnostics → Reboot
then released the WAN, waited a minute and clicked on "Renew WAN".I couldn't find any log entry at the exact time I released/renewed the WAN DHCP, but here are the log for around that time:
May 11 10:56:48 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 8 May 11 10:56:27 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 21 May 11 10:56:15 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 12 May 11 10:56:10 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 5 May 11 10:56:08 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2 May 11 10:56:07 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:56:06 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:55:53 dhclient 44601 FAIL May 11 10:55:53 dhclient 47197 No working leases in persistent database - sleeping. May 11 10:55:53 dhclient 43177 Deleting old routes May 11 10:55:52 dhclient 35199 New Routers (mvneta0.4090): 98.37.144.1 May 11 10:55:51 dhclient 34723 New Routers (mvneta0.4090): 98.37.144.1 May 11 10:55:51 dhclient 34691 New Broadcast Address (mvneta0.4090): 255.255.255.255 May 11 10:55:51 dhclient 34482 New Subnet Mask (mvneta0.4090): 255.255.254.0 May 11 10:55:51 dhclient 34380 New IP Address (mvneta0.4090): 98.37.145.152 May 11 10:55:51 dhclient 34144 ifconfig mvneta0.4090 inet 98.37.145.152 netmask 255.255.254.0 broadcast 255.255.255.255 May 11 10:55:51 dhclient 34090 Starting add_new_address() May 11 10:55:51 dhclient 33820 TIMEOUT May 11 10:55:51 dhclient 47197 Trying recorded lease 98.37.145.152 May 11 10:55:51 dhclient 47197 No DHCPOFFERS received. May 11 10:55:46 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 5 May 11 10:55:35 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 11 May 11 10:55:18 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 17 May 11 10:55:04 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 14 May 11 10:54:58 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 6 May 11 10:54:54 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 4 May 11 10:54:52 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2 May 11 10:54:50 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2 May 11 10:54:37 dhclient 97922 FAIL May 11 10:54:37 dhclient 47197 No working leases in persistent database - sleeping. May 11 10:54:37 dhclient 97096 Deleting old routes May 11 10:54:36 dhclient 89042 New Routers (mvneta0.4090): 98.37.144.1 May 11 10:54:35 dhclient 88129 New Routers (mvneta0.4090): 98.37.144.1 May 11 10:54:35 dhclient 88001 New Broadcast Address (mvneta0.4090): 255.255.255.255 May 11 10:54:35 dhclient 87847 New Subnet Mask (mvneta0.4090): 255.255.254.0 May 11 10:54:35 dhclient 87557 New IP Address (mvneta0.4090): 98.37.145.152 May 11 10:54:35 dhclient 87208 ifconfig mvneta0.4090 inet 98.37.145.152 netmask 255.255.254.0 broadcast 255.255.255.255 May 11 10:54:35 dhclient 87065 Starting add_new_address() May 11 10:54:35 dhclient 86959 TIMEOUT May 11 10:54:35 dhclient 47197 Trying recorded lease 98.37.145.152 May 11 10:54:35 dhclient 47197 No DHCPOFFERS received. May 11 10:54:32 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 3 May 11 10:54:16 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 16 May 11 10:53:59 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 17 May 11 10:53:45 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 14 May 11 10:53:40 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 5 May 11 10:53:38 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 2 May 11 10:53:37 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:53:36 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:53:35 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:53:34 dhclient 47197 DHCPDISCOVER on mvneta0.4090 to 255.255.255.255 port 67 interval 1 May 11 10:53:21 dhclient 11536 FAIL May 11 10:53:21 dhclient 47197 No working leases in persistent database - sleeping. May 11 10:53:21 dhclient 10783 Deleting old routes May 11 10:53:20 dhclient 10256 New Routers (mvneta0.4090): 98.37.144.1 May 11 10:53:19 dhclient 9937 New Routers (mvneta0.4090): 98.37.144.1
-
@gertjan Looking into logs some more, in the System logs, I see those:
May 11 10:51:00 rtsold 48078 <cap_rssend> sendmsg on mvneta0.4090: Permission denied May 11 10:50:56 rtsold 48078 <cap_rssend> sendmsg on mvneta0.4090: Permission denied May 11 10:50:52 rtsold 48078 <cap_rssend> sendmsg on mvneta0.4090: Permission denied
And in the Firewall logs, I see tones of those:
May 11 11:12:59 WAN Block all IPv6 (1000103383) [fe80::201:5cff:fe83:a046] [ff02::1] ICMPv6 May 11 11:12:57 LAN Block all IPv6 (1000103383) [fe80::e263:daff:fee9:381d]:44008 [ff02::1]:10001 UDP May 11 11:12:56 WAN Block all IPv6 (1000103383) [fe80::201:5cff:fe83:a046] [ff02::1] ICMPv6
Like I mentioned, I'm total noob material, so I don't really know what those mean but I'm adding this here since it looks like it could be related?
Thanks a bunch for your help!!
-
@yannb It's not getting an IP address from upstream. DHCP is not responding to address requests. I would power down your modem and then router, wait 10s then power up the modem until it is fully ready then power up pfSense.
-
@kom I'm pretty sure I've tried that already, but I've tried so many things I'm doubting myself… I will try that again for good measure.
Thanks!
-
I would add one thing to what KOM stated. If you power down the modem and wait 10 seconds and it still does NOT work then power down the modem and wait 15 minutes before powering it back on. If that modem has a battery backup in it, make sure you remove that as well during the 15 minutes you wait to power it back on. Looks like you are using Comcast Cable and sometimes you need to wait this long to pull an IP.
Did you plug up a laptop or some other device to that modem to check and see if the modem and Internet were working? If you did, and that device worked you need to shut down that modem for at least 15 minutes before powering back on and then plugging it back up to pfSense.
I am in a different area with a cable provider and whenever a routing appliance is switched out this ALWAYS has to be done or the new device (routing appliance) won't work. Well, I guess you could clone the MAC address of the working device in pfSense's WAN interface and it will work but I wouldn't advise doing that.
-
Thanks guys…
Checking each part of the network independently to isolate the cause of the outage is the first thing I did: computer straight in modem works just fine, I swapped all the ethernet cables to make sure they all work, etc. The issue is definitely my SG-1100.
I tried what you recommended: turned off everything, unplugged the power from everything, unplugged the cable connection too just in case. Left if off for an hour (had to step out) and reconnected everything.
Still the same issue.
Not sure what to try next
-
Figured it out… In case someone runs into the same issue:
After finding this reddit post, I tried to power down the modem only, while leaving my SG-1100 on.
And that did the trick for me, pfsense could finally pick up the IP for my WAN. Take that with a grain of salt though, 'cause I'm 90% sure that's the first thing I tried, so it could be a coincidence and some cache cleared somewhere or something else? ️
Something to try if you get stuck like me though…
Thanks guys!!