Overwrote Configuration Now I Have Issues
-
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?
