3 ms·
> All Starlink customer traffic egresses via Google's network That’s not true. Customers that were getting public IPs without CGNAT were coming from a non-Goog
by kortilla 5y ago
> All Starlink customer traffic egresses via Google's network
That’s not true. Customers that were getting public IPs without CGNAT were coming from a non-Google ASN.
- JustFinishedBSG 5y agoThat doesn't mean anything, Google will announce your routes for you if you want. [1] [1] https://cloud.google.com/network-connectivity/docs/router/how-to/configuring-bgp https://cloud.google.com/network-connectivity/docs/router/ho...
- kortilla 5y agoThe google asn would still show up in the path if that were the case.
- mike_d 5y ago> That’s not true. My two Starlink terminals respectfully disagree. It has been mentioned numerous times on the Starlink forums. It's IP space previously used by Google Station.
- walrus01 5y agoboth are happening simultaneously in different areas, there are still many starlink terminals behind cgnat inside the google ASN, there are now some starlink terminals that have been giving out dhcp leases of public addresses owned/controlled by the starlink ASN, and there are also starlink terminals that have been seen doing cgnat and with an exit point in the starlink ASN. it really depends on where you are and whether your terminal has been selected by (some unknown criteria) for spacex's network topology changes.
- kortilla 5y agoDo you have public IP addresses assigned directly to your router? This was showing up on the people who got public IPs.