Update to latest snapshot (1537) this morning appears to have broken my network
-
Could be a coincidence but I started working on carp just day before. Can't see the opp node in pfsync. May be it's just coz of this snapshot issue.
-
Possible, but since nobody is commenting this we don`t know :)
All I was able to find out was that Intel drivers were updated 19 days ago… -
Can you check if polling is enabled on your NICs?
I noticed that after this commit, Only set IFCAPS where they're not already set correctly. Ticket #5887 #7f283fab1b18bb575537bb8498b16a6b1b6d0251 it enabled polling on 2 out of my 3 NICs even though it was disabled in the configuration.
From the console turning off polling on the interfaces where it was enabled allowed me to regain access to the system over the network.
Reverting that commit allows the system to function after a reboot.
I am using 3 RE interfaces with 2 of them in a LAGG with VLANs.
-
Reverting that commit allows the system to function after a reboot.
I reached the same conclusion here testing it today. I reverted the commit from the repo, a new functional snap should be up before long.
If you are on a non-functional snapshot you can use the system patches package to revert that commit and then it should be OK. A reboot would be the easiest way to get things going after, though saving/applying the lagg and child interfaces should also do it
-
Hey Jimp!
Thanks for that.
Can this also influence on my issue in the other thread?
Thanks!
-
Unlikely, but possible, worth trying. Keep that in the other thread though.
-
I can confirm that updating +gitsyncing solved this one (lagg).
I also updated my thread because it solved my issues too :) -
So, after next snapshot it is save to update again. Is that correct?
-
With current. :)
-
I see 2.3.b.20160215.1142 in dashboard.
Don't have the time to update now (actualy to repair if it fails). Will do when enough time to execute repair (reinstall 2.3 beta from some snapshots ago).
-
I see 1408.
And with what you see issues are resolved. -
Will the reversal of this commit also resolve the issues I had with VLANs not being routed through pfsense? I am not using LAGG so a bit unclear on this.
Thanks in advance.
-
Will the reversal of this commit also resolve the issues I had with VLANs not being routed through pfsense? I am not using LAGG so a bit unclear on this.
If it broke on a snap from last Saturday, then maybe. If it's an older issue, probably not.
-
It solved my problem (multiple VLANs and LAGG)
-
Yup - happened Saturday, which is when I started this post.
I can confirm that the 2.3 now works fine with my setup, using VLANs. No LAGG.
Thanks.
-
Spoke too soon. Looks like clients are no longer routing out VPN, despite PIA VPN connection being up. Maybe something else broke this.. :-[
-
VPN (PIA in my case) gave problems in my setup also. Gateway status stay at 'pending' until I turned off gateway monitoring. After that, it start working and routing traffic. Maybe not just my setup….
