VLAN routing non-functional after 2.3.3 upgrade



  • Hi,
    I've been running pfSense with 5 VLANs on my em1 interface on my router, all tagged.
    VLAN1 is on 10.10.2.0/24
    VLAN11 is 10.10.11.0/24
    VLAN12 is 10.10.12.0/24
    etc..
                                              LAN2 host
                                                  |                              /–-------------VLAN11 hosts
                                            (em2)                          /            /----------------------VLAN13 hosts
    Internet(Comcast)---(em0)pfSense(em1)====(1/g48)Dell 6248======Other Dell Powerconnect
                                                                                                          \======Other Dell Powerconnect

    I upgraded from 2.3.2 to 2.3.3 and the network is now non-functional. Things seemed to be fine for a while but then traffic stopped flowing between pfSense and VLANs.

    Any ideas. I've disabled all but one VLAN.
    In the DHCP logs I see hosts broadcasting for an address, and they get offered an address according to the log, but they never ACK/claim the lease.

    I've connected a PC to em2 and configured it as a secondary LAN with no VLAN config. Works with no issues.


  • Netgate

    Nothing from 2.3.2 to 2.3.3 would have changed anything there.

    Packet capture and see what's really going on.



  • Those PCAPs don't make much sense. I don't see any tagged traffic arriving at all in pcap-4.

    Please post a screen shot of your Interfaces > Assign and the output from Diagnostics > Command Prompt Execute: ifconfig -a

    packetcapture-3.pcap
    packetcapture-4.pcap



  • No issue here with pfSense. Configuration error on switch which didn't manifest as a problem immediately, so didn't cause a problem initially.


  • Netgate

    Wow. Sorry, man. it looks like I hit modify there instead of reply. Ugh.

    Glad you got it sorted out though.