Minowboard reboot bug

techpro2004

One more thing I just noticed

/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1581544166] unbound[54749:0] error: bind: address already in use [1581544166] unbound[54749:0] fatal error: could not open ports'

and

/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1581544166] unbound[65021:0] error: bind: address already in use [1581544166] unbound[65021:0] fatal error: could not open ports'

jimp

Your modem is probably handing out an RFC1918 address when it's not in sync, and pfSense picks that up but doesn't switch back to the public address after it gets a link.

In your WAN settings, there is a box to reject DHCP leases from a specific address. Add 192.168.10.1 in there and then see if you can reboot successfully.

techpro2004

I tried it but no luck. Please look into the unbound errors I just posted

stephenw10

That unbound error is common at boot if it tried to start twice for some reason. I've never seen it cause a problem.

The fact your WAN is pulling a private IP from the modem is almost certainly the issue here.

Steve

jimp

With that address in the "Reject leases from..." box, do you still see that private address at boot time in the logs? If so, look in the DHCP logs on pfSense, maybe its reporting a different DHCP server. If so, put the private address you see in the logs there. It would be on lines labeled DHCPOFFER from x.x.x.x or DHCPACK from x.x.x.x.

techpro2004

I don't see that address but I do see something else. I get a lot of these errors:

arpresolve: can't allocate llinfo for 108.6.172.1 on igb0

I also have a few of these

/rc.linkup: DEVD Ethernet detached event for wan

and a few seconds later

/rc.linkup: DEVD Ethernet attached event for wan

and

/rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...

/rc.newwanip: rc.newwanip called with empty interface.

Is it possible I have a bad nic?

edit: I just noticed this also:

/rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...

techpro2004

fyi this is on verizon fios so no modem.

jimp

Something upstream is handing you 192.168.10.1 in the previous cases, so either you have something else on the WAN segment serving DHCP, or it's your FIOS CPE/ONT/<whatever they want to call it> doing it.

jimp

@techpro2004 said in Minowboard reboot bug:

Is it possible I have a bad nic?

Not likely, but you could swap the WAN/LAN assignments and see if the behavior changes.

techpro2004

Well We both got it wrong. In System/Routing/Gateways, Somehow I had 2 gateways. WANGW which had a gateway and monitor of 192.168.10.1 and I had WAN_DHCP. I switched the default to WAN_DHCP and then deleted WANGW and now it appears to be working. I don't know how WANGW got in there but I will look into it. FYI, fios is ipv4 only Thanks.

jimp

It's always in the last place you look, eh? :-)

techpro2004

Absolutely, every time. That is because once you find it you stop looking :)

stephenw10

Hard to argue with that!

techpro2004

Now that we know it is not a hardware issue, maybe you should move this thread to a more appropriate area of the forums. Thanks.

jimp