Overwrote Configuration Now I Have Issues
-
Mmm, dynamic gateways are not stored in the config unless you apply some custom setting to them like the monitor IP.
However that shouldn't be needed to set the default gateway.
Check the system and routing logs at boot. Something is failing to set the default route or removing it.
Do you have multiple gateways defined? The OpenVPN interfaces perhaps? If you have OpenVPN clients one of them could be pushing a new default route.
-
@stephenw10 Changed speed and duplex on WAN to default once again and rebooted, been checking the logs under System - General but I don't see anything unusual Pastebin for reference (hope I sanitized that good enough). There is nothing under the System - Routing logs save for one entry from April 15 of this year about starting radvd 2.19, which I removed hoping that new logs would be created but that has not been the case as the log is still empty.
As for defining multiple gateways, yes I have the WAN_DHCP and three OpenVPN clients. The OpenVPN's are combined into a gateway group and is configured as is detailed in this guide. I do have Don't add/remove routes checked in the config of all three so I am unsure of how they could be pushing a new default route. Also if they were pushing a new default route wouldn't that show up as the default when I use netstat -rn at boot?
-
Hmm, what I don't see there is:
Jul 4 20:17:26 php-cgi 447 rc.bootup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP' Jul 4 20:17:26 php-cgi 447 rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.Or similar to that.
But what I do see is that it appears that igb0 links some seconds after igb1 and the VLANs on that:
Jul 4 09:53:25 kernel igb1: link state changed to UP Jul 4 09:53:42 kernel igb0: link state changed to UPWhat are those NICs actually connected to?
I think you're seeing that dhclient error because at that point in the boot it's trying to start it on an interface that is down.
If you simply disconnect and reconnect the WAN cable after boot does that also restore the default route?
Steve
-
@stephenw10 NIC is a Intel I350-T4 port igb0 is connected to the DSL modem and port igb1 is connect to a 16-port TP-Link switch, ports igb2 and igb3 are not connected to anything.
When I first started troubleshooting this I believe I tried unplugging the modem and plugging it back in and that seemed to give igb0 an IP from my ISP. Keep in mind that this first started happening with 2.6 and on boot it would tell me my WAN_DHCP gateway was offline while on 2.7 the gateway is online, it has an IP from the ISP but for some reason has no globe icon by the default gateway and is unable to ping anything from the WAN. I don't think I ever tried just unplugging the cable and plugging it back in (may give that a try). On 2.6 I was also able to go to Status - Interfaces and renew the lease on the WAN, I have not tried this on 2.7 because it already has an IP.
-
The globe icon indicates the current default gateway/route. You don't see one because for some reason it's not setting a default route when the dhcp client pulls a lease. Even though it is pulling a public IP and a gateway.
Check the DHCP logs for the dhclient entries when it connects. Are there errors shown when it tries to add the gateway as a router?I think you may be hitting two issues here. Try renewing the dhcp lease in 2.7 and see if that also adds the default route.
-
@stephenw10 Here is a Pastebin Link for the DHCP log during the same time as the other log (July 4: 09:52-09:54) and I am not seeing any errors when it's adding new routers or any errors at all for that matter.
Next time I reboot I will try to release and renew the IP, I imagine it will work but that's just an assumption. Also not sure what good it will do.
-
Mmm, nothing in that log, looks fine.
When you reboot pfSense does the WAN actually link ~20s after the LAN, looking at the link LEDs?
That seems odd if the upstream modem is already up. I bet putting a switch between the WAN and modem would stop this happening. That would be a good test.If that does solve it we might be able to work around it with the dhcp client timing values.
-
@stephenw10 Rebooted again and tried to release and renew the WAN IP which I think it's safe to say that it doesn't work, makes the WAN come up as "Pending" then it just sits there and doesn't choose a default route.
As for watching the NIC activity lights I'm sure the LAN is coming up around 20 seconds or more before the WAN does, as for putting a switch between the modem and the router I'm having trouble finding my old one so that test might be a no go.
I'm also getting a post code error beep from the Asus motherboard now, which I didn't have before. The internet is being less than helpful in finding out it's meaning, and there is nothing in the manual. I hear the POST beep, then beep, one second pause, beep, beep, beep, one second pause, beep. It's either two errors in one about RAM not being seated correctly (all the RAM is showing up in the GUI), or it's complaining about the video card that the system doesn't have, or maybe because the monitor is off. Sigh... computers.
-
Nevermind about the BIOS beep code, seems in was video related and gone now.
-
Hmm, WAN and LAN both on the same 4 port NIC yes?
Is it somehow causing the modem to reboot? I expect it to link immediately to the modem if it's already booted.
-
@stephenw10 Yes, WAN and LAN both on the same NIC and I'm positive the modem is not rebooting.
-
As a test try editing /boot/loader.conf and set autoboot_delay to something much higher like 30.
See if that changes anything.
-
@stephenw10 Some weird behavior here, I edited the file changing autoboot_delay from 3 to 30, I then confirmed that it was changed. I rebooted and saw the 30 second count down, when the box booted back up and I saw that it didn't have any effect at fixing the problem I went to change autoboot_delay from 30 back to 3 but it was already at 3. Something is not being saved properly or settings aren't being adhered to I think.
-
That's expected. The loader values are checked and set at boot. If you actually wanted to keep that setting you would put it in loader.conf.local.
Was the timing in the logs still the same? Between the LAN and WAN linking? Or between the initial WAN dhcp failure and WAN linking?
-
@stephenw10 Rebooted so many times this morning testing various things but as far as I can tell yes the timing is still the same.
-
Can you check the log to be sure. If it really makes no difference then it's something pfSense is doing that slows the link. Which is weird.
-
@stephenw10 I edited the /boot/loader.conf changing autoboot_delay to 30, changed WAN speed and duplex back to default and rebooted. Looks like igb1 comes up first then 18 seconds later igb0 comes up still not choosing default gateway. Interestingly if I leave speed and duplex of WAN on 100baseTX full-duplex both igb0 and igb1 come up at exactly the same time.
-
Hmm, well the only other thing I can suggest testing is a switch between igb0 and the modem.
You could also try re-assigning the NICs in case igb0 is doing something odd but that seems unlikely.
-
@stephenw10 I have been looking all over the place for my old switch but doesn't look like I'm going to find it as it may have been taken to the recycle. I may try switching ports but I don't think that will make much of a difference.
I'm currently debating a complete reinstall and restore and if that doesn't work I'll try setup from scratch, as I keep finding more problems. I have ARP entries that are permanent (static) that keep expiring, and I have certain webpages that unbound refuses to resolve. Trying to figure out if this is caused by the restore or if they are new issues caused by 2.7.
Thank you very much for your assistance thus far.
-
Do you have an old router with a switch in it you could use as a test perhaps?
Or maybe you could put the WAN through a VLAN on another switch so it's already linked?
