Starlink seems to have had a reboot of its own accord.. i'm gonna guess a middle of the night firmware update. anyway, router was sat stuck again. This is the output from "ip dhcpc status"

DHCP Server IP : 0.0.0.0
WAN IP : 192.168.100.100
WAN Netmask : 255.255.255.0
WAN Gateway : 192.168.100.1
Primary DNS : 192.168.100.1
Secondary DNS : 0.0.0.0
Leased Time : 5
Leased Time T1 : 2
Leased Time T2 : 0
Leased Elapsed : 0
Leased Elapsed T1: 0
Leased Elapsed T2: 0

values stuck at those for 20 mins!


then after me poking it and a "ip dhcpc release 2" it sorted itself to...

DHCP Server IP : 0.0.0.0
WAN IP : 100.69.xxx.xxx
WAN Netmask : 255.192.0.0
WAN Gateway : 100.127.255.1
Primary DNS : 8.8.8.8
Secondary DNS : 8.8.4.4
Leased Time : 300
Leased Time T1 : 150
Leased Time T2 : 259
Leased Elapsed : 252
Leased Elapsed T1: 102
Leased Elapsed T2: 211

Now i have sensible looking values for elapsed time that actually update!

finally got around to messing with where Dishy was pointed. powered it off and while faffing, intentionally put it back tilted towards the north. it turned itself around to the same just off south orientation it has had since setting it up.

jadzy wrote:
This is the output from "ip dhcpc status"

DHCP Server IP : 0.0.0.0
WAN IP : 192.168.100.100
WAN Netmask : 255.255.255.0

etc

then after me poking it and a "ip dhcpc release 2" it sorted itself to...

DHCP Server IP : 0.0.0.0
WAN IP : 100.69.xxx.xxx
WAN Netmask : 255.192.0.0

etc

I suppose you could attach a PC directly to the Starlink 'Dishy' - just to see if it behaves the same way as the 2862, or if it does what it ought to do and gets a 'proper' lease of its own accord.

The Wan IP address is interesting (though I doubt it's related to the problem)...

remarks: 100.64.0.0/10 reserved for Shared Address Space
remarks: [RFC6598]. Complete registration details for
remarks: 100.64.0.0/10 are found iniana-ipv4-special-registry.

Summary: IP Address 100.69.1.2 is a public IP address but at this moment it is not configured in the global routing table.

Makes you wonder how it's working at all

Guess you guys don't care about the ruination of the night sky then.... :?

https://www.newscientist.com/article/mg25133480-100-why-it-is-so-important-to-protect-access-to-the-dark-night-sky/

Starlink uses cgnat. hence the odd IPs it gives. You'd think with the crazy money they're spending they could afford some proper IPv4 address, but no. IPv6 isn't officially offered yet, and is a bit flaky.

Piste Basher wrote:
Guess you guys don't care about the ruination of the night sky then.... :?

I love the Dark Skies of North Devon; it makes it so much easier to watch the satellites zooming by.