…-net#21062)

[smart-switch][dpu] Do not run dhclient on the eth0 interface.

…D automatically (sonic-net#21165)

#### Why I did it
src/sonic-platform-daemons
```
* 60e7224 - (HEAD -> 202411, origin/test_202411_20, origin/test_202411_100, origin/kperumal_202411, origin/202411) thermalctld: Add support for fans on non-CPU modules (sonic-net#555) (11 days ago) [Patrick MacArthur]
```
#### How I did it
#### How to verify it
#### Description for the changelog

…ically (sonic-net#21163)

#### Why I did it
src/sonic-dbsyncd
```
* b0ea01f - (HEAD -> 202411, origin/test_202411_20, origin/test_202411_100, origin/master, origin/kperumal_202411, origin/HEAD, origin/202411, master) [lldp]Fix the issue of only one field lldp_rem_time_mark in APPL_DB (sonic-net#71) (13 days ago) [Zhaohui Sun]
```
#### How I did it
#### How to verify it
#### Description for the changelog

sonic-net#21162)

[202411][submodule] Update submodule linkmgrd to the latest HEAD automatically (sonic-net#21162)

…tomatically (sonic-net#21164)

[submodule][202411] Update submodule sonic-linux-kernel to the latest HEAD automatically

…tically (sonic-net#21166)

[submodule][202411] Update submodule sonic-sairedis to the latest HEAD automatically

…omatically (sonic-net#21168)

[submodule][202411] Update submodule sonic-swss-common to the latest HEAD automatically

…atically (sonic-net#21169)

[submodule][202411] Update submodule sonic-utilities to the latest HEAD automatically

FRR 10.0.1 upgrade (sonic-net#20269) brought in a mgmtd daemon for FRR. This needs to be started up in docker-sonic-vs as part of the other daemons in this container.

Additionally, Debian Bookworm provides version 2.5.0 of scapy, but the pip3 command later in the file downgraded it to 2.4.5, which does not work in Bookworm. Fix this by removing the pip3 installation for scapy, and updating the other packages installed via pip3.

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>

Initial 202411 release

Signed-off-by: Anand Mehra anamehra@cisco.com

Why I did it
dhcp_relay/test_dhcp_relay_stress.py::test_dhcp_relay_stress[offer|ack] tests are failing on dualtor topologies with signature Failed: /tmp/dhcp_stress_test_offer.json is missing, see issue aristanetworks/sonic-qual.msft#325 for more details.

Work item tracking
Microsoft ADO (number only):
How I did it
count_matched_packets method is getting stuck in a while loop as long as ptf server port receives any packet (Ex: in dualtor case, we do see continuous ICMP packets on ptf port). Fix is to consider only expected packets w.r.t timeout (similar to count_matched_packets_all_ports logic).

How to verify it
With this PR changes we should not see dhcp_relay/test_dhcp_relay_stress.py failures on dualtor topologies with symptom Failed: /tmp/dhcp_stress_test_offer.json is missing.

…tically (sonic-net#21302)

[submodule] Update submodule sonic-sairedis to the latest HEAD automatically

…ly (sonic-net#21301)

[submodule][202411] Update submodule dhcprelay to the latest HEAD

…sonic-net#21300)

[submodule][202411] Update submodule dhcpmon to the latest HEAD

…-net#487)

This reverts commit 08f1083.

…atically

…ic-utilities

[submodule][202412] Update submodule sonic-utilities to the latest HEAD automatically

…ic-swss

[submodule][202412] Update submodule sonic-swss to the latest HEAD automatically

[202411]Adding sonic_version file

…tically

…ic-sairedis

[submodule][202412] Update submodule sonic-sairedis to the latest HEAD automatically

Update submodule branches to 202412 and 202411 if not forked.

<!--
     Please make sure you've read and understood our contributing guidelines:
     https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

     ** Make sure all your commits include a signature generated with `git commit -s` **

     If this is a bug fix, make sure your description includes "fixes #xxxx", or
     "closes #xxxx" or "resolves #xxxx"

     Please provide the following information:
-->

#### Why I did it

Adding the below fix from FRR FRRouting/frr#17297

This is to fix the following crash which is a statistical issue

```
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/frr/zebra -A 127.0.0.1 -s 90000000 -M dplane_fpm_nl -M snmp'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fccd7351e2c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
[Current thread is 1 (Thread 0x7fccd6faf7c0 (LWP 36))]
(gdb) bt
#0  0x00007fccd7351e2c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fccd7302fb2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007fccd72ed472 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007fccd75bb3a9 in _zlog_assert_failed (xref=xref@entry=0x7fccd7652380 <_xref.16>, extra=extra@entry=0x0) at ../lib/zlog.c:678
#4  0x00007fccd759b2fe in route_node_delete (node=<optimized out>) at ../lib/table.c:352
#5  0x00007fccd759b445 in route_unlock_node (node=0x0) at ../lib/table.h:258
#6  route_next (node=<optimized out>) at ../lib/table.c:436
#7  route_next (node=node@entry=0x56029d89e560) at ../lib/table.c:410
#8  0x000056029b6b6b7a in if_lookup_by_name_per_ns (ns=ns@entry=0x56029d873d90, ifname=ifname@entry=0x7fccc0029340 "PortChannel1020")
    at ../zebra/interface.c:312
#9  0x000056029b6b8b36 in zebra_if_dplane_ifp_handling (ctx=0x7fccc0029310) at ../zebra/interface.c:1867
#10 zebra_if_dplane_result (ctx=0x7fccc0029310) at ../zebra/interface.c:2221
#11 0x000056029b7137a9 in rib_process_dplane_results (thread=<optimized out>) at ../zebra/zebra_rib.c:4810
#12 0x00007fccd75a0e0d in thread_call (thread=thread@entry=0x7ffe8e553cc0) at ../lib/thread.c:1990
#13 0x00007fccd7559368 in frr_run (master=0x56029d65a040) at ../lib/libfrr.c:1198
#14 0x000056029b6ac317 in main (argc=9, argv=0x7ffe8e5540d8) at ../zebra/main.c:478
```

##### Work item tracking
- Microsoft ADO **(number only)**:

#### How I did it
Added patch.

#### How to verify it
Running BGP tests.

<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->

#### Which release branch to backport (provide reason below if selected)

<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->

- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211
- [ ] 202305

#### Tested branch (Please provide the tested image version)

<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->

- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->

#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->

<!--
 Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->

#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->

#### A picture of a cute animal (not mandatory but encouraged)

…1095

[action] [PR:21095] [FRR]Fixing zebra to use internal rbtree per NS tree of ifps

…e via Netlink to fpmsyncd

What I did:
Added patch in FRR to send tag value associated with route via NETLINK RTA_PRIORITY field which can be used as attribute/metadata in fpmsyncd for different use-cases.

Why I did:
Some of use cases:
1. Do not program specific routes into APP_DB
2. Fallback to default route for specific routes.

How I verify:
Manual Verification.

…0692

[action] [PR:20692] [FRR Patch] Added patch in FRR to send tag value associated with route via Netlink to fpmsyncd

…1466

[action] [PR:21466] [YANG] SRv6 yang model followup fix

…1070

[action] [PR:21070] [sonic-mgmt-docker-image] Support ptf dataplane packet poll with multiple ptf nn agents connection

…1455

[action] [PR:21455] [Mellanox] Update SN5640 SIMX sensors.conf file

…1156

[action] [PR:21156] Add SRv6 support in Bgpcfgd

…d for modules that does not support this API sonic-net#21196

sonic-net#20991

…onic-net#21425

…ey as an ipv6 prefix

…agentaddress(sonic-net#20152)

…by system time change sonic-net#21446

…onic-net#20754

…onic-net#21200

…C224O8 buffers and DSCP mapping#21427

… emulation platform sonic-net#21478