System Log WAN errors on boot

Started by bunchofreeds, August 04, 2022, 06:22:04 AM

Previous topic - Next topic
Hi,

I'm seeing this set of errors in the System>General logs on a reboot.
My connectivity seems fine however

Just wondering what they are about as I hate seeing errors
I've recently applied some fixes regarding a WAN DHCP lease renewal issue, but pretty sure these were showing before that.


2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.routing_configure: The WAN_DHCP monitor address is empty, skipping.
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.routing_configure: ROUTING: keeping current default gateway '100.100.100.1'
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.routing_configure: ROUTING: setting IPv4 default route to 100.100.100.1
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.routing_configure: ROUTING: IPv4 default gateway set to wan
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: The WAN_DHCP monitor address is empty, skipping.
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway '100.100.100.1'
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.100.100.1
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: On (IP address: 100.100.100.100) (interface: WAN[wan]) (real interface: vtnet1).
2022-08-04T15:35:30 Error opnsense /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'vtnet1'
2022-08-04T15:35:23 Error opnsense /usr/local/etc/rc.newwanip: IP renewal deferred during boot on 'vtnet1'

These are diagnostic messages feed through the canonical "log_error" function. Since 22.1 they actually show up as "errors" in syslog with the extended format but in truth they need to be lowered in severity since they are not real errors (and have existed for ages).


Cheers,
Franco

Thanks again for your help here @franco.

I will duly ignore these :)

Still have these in my TODO, hopefully in 23.1 they will have reasonable severity levels (probably "notice").


Cheers,
Franco