Add 't0-56' testbed_type for decap.#1001
Open
iris00522 wants to merge 2 commits intosonic-net:masterfrom
Open
Conversation
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…net#3424) Submodule src/sonic-sairedis 4ee82cb..1cf2eea: > Add acl counter match logic based on acl entry field (sonic-net#511) > Add specific comparison logic for ACL counter (sonic-net#484) Submodule src/sonic-swss 46bc1f4..660530e: > Fix VLAN error introduced with new 4.9 kernel behavior (sonic-net#1001) > Warmboot Vlan neigh restore fix (sonic-net#1040) Submodule src/sonic-utilities 11b4cf1..f76fc2c: > [warm reboot] Skip ASIC config pre-check if current image does not support it (sonic-net#637) > [FastReboot]: Send SIGINT to all teamd before stop (sonic-net#633) > [warm/fast reboot] provide strict option to prevent warm reboot under certain conditions (sonic-net#631) Signed-off-by: Ying Xie <[email protected]>
sdszhang
pushed a commit
to sdszhang/sonic-mgmt
that referenced
this pull request
Mar 23, 2026
…c-net#1001) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: PTF may see multiple default IPv6 routes coming from DUT due to RA packets. which will cause a routing issue on the PTF for IPv6 packets as the traffic may be sent to DUT unexpectedly. One example is that the ipv6 traffic coming in via mgmt interface, may choose one of the interfaces towards DUT to send the traffic back which is not intended. This PR fix this routing behavior so that PTF doesn't rely on default routes learned via RA from DUT interfaces. following is the output in PTF when RA routes are accepted on eth interfaces. ``` root@41d9f9447440:~# ip -6 route ...... default via fe80::a67a:72ff:fe55:1efc dev eth113 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth129 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth144 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth64 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth101 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth121 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth80 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth124 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth104 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth72 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth112 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth97 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth89 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth128 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth36 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth81 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth120 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth69 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth100 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth32 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth109 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth76 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth85 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth84 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth125 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth61 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth116 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth108 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth92 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth88 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth148 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth68 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth105 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth77 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth73 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth117 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth96 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth65 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth93 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium default via fe80::a67a:72ff:fe55:1efc dev eth60 proto ra metric 1024 expires 530sec mtu 9100 hoplimit 64 pref medium root@41d9f9447440:~# ``` ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 ### Approach #### What is the motivation for this PR? Fix mgmt routing issue for PTF container #### How did you do it? disable accept_ra_defrtr flag for ethxxx interfaces in PTF. #### How did you verify/test it? local testbed. #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
when deploy the topo: t0-56 and run the decap test case, it causes the error: ERROR! 'props' is undefined.
Type of change
[] Bug fix
[] Testbed and Framework(new/improvement)
[+] Test case(new/improvement)
Approach
How did you do it?
Add 't0-56' testbed_type for decap.
How did you verify/test it?
Tested on the broadcom platform.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation