Bug #7942
closedQinQ interfaces never show as active
100%
Description
In a fresh 2.4 install QinQ interfaces always show in Status > Interfaces as down even when the parent interface shows as up.
No traffic passes.
QINQ Interface (opt3, igb5_50_25) Status down
igb5_50: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:08:a2:09:31:07 inet6 fe80::208:a2ff:fe09:3107%igb5_50 prefixlen 64 scopeid 0xb nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan: 50 vlanpcp: 0 parent interface: igb5 groups: vlan
igb5: flags=28943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC> metric 0 mtu 1500 options=6500bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:08:a2:09:31:07 hwaddr 00:08:a2:09:31:07 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active
<qinqs> <qinqentry> <if>igb5</if> <tag>50</tag> <members>25</members> <descr><![CDATA[Test QinQ 25]]></descr> <vlanif>igb5_50</vlanif> </qinqentry> </qinqs>
Updated by Steve Wheeler almost 7 years ago
[2.4.0-RELEASE][root@4860.stevew.lan]/root: cat /tmp/netgraphcmd shutdown igb5_50qinq: mkpeer igb5_50: vlan lower downstream name igb5_50:lower igb5_50qinq connect igb5_50: igb5_50qinq: upper nomatch shutdown igb5_50h25: mkpeer igb5_50qinq: eiface igb5_5025 ether name igb5_50qinq:igb5_5025 igb5_50h25 msg igb5_50qinq: addfilter { vlan=25 hook="igb5_5025" } msg igb5_50h25: setifname "igb5_50_25" msg igb5_50h25: set 00:08:a2:09:31:07
Updated by Luiz Souza almost 7 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Please, test again when the next snapshot is ready.
It is fixed and updated to use the same name format as VLANs.
It is still possible to create interfaces with names biggers than 15 characters, it will silently ignore these (to not break the system later).
Updated by Jim Pingle almost 7 years ago
- Status changed from Feedback to Confirmed
- Target version changed from 2.4.1 to 2.4.2
Apparently this still has some issues:
Azamat: Created QinQ interface: OPT2 Interface (opt2, igb1_201_666) on SG-2220 with 2.3.3_p1 - Interface status was UP. Made an update to 2.4.0 - interface status became Down. After update to current snap 2.4.1.a.20171017.2141 interface status became UP again. During tests on 2.3.3_p1 and 2.4.0-RELEASE, reboot process deleted assigned QinQ interfaces. Update from 2.4.0 to 2.4.1 deleted assigned QinQ interfaces too.
- I connected two pfSenses (SG-2220 and SG-4860) with 2.4.1.a.2017017.2141 through their LAN interfaces. Then I created QinQ on both and PCAP showed me that traffic between these two pfSenses are double-tagged.
BUT rebooting still deletes all QinQ assigned interfaces. I tried to assign only OPT5=(opt2, igb1_201) without assigning (opt2, igb1_201_666) - after reboot interface OPT5 was deleted anyway."
Updated by Jim Pingle almost 7 years ago
- Category set to Interfaces
- % Done changed from 100 to 50
- Affected Architecture All added
- Affected Architecture deleted (
)
Updated by Luiz Souza almost 7 years ago
- Status changed from Confirmed to Feedback
A few commits were made to address QinQ general issues.
This issue has to tested again.
Updated by Luiz Souza almost 7 years ago
- Status changed from Feedback to Resolved
- % Done changed from 50 to 100