Starlink moved us to 2025.07.13.mr59602 from 2025.07.25.mr60394. Lets hope this works. Will update on more info when it comes in
Issue presented one more time yestarday. Starlink did something and now its stable. Sounds like they will be fixing this in the next few updated. I did loose telemetry into IC2. But I am not to worried about that as I just need the data to work.
Yes, this is the issue we have… starlink’s response was:
“Since Starlink advises against placing a switch before the router, or connecting the switch directly to the power supply, the update will not provide any change that would be aimed towards addressing that sort of network setup.”
I’m having the same problem with the HP Articulated Dishy
@KPS-ps ,
When Starlink is in router mode, you won’t encounter the issue because the router-mode device filters all ARP packets.
In bridge mode, however, any unwanted ARP traffic can potentially disrupt ARP mapping for the Starlink user terminal (UT). The Starlink Engineering team has confirmed the issue and is currently working on a fix.
The reason LAN client traffic is not functioning properly is that the Starlink UT maps the wrong MAC address when replying to packets. The Peplink router will not accept such traffic or forward it to the LAN. However, if packets are sent directly from the WAN interface, which operates at Layer 2 (L2), those packets are still accepted.
1 Like
I believe Starlink Level 1 and Level 2 Support may have provided incorrect information. Starlink’s WAN is used by many enterprise customers who connect Starlik UT device via a switch.
1 Like
If you are experiencing the issue, please create a ticket at Peplink Ticketing System and address it to Sitloongs. I will try to connect you with the appropriate Starlink team to implement a temporary workaround until Starlink releases the official fix.
1 Like
Wow thanks so much for the care! I’ve already wired it direct to the BR1 in my attic. I’ll crawl back up there once they’ve fixed it. I’ll keep an eye on this thread in the meantime.