Update to latest snapshot (1537) this morning appears to have broken my network
-
Reverted to 2.2.6. Everything back to normal.
-
There's a good chance it isn't just you. I saw my VLANs go down as well, but thought it was the lacp lagg I run them through. Can't seem to route anything through any of them, so I had to move everything over to the non-vlan/lagg port for the time being.
-
All fine here.
Did you tried latest snapshot? -
Yup, that's pretty much what happened with me. None of my tagged VLANs were working. No traffic would route. Working perfectly with 2.2.6 so will stick with this until 2.3 is final.
Using an SG-2440.
-
Broke my amd64 full install. Wan interface in on a Broadcom 5719 interface as a vlan. Put a console on it and saw it hanging at "initialing WAN". Found that if I unplugged the lan cable, it would boot up . I could then plug back in the cable and it came up and started passing traffic.
-
Macboy and others, what nics are you using?
-
We may be in the same boat here: https://forum.pfsense.org/index.php?topic=106845.0
Maybe some driver or something else?Tomorrow devs will comment I`m sure :)
-
Latest snapshot killed my networking. Could not get to pfSense box (connected by LAGG) and VLANs not operational.
On console shell ping 8.8.8.8 gives no route could be found.Reverted to:
2.3-BETA (amd64)
built on Thu Feb 11 00:16:09 CST 2016
FreeBSD 10.3-BETA1And uploaded config.xml and back in business :D
-
I'm using an SG-2440 which uses Intel I354 nics.
I am not using LAGG.
I will stick with 2.2.6 until this is sorted.
-
If it's helpfull, I use this adapter: Intel PRO/1000 PT Dual Port Server Adapter
Both nic's are in use for LAGG connection to my switch (Cisco SG300-28) -
I'm just gathering info because I too have problems but on different layer… maybe its connected
-
Thats a good thing. Updated my pfSense-box 2.3 Beta regular with latest snapshot for a while (starting pre-2.3 beta).
My problem (no WAN and LAN connectivity) started yesterday after another update to latest snapshot.My setup:
| Several VLAN's over LAGG connection on LAN side
Seperate dedicated (Realtek) nic for IPTV
WAN Connection is a PPPoE fiber connection IPv4 and IPv6.
3 concurrent VPN connections for several VLAN's | -
Can you do quick test.
If you disconnect pppoe and then reconnect it, does it work?It doesn`t for me…
-
Sorry, cannot. I am on remote location now and only have VPN access. So if I disconnect…
-
Yay :)
If you can, try it.
For me it fails. -
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!
