frozen pfsense, administration interface, openvpn...
-
Can you pls. check if you have any kind of power management on the pfsense machine?
It could be a NIC going into hybernation.
-
@rds25 said in frozen pfsense, administration interface, openvpn...:
the only PC connected to the lan interface is off.
Poor router firewall. It needs two interfaces to exist, and you disable one
?
Maybe it works just fine, but I'm not a member of the club that tries to run a router with one or even less interfaces. As it makes no sense.
What about adding a switch between that one PC and pfSense ?
At least pfsense will have its two NIC up all the time.Btw : this is just me thinking out loud. Dono what happens when LAN goes away. Never tried that. If LAN goes away, might as well shut down pfSense all together.
-
@cool_corona
indeed if PFsense attach services on an int which goes into hibernation, this is a problem. -
Indeed, Pfsense needs two interfaces.
I have a Wan a Lan and two other interfaces used for servers.
The Lan interface is only used to manage the firewall in my case.
So, if the interface has a hibernation option, I will not add a switch which is not very ecological, just to have a UP port to look pretty.In the case of figure, if the Lan Switch is down that to crash the firewall by domino effect?
Why not link Pfsense’s vital services to a virtual interface?? -
@rds25 said in frozen pfsense, administration interface, openvpn...:
which is not very ecological
I fully agree.
Your pfSense also agrees : a frozen pfSense .... what about removing the power cord ?
With just the WAN active, pfSense will check every 12 hours if there is a package update.
It will sync NTP.
And according to the resolver settings, keep the DNS cache up to date.
I mean : what's that good for ?Still, now serious : it should work with LAN going down = no carrier.
If it works well if the NIC device goes into sleep mode : that's more a hardware question, like : does the driver support that ? The OS ? pfSense ?
It's not a common scenario. -
now that the cause is identified.
solution 1: connect a switch to the port called LAN which I only use to configure the fw.solution 2: does pfsense offer a function to deactivate hibernation.
ps: I have 2.5gbps ports that only work with unstable 2.7.0.
-
@rds25 said in frozen pfsense, administration interface, openvpn...:
solution 2: does pfsense offer a function to deactivate hibernation.
In my knowledge hibernation should be turned off in the BIOS of the machine ...
-
I only "disabled HCPI hibernation" but if I'm not mistaken, it's for the general sleep mode of the machine and not of one or more interfaces?
-
@rds25 said in frozen pfsense, administration interface, openvpn...:
I only "disabled HCPI hibernation" but if I'm not mistaken, it's for the general sleep mode of the machine and not of one or more interfaces?
Power management for individual interfaces is specifically to the interface hardware - you have to dig deep if you want to manipulate that (AFAIK)
-
So to summarize I will plug a switch on the port to force the lifeline.
And I’ll tell you again if the workaround works. -
@rds25 said in frozen pfsense, administration interface, openvpn...:
So to summarize I will plug a switch on the port to force the lifeline.
That could be a workaround. If you dont mind - what hardware (machine) are we talking about?
-
@fireodo
Good morning,
Don’t worry, it’s a prototype from the future.
All I can say is that the interfaces are "intel i226-v"
Or the norm is hibernating non-active interfaces. -
@rds25 said in frozen pfsense, administration interface, openvpn...:
Don’t worry, it’s a prototype from the future.
... then I hope the Flux capacitor is still OK!
-
@fireodo said in frozen pfsense, administration interface, openvpn...:
Flux capacitor
Yeah, doc, but we gotta cool it!
Thank you all for your intelligence of mind, and your responsiveness, long life to pfSense community.
