@risefibre My line's path MTU is 1480, but the Icotera i4882 router leaves LAN devices at 1500 and has no MTU setting. Over IPv6, AWS-hosted services (Docker Hub, Tailscale control) stall until I hand-set each device to 1480. Can the router advertise MTU 1480 in its IPv6 RAs and clamp IPv6 MSS?
IPv6 path MTU fault report (2026-10-06)
Router: Icotera i4882-01 (ISP supplied). LAN hosts get IPv6 by router advertisement.
Headline: the line's path MTU is 1480, but LAN devices are left at 1500. Packets larger than 1480 bytes cannot cross the line. The router's IPv6 router advertisements do not lower the MTU (a Linux host with accept_ra_mtu=1 stays at 1500), and the router's web UI has no setting for it. IPv6 servers that do not act on "Packet Too Big" (several AWS us-east-1 endpoints, including Docker Hub and Netflix) send 1500-byte packets that never arrive, so connections to them stall. Docker pulls, Tailscale's control server and some sites hang until each device is set to MTU 1480 by hand.
Measurements (two LAN hosts, a Linux container and an Orange Pi, same results):
IPv6 ping with Don't Fragment to 2606:4700:4700::1111: 1480 bytes on the wire gets replies; 1500 gets "Packet too big, mtu=1480".
IPv4 ping with Don't Fragment to 8.8.4.4 at 1500 on the wire: "Frag needed and DF set (mtu = 1480)". 1480 gets replies. IPv4 path MTU discovery works; the limit is the same 1480.
docker pull busybox over IPv6 to https://t.co/fcpk8ELZwC (2600:1f18:2148::/48): 4 of 4 attempts failed with "TLS handshake timeout". The stuck socket showed the host had never received a full-size segment (rcv_mss 536).
Same pull after setting only the host's IPv6 MTU to 1480 (route cache flushed between attempts): 3 of 3 succeeded in 1.4 to 3.0 s.
Tailscale control server over IPv6: TLS handshake 3.5 s at MTU 1500, 0.06 s at 1480 (IPv4: 0.06 s).
Google, Cloudflare, Wikipedia, Facebook and Microsoft over IPv6 work at 1500. The first connection to an AWS us-east-1 IPv6 address times out, and an immediate retry succeeds once the host has cached the 1480 path MTU.
Requests:
Have the router advertise MTU 1480 in its IPv6 router advertisements (RA MTU option), or tell me how to set it; the LAN settings page does not expose it.
Clamp TCP MSS for IPv6 traffic on the WAN side, as is usual for IPv4.
Confirm why the WAN path MTU is 1480 rather than 1500 (tunnel or encapsulation on the access line), and whether a 1500 path is available.
@MichaelGannotti@huggingface@Zai_org@MiniMax_AI@deepseek_ai We definitely do, Iβve even made a mobile OS focused on agents, it runs (and builds ha) apps for Linux, Windows, Android and even Mac and iOS in a simulator. All of your agents and apps in your pocket :)