Updating on the below incase someone else has the same issue.
It looks like Starlink rolled out a firmware update on Gen1 dish's and that has stopped it working with 3rd party routers. Hoping it's a bug and they fix it promptly.
Hi,
I've had Starlink running perfectly on Opnsense for 18 months and at 3am the other morning it dropped out and I haven't been able to get it to reconnect in Opnsense since.
Hoping someone might be able to point me in the right direction.
It's a Gen1 version.
I've tested the Starlink dish by going back to the Starlink router and it connects and works perfectly.
All using the same cables, just plugged into the original router instead.
I've removed all the Starlink setup from Opnsense and redone all the setup again, but still to no avail.
Below is the section of the logs from when I reboot the dish to when the link goes down.
It's like it connects, then fails.
I know my way around Opnsense and basic networking, but this one has me stumped.
I'm running version 24.1.4 of Opnsense.
Any advice would be thankfully received. I don't want to have to go back to using the Starlink router.
Thanks
Simon
Quote2024-03-22T16:38:51 Notice kernel <6>igb5: link state changed to DOWN
2024-03-22T16:38:51 Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for opt1(igb5)
2024-03-22T16:38:30 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.119.167.194, old: 100.119.167.194, interface: opt1, device: igb5, force: yes)
2024-03-22T16:38:29 Notice dhclient dhclient-script: New Classless Static Routes (igb5): 192.168.100.1/32 0.0.0.0 34.120.255.244/32 0.0.0.0 default 100.64.0.1
2024-03-22T16:38:29 Notice dhclient dhclient-script: New Routers (igb5): 100.64.0.1
2024-03-22T16:38:29 Notice dhclient dhclient-script: New Broadcast Address (igb5): 100.127.255.255
2024-03-22T16:38:29 Notice dhclient dhclient-script: New Subnet Mask (igb5): 255.192.0.0
2024-03-22T16:38:29 Notice dhclient dhclient-script: New IP Address (igb5): 100.119.167.194
2024-03-22T16:38:29 Notice dhclient dhclient-script: Reason REBOOT on igb5 executing
2024-03-22T16:38:29 Notice dhclient dhclient-script: Reason PREINIT on igb5 executing
2024-03-22T16:38:29 Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt1(igb5)
2024-03-22T16:38:29 Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for opt1(igb5)
2024-03-22T16:38:26 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.119.167.194, old: 100.119.167.194, interface: opt1, device: igb5, force: yes)
2024-03-22T16:38:26 Notice dhclient dhclient-script: New Classless Static Routes (igb5): 192.168.100.1/32 0.0.0.0 34.120.255.244/32 0.0.0.0 default 100.64.0.1
2024-03-22T16:38:26 Notice dhclient dhclient-script: New Routers (igb5): 100.64.0.1
2024-03-22T16:38:26 Notice dhclient dhclient-script: New Broadcast Address (igb5): 100.127.255.255
2024-03-22T16:38:26 Notice dhclient dhclient-script: New Subnet Mask (igb5): 255.192.0.0
2024-03-22T16:38:26 Notice dhclient dhclient-script: New IP Address (igb5): 100.119.167.194
2024-03-22T16:38:26 Notice dhclient dhclient-script: Reason BOUND on igb5 executing
2024-03-22T16:38:25 Notice dhclient dhclient-script: Reason ARPCHECK on igb5 executing
2024-03-22T16:38:23 Notice dhclient dhclient-script: Reason ARPSEND on igb5 executing
2024-03-22T16:37:33 Notice kernel <6>igb5: link state changed to UP
2024-03-22T16:37:33 Notice dhclient dhclient-script: Reason PREINIT on igb5 executing
2024-03-22T16:37:33 Notice dhclient dhclient-script: Reason EXPIRE on igb5 executing
2024-03-22T16:37:29 Notice kernel <6>igb5: link state changed to DOWN
2024-03-22T16:37:21 Notice dhclient dhclient-script: Reason PREINIT on igb5 executing
2024-03-22T16:37:21 Notice dhclient dhclient-script: Reason EXPIRE on igb5 executing
2024-03-22T16:37:21 Notice dhclient dhclient-script: Reason PREINIT on igb5 executing
2024-03-22T16:37:20 Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt1(igb5)
2024-03-22T16:37:20 Notice kernel <6>igb5: link state changed to UP
Thanks for posting this (and the update!) I had a client down due to this yesterday, and could only isolate it to something going on with Starlink.
I found this reddit post that suggests if you boot the dishy up connected to the stock router, once it's been up for a few minutes, you can remove it and put your own 3rd party router back in. Then it should work until the next time the dishy reboots: https://www.reddit.com/r/Starlink/comments/1bjr8yf/how_i_mostly_got_back_to_normal_with_a_gen1_the/
Also found this unofficial starlink-related site stating the problem: https://www.starlinkhardware.com/firmware-updates/
Hopefully this gets fixed soon.