Bug #4186
closed
VLANs on lagg not configurable with FEC, LB and RR modes
0%
Description
Hi,
i created different variants (simple virtualbox (3× pcn, 3x em), lanner 7535 (6x EM), supermicro c2758 board (6x igb) default installations with pfsense 2.2 RC or pfsense RC snapshot from 5th of january (other snapshots not tested)
Now i added several combinations of lagg interfaces.
None of the combinations allowed me to created tagged interfaces in top of the lagg interface.
With pfsense 2.1 the lanner was fine with vlan tagging on lagg. The tagging still works when importing old config part from XML or manually editing it in XML file.
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Feedback
what do you mean it doesn't allow you to create tagged interfaces on the lagg? That works fine, we have several systems running that way and I just setup another one as a test, all good.
Updated by Ron Hubert almost 10 years ago
For me it is not possible to create a vlan tag on top of the lagg0 interface. I am currently investigating /etc/inc/interfaces.inc since there is the function is_vlan_capable, which checks for vlanmtu. I did not change any mtu settings , should I? Both lagg0 and lagg0_vlanXXX show mtu 1500, But the VLAN_MTU flag is present.
The following ifconfig output is from the current running (supermicro c2758) system, which I configured by editing xml-config file myself adding lagg0_vlan1001:
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether XX:XX:XX:XX:XX:XX
inet6 fe80::XXXX:XXff:feXX:XXXX%lagg0 prefixlen 64 scopeid 0x9
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
laggproto loadbalance lagghash l2,l3,l4
laggport: igb3 flags=4<ACTIVE>
laggport: igb2 flags=4<ACTIVE>
laggport: igb1 flags=4<ACTIVE>
lagg0_vlan1001: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3<RXCSUM,TXCSUM>
ether XX:XX:XX:XX:XX:XX
inet6 fe80::XXXX:XXXX:XXXX:XXXX%lagg0_vlan1001 prefixlen 64 scopeid 0xa
inet 10.XXX.XXX.5 netmask 0xffff0000 broadcast 10.XXX.255.255
inet 10.XXX.XXX.36 netmask 0xffff0000 broadcast 10.XXX.255.255 vhid 1
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 1001 vlanpcp: 0 parent interface: lagg0
carp: MASTER vhid 1 advbase 2 advskew 0
Sorry if I did something wrong or forgot something. But in the former 2.1 release on my old lanner board it was possible to define the vlans through the web interface. With that it is not possible to do it through the web interface too, the only difference is that there I have three em0 in the lag group instead of the three igb's. I am sorry that I cannot test 2.1 on the supermicro c2758, I think there was the problem with the unsupported igb in freebsd 8.3 in former times.
Updated by Ron Hubert almost 10 years ago
To be more precise: The drop down boxes on interface_vlan_edit.php only show igb0 to igb3, but not lagg0.
Updated by Chris Buechler almost 10 years ago
- Subject changed from Web interface does not allow to tag lag interface sinsige update to 2.2 various snapshots to VLANs on lagg not configurable with FEC, LB and RR modes
- Status changed from Feedback to Confirmed
Thanks, that's what I was wondering. It's 3 of the modes where lagg stops reporting itself as VLAN-capable.
Updated by Chris Buechler almost 10 years ago
- Status changed from Confirmed to Feedback
Added a workaround for this.