Description
There should be a verification for config interface ip add command in case of assigning an ip-address on a trunk port.
Steps to reproduce the issue
Add a vlan
# config vlan add 2
Add interfaces to vlan
# config vlan member add 2 -u Ethernet44# config vlan member add 2 -u Ethernet48
Assign IP addresses on trunks ports
# config interface ip add Ethernet44 192.168.1.1/24# config interface ip add Ethernet48 192.168.2.1/24
Describe the results you received
Having assigned an ip-address on a trunk port neither L2 not L3 traffic (with and without 802.1Q header) can't flow via such port.
L2 traffic is not being processed because it's a L3 port (dst mac differs from this port's mac)
But this L3 port treats all untagged traffic as tagged (see this bug [https://github.com/Azure/sonic-buildimage/issues/3943])
Describe the results you expected
There are two options:
system should prevent from assigning an ip-address on vlan member port.
having assigned ip address on trunk port, such port should stop being a trunk port (vlan member) and start to process traffic as router port.
Description There should be a verification for config interface ip add command in case of assigning an ip-address on a trunk port.
Steps to reproduce the issue
# config vlan add 2
# config vlan member add 2 -u Ethernet44
# config vlan member add 2 -u Ethernet48
# config interface ip add Ethernet44 192.168.1.1/24
# config interface ip add Ethernet48 192.168.2.1/24
Describe the results you received Having assigned an ip-address on a trunk port neither L2 not L3 traffic (with and without 802.1Q header) can't flow via such port. L2 traffic is not being processed because it's a L3 port (dst mac differs from this port's mac) But this L3 port treats all untagged traffic as tagged (see this bug [https://github.com/Azure/sonic-buildimage/issues/3943])
Describe the results you expected There are two options:
Output of
show version