Unusual Booting Up Message
-
@stephenw10 said in Unusall Booting Up Message:
Hmm, strange. I assume you are not seeing any routing issues? Just that log message?
Yes and why I wondered about the complaining...
-
vtnet1 is definitely LAN there? And it's using a static IP?
If you do a Status > Filter Reload do you see any errors?
-
@stephenw10 said in Unusall Booting Up Message:
vtnet1 is definitely LAN there? And it's using a static IP?
If you do a Status > Filter Reload do you see any errors?
Yes vtne1t is definitely LAN with static 10.8.27.1...now, I wondered whether the backup restoration had vtnet2 and vtnet3 but Linux bridges had not been created yet...I added them earlier but that shouldn't caused the bad route vtnet1 complaint.
No errors:Initializing
Creating aliases
Creating gateway group item...
Generating Limiter rules
Generating NAT rules
Creating 1:1 rules...
Creating outbound NAT rules
Creating automatic outbound rules
Setting up TFTP helper
Generating filter rules
Creating default rules
Pre-caching all clients use pfSense DNS...
Creating filter rule all clients use pfSense DNS ...
Creating filter rules all clients use pfSense DNS ...
Setting up pass/block rules
Setting up pass/block rules all clients use pfSense DNS
Creating rule all clients use pfSense DNS
Pre-caching NTP for all clients...
Creating filter rule NTP for all clients ...
Creating filter rules NTP for all clients ...
Setting up pass/block rules
Setting up pass/block rules NTP for all clients
Creating rule NTP for all clients
Pre-caching Default allow LAN to any rule - priviledge ports...
Creating filter rule Default allow LAN to any rule - priviledge ports ...
Creating filter rules Default allow LAN to any rule - priviledge ports ...
Setting up pass/block rules
Setting up pass/block rules Default allow LAN to any rule - priviledge ports
Creating rule Default allow LAN to any rule - priviledge ports
Pre-caching Default allow LAN to any rule - UDP ports...
Creating filter rule Default allow LAN to any rule - UDP ports ...
Creating filter rules Default allow LAN to any rule - UDP ports ...
Setting up pass/block rules
Setting up pass/block rules Default allow LAN to any rule - UDP ports
Creating rule Default allow LAN to any rule - UDP ports
Pre-caching Default allow LAN IPv6 to any rule...
Creating filter rule Default allow LAN IPv6 to any rule ...
Creating filter rules Default allow LAN IPv6 to any rule ...
Setting up pass/block rules
Setting up pass/block rules Default allow LAN IPv6 to any rule
Creating rule Default allow LAN IPv6 to any rule
Creating IPsec rules...
Generating ALTQ queues
Loading filter rules
Setting up logging information
Setting up Ethernet filter rules...
Setting up SCRUB information
Processing down interface states
Running plugins
Done -
Hmm, try running:
etc/rc.reload_allat the command line.Do you see the error there?
-
@stephenw10 said in Unusall Booting Up Message:
Hmm, try running:
etc/rc.reload_allat the command line.Do you see the error there?
Yet, it's there...
-
Sorry you need ghe leading / so:
/etc/rc.reload_allRun that from the actual command line not via the GUI.
-
@stephenw10 said in Unusual Booting Up Message:
Sorry you need ghe leading / so:
/etc/rc.reload_allRun that from the actual command line not via the GUI.
So, it's appears something it doesn't like for unknown reason...
-
Doe this also hit it?:
/etc/rc.reload_interfaces -
@stephenw10 said in Unusual Booting Up Message:
Doe this also hit it?:
/etc/rc.reload_interfacesIt doesn't appear to...do you think it's because I have since added the other two interfaces of the four-port NIC to Linux bridges, eg. vtnet2 and vtnet3 that were in the backup?
-
No I doubt it, that wouldn't affect routes added on vtnet1.
-
@stephenw10 said in Unusual Booting Up Message:
No I doubt it, that wouldn't affect routes added on vtnet1.
That's what was revealed when I reboot...it's still complaining...I may reinstall again.
-
N NollipfSense referenced this topic on
