20 ms·
If I have AS22, advertising 2.2.2.0/24 out of NY, then I can reach 1.1.1.1, great I then have 2.2.3.0/24 advertised out of Frankfurt with the same AS. Again I
by midasuni 3y ago
If I have AS22, advertising 2.2.2.0/24 out of NY, then I can reach 1.1.1.1, great
I then have 2.2.3.0/24 advertised out of Frankfurt with the same AS. Again I have transit. I can reach 1.1.1.1.
How does a packet from 2.2.2.1 reach 2.2.3.1 -— 2.2.3.0 won’t be advertised by the transit to me in NY as it thinks I’ve already got the route, after all it originated from my AS.
- ericpauley 3y agoPresumably since these IPs are in the same AS the operator can implement custom routing logic, since they control the routing on both sides.
- zajio1am 3y agoOn BGP protocol level, the loop check is on the receiving side - received paths are scanned for local ASN. The transit may not send you your routes with your ASN due to how its policies are configured, but that is configurable, not protocol-level issue. And most BGP implementations have knobs to disable the loop check, so on your side you could just disable it.
- Hikikomori 3y agoThey could have something to connect their sites, or even tunnel between them over their transit. But if they only have customers on their network, likely behind nat, they don't need to reach each other.
- kiallmacinnes 3y agoPeer to peer? Self hosted stuff? (not sure how these work with starlink specifically, but - they should work, even if for whatever reason they don't)
- Hikikomori 3y agoAfaik you don't get your own public IPv4 address on Starlink.
- lxgr 3y agoAs far as I know, inbound TCP/UDP connections are not supported on Starlink natively. You can of course use a VPN or various types of reverse port forwarding. That said, you can often still communicate between two NATs using various traversal techniques, although that's generally less likely for carrier-grade NATs, so NAT traversal solutions usually need relays as a fallback anyway.