Problems defining VLAN interfaces on LAGG ports [RESOLVED]



  • Hello,

    I was doing some testing with 2.0 BETA4 (i386), and noticed that I could quite easily define a LAGG group (using FEC as the protocol). However, I want to then define multiple VLANs off of that LAGG group, but when I went to VLANs and clicked '+', it did not list my LAGG group.

    After poking around for a while, it looks like inside get_nics_with_capabilities(), there's a call to pfSense_get_interface_addresses(), which doesn't appear to be returning 'lagg' (I haven't yet had a chance to look at pfSense_get_interface_addresses() yet to see what it's actually doing). So, I just added an entry to the vlan_native_supp array for 'lagg', and was able to then use VLANs on the lagg interface group I had defined without any problems.

    Obviously, this is a hack and not recommended, but I was wondering if we could get a more official fix somehow?


  • Rebel Alliance Developer Netgate

    How old of a snapshot are you using?

    I added vlans on a lagg interface quite recently and it worked fine.



  • I am currently using the 12/15/2010 build for i386. It doesn't list the LAGG ports on the VLAN page as a selectable interface for me.



  • Can you please show an ifconfig output?



  • @ermal:

    Can you please show an ifconfig output?

    Here you go (the current set of lagg0_vlan{N} entries were added manually by my hacking):

    
    [2.0-BETA4][root@localhost]/root(1): ifconfig -a
    em0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:07:e9:04:5f:8a
            inet6 fe80::207:e9ff:fe04:5f8a%em0 prefixlen 64 scopeid 0x1 
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    em1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:07:e9:04:5f:8a
            inet6 fe80::207:e9ff:fe04:5f8b%em1 prefixlen 64 scopeid 0x2 
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:02:b3:b7:bf:7d
            inet6 fe80::202:b3ff:feb7:bf7d%fxp0 prefixlen 64 scopeid 0x3 
            inet 24.N.N.N netmask 0xfffff000 broadcast 255.255.255.255
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    fxp1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
            options=219b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic>ether 00:02:b3:b7:bf:7e
            media: Ethernet autoselect (none)
            status: no carrier
    pflog0: flags=100 <promisc>metric 0 mtu 33128
    enc0: flags=0<> metric 0 mtu 1536
    lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
            options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 
            inet6 ::1 prefixlen 128 
            inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 
            nd6 options=3 <performnud,accept_rtadv>pfsync0: flags=0<> metric 0 mtu 1460
            syncpeer: 224.0.0.240 maxupd: 128
    lagg0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:07:e9:04:5f:8a
            inet6 fe80::207:e9ff:fe04:5f8a%lagg0 prefixlen 64 scopeid 0x9 
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
            status: active
            laggproto fec
            laggport: em1 flags=4 <active>laggport: em0 flags=4 <active>lagg0_vlan2: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=3 <rxcsum,txcsum>ether 00:07:e9:04:5f:8a
            inet6 fe80::202:b3ff:feb7:bf7d%lagg0_vlan2 prefixlen 64 scopeid 0xa 
            inet 172.16.45.1 netmask 0xffffff00 broadcast 172.16.45.255
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
            status: active
            vlan: 2 parent interface: lagg0
    lagg0_vlan3: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=3 <rxcsum,txcsum>ether 00:07:e9:04:5f:8a
            inet6 fe80::202:b3ff:feb7:bf7d%lagg0_vlan3 prefixlen 64 scopeid 0xb 
            inet 172.16.46.1 netmask 0xffffff00 broadcast 172.16.46.255
            nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
            status: active
            vlan: 3 parent interface: lagg0</performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></active></active></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic></broadcast,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast> 
    


  • Can you please run this under Diagnostic->Command Promt php section:

    require_once("globals.inc");

    var_dump(get_nics_with_capabilities("vlanmtu"));

    ?>



  • Here's the output with my hacks removed:

    
    array(2) {
      [0]=>
      string(2) "em"
      [1]=>
      string(3) "fxp"
    }
    
    


  • Can you give me some kind of remote access to verify?!

    It works for me locally so i have to look in your environment.



  • I can replicate that, it's only an issue with FEC. http://redmine.pfsense.org/issues/1123



  • Can you please try latest snapshots it should work ok now.



  • Yup, looks like 2.0-BETA4 from 12/23/2010 does indeed fix the problem. Thanks!


Locked