Open vivekrnv opened 11 months ago
@yaqiangz @yxieca @kellyyeh, Please check
@vivekrnv I wonder whether we can confirm the advertise and reply packets is actually send to client in scenario you mentioned?
yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface
yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface
From dump file you shared, seems this is a ToRRouter? Could you share more details about this use case like why tagged is needed to let me fully understand this scenario?
@vivekrnv please confirm this is a valid scenario
yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface
From dump file you shared, seems this is a ToRRouter? Could you share more details about this use case like why tagged is needed to let me fully understand this scenario?
@yaqiangz , good point. Seems trunk vlan is not a general use case. Keeping the issue as open, as documentation
Description
With this new ability https://github.com/sonic-net/sonic-dhcp-relay/pull/43 to see dhcp_relay counters in Physical interfaces in addition to L3 Vlan interface, I can't see Reply and Advertise counters rising on Physical interfaces connected to dhcp client, But I can see it on L3 Vlan interace.
The sonic-mgmt test covers this scenario, but for untagged interfaces.
Setup description
dhcp client -> Ethernet4 -> Vlan2024 -> Ethernet0 -> dhcp server
Steps to reproduce
1) Configure interfaces to IPv6 DHCP server and Client 2) Configure IPv6 dhcp_ 3) Request IPv6 address from ipv6 client 4) check IPv6 dhcp relay counters