Update to latest snapshot (1537) this morning appears to have broken my network
-
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ā¦.