Actions
Bug #8446
closedQinQ interfaces are assigned incorrectly
Start date:
04/08/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.3
Affected Architecture:
All
Description
When creating a QinQ interface in 2.4.3 it is stored in the config correctly and created as an interface as expected:
<qinqentry> <if>em0</if> <tag>100</tag> <members>200</members> <descr><![CDATA[test wan]]></descr> <vlanif>em0.100</vlanif> </qinqentry>
em0.100.200: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=28<VLAN_MTU,JUMBO_MTU> ether 00:90:7f:87:dc:75 inet6 fe80::290:7fff:fe87:dc75%em0.100.200 prefixlen 64 scopeid 0x10 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active
But when selecting that device to assign it in the GUI the resulting config is still using the old notation:
<opt2> <descr><![CDATA[OPT2]]></descr> <if>em0.100_200</if> <enable></enable> <spoofmac></spoofmac> </opt2>
Which results in expected failure:
Apr 9 01:03:35 php-fpm 8969 /interfaces_assign.php: The command '/sbin/ifconfig 'em0.100_200' -staticarp ' returned exit code '1', the output was 'ifconfig: interface em0.100_200 does not exist' Apr 9 01:03:35 php-fpm 8969 /interfaces_assign.php: The command '/usr/sbin/arp -d -i 'em0.100_200' -a > /dev/null 2>&1 ' returned exit code '1', the output was ''
That config updated correctly top the new notation and functioned but the GUI showed the parent interface only, see pic. Selecting the expected QinQ port broke the config.
Files
Actions