non-ENA0 as WAN
-
But in both cases you're seeing the WAN assignment change to ena0 across a reboot?
-
Yes
-
Is that shown in the config history? Is there a reason shown?
What exactly are you seeing change? I'm having a hard time imagining what could be happening here!
-
Please see below - it loads like this. No exceptions - just brings a single interface up and then puts all IP's as aliases on it (you see LAN and WAN together on one ena0). Then you can see me logging in as admin and re-assigning the interfaces. Right after, you see IPSec coming up as an indicator that WAN interface is in the right place.
P.S.: I would really appreciate some help with another issue I mentioned before - I am in a jam there. Cheers mate!
-
Hmm, that's the output in the main system log?
It's odd that it ena1 going up only after you connect.
But also back to my earlier question; what does the config history show when you initially log in?
I would also expect to see a whole bunch of other scripts triggered if you re-assign an interface like that.
Is LAN unassigned at that point? Assigned as ena0 also?
-
LAN and WAN are collapsed into one interface. I have to manually login and re-assign WAN to be on ena1. About scripts - I don't see anything
special there.Let me know where I can send you the debug information - I don't want to post it publicly.
-
Sure, please upload anything you can here: https://nc.netgate.com/nextcloud/s/eF4YsKErrP97X6A
-
Added logs, config and network environment files into the drop point. let me know if you need anything else.
Regards
-
Ok, so when were those files taken?
The system log looks like you restored a config file after the initial boot?
I assume that was not the config file that you uploaded?
Those also look like 24.11 logs only. I assume 25.03 shows similarly?
-
After encountering the VPN issue, I attempted to use the paid PFSense and was indeed restoring the configuration from the community edition. Files were taken this morning, while I was restoring them about 24 hours before. I will be restoring the 25.03 version because of the bugs, and can send these as well - they should be looking similar.
-
Yes, I'd like to see that. I'd also particularly like to see the configuration history after it fails. The only thing I can imagine so far is that is fails to detect ena1 and somehow assigns all interfaces to the only remaining NIC.
But if that did happen it should drop to the interfaces assign prompt because the config contains interfaces no longer in the system.
In the config you uploaded though both WAN and LAN are assigned as ena0 and that shouldn't be possible.
