2.2 vlans and ubnt edge switch



  • I was pulling my hair out trying to get 2.2 RC working with the ubnt edgeswitch-48.  I tried every setting, every option for a few days, couldn't get it to work.  Switched back to 2.15 and had it working within minutes.  I have no idea what would be causing it, but figured I should report it.

    Hardware is the rackmount supermicro d525
    http://mitxpc.com/proddetail.asp?prod=ER1UX7SPEHD525FIO&cat=211

    and a 4 port intel 100/1000 NIC.



  • What is work and what isn't working?



  • I strongly suspect whatever happened there wasn't specific to the version. VLANs are widely used on similar if not identical hardware to what you have. Your config somewhere wasn't right, and you got it right after redoing it. If you upgrade back to 2.2 with your working config now (get a backup beforehand so you can restore to 2.1.5 if needed), it'll almost certainly work.



  • @Harvy66:

    What is work and what isn't working?

    I wasn't able to pass traffic to the router, just nothing



  • @cmb:

    I strongly suspect whatever happened there wasn't specific to the version. VLANs are widely uersed on similar if not identical hardware to what you have. Your config somewhere wasn't right, and you got it right after redoing it. If you upgrade back to 2.2 with your working config now (get a backup beforehand so you can restore to 2.1.5 if needed), it'll almost certainly work.w

    It makes sense to me that I wouldn't be the only one experiencing this if it was an issue. 
    At the end though, the switch config was exactly the same, I reinstalled 2.1.5 from scratch, not changing anything to the switch config and it came up asap.  I originalyl did have a bit of a funky config, using Vlan's over a LAGG group to the switch.  When that didn't work, I started peeling back the complexity until I was left with just a straight vlan on PFsense and no luck.  Restarted both devices as that had been a problem before.  Still nothing.  It wasn't passing traffic.    I was able to setup the same config in 2.1.5 and have it working nicely.

    Unfortunately I put the switch and router into a DC from my lab running 2.1.5 so it's not easily accessible.  I'll go give it a try in the next few days.

    What should I be looking for for logs if it doesn't work?



  • Just a guess into the blue:
    I remember to have encountered similar problems between pfSense 2.1.x beta and OpenWRT Backfire.
    I tracked it down to having to do with vlan traffic priority tagging -> pcp.
    Someone here gave me the hint to set the following "system tunables"

    net.link.vlan.mtag_pcp 1

    net.link.vlan.soft_pad 1

    Since then it worked perfectly.
    Up to my knowledge, ubnt airos is a modified flavour of openwrt. Probably it is related somehow.
    Let me know, if it helps.



  • @epek:

    Just a guess into the blue:
    I remember to have encountered similar problems between pfSense 2.1.x beta and OpenWRT Backfire.
    I tracked it down to having to do with vlan traffic priority tagging -> pcp.
    Someone here gave me the hint to set the following "system tunables"

    net.link.vlan.mtag_pcp 1

    net.link.vlan.soft_pad 1

    Since then it worked perfectly.
    Up to my knowledge, ubnt airos is a modified flavour of openwrt. Probably it is related somehow.
    Let me know, if it helps.

    I'll check that out.  I think the edge switches are based off Broadcom Fastpath though.

    I've been reading on the ubnt forums of some people having Vlan trouble and it relating to MTU size.  I'm not sure why that would change from 2.1.5 to 2.2 though.  I'm going to head down there today to play for a bit, will report back.



  • Did it help?



  • I did get them working.  Part of the issue was that there was no type assigned to the LAGG group.  The reason there was no type was because when there was a type, (i only tried failover and loadbalance), the lagg interfaces didn't show up as available interfaces in the VLAN setup menu.  However, they did show up when "none" was selected.  "none" doesn't pass any traffic.  Going back after and then switching to loadbalance worked just fine.

    The vlan lagg issue seems to have been resolved in a nightly build.

    I think this was similar

    https://forum.pfsense.org/index.php?topic=86147.0

    Thanks for the help!


Log in to reply