would appreciate some help. i suspect goog fiber is announcing inconsistently. i wrote to noc@googlefiber.net and crickets. vm0.dfw.rg.net:/home/randy> traceroute6 2605:a601:f70:f0::1 traceroute to 2605:a601:f70:f0::1 (2605:a601:f70:f0::1), 30 hops max, 80 byte packets 1 r1.dfw.rg.net (2001:418:3807::2) 0.210 ms 0.214 ms 0.195 ms 2 r2.dfw.rg.net (2001:418:3807::3) 1.019 ms 1.085 ms 1.195 ms 3 * * * 4 * * * 5 e0-36.core1.aus1.he.net (2001:470:0:4ae::2) 5.713 ms 6.085 ms 6.421 ms 6 * * * 7 * * * 8 * * * 9 * * * atlas essenitally says no route, see attached porn (or https://archive.psg.com/250912.gf-traces.jpg in case list does not allow). and see https://atlas.ripe.net/measurements/128265158/ but rv says gf announces the /31 route-views>show bgp ipv6 unicast 2605:a601:f70:f0::1/31 BGP routing table entry for 2605:A600::/31, version 593974717 Paths: (12 available, best #6, table default) Not advertised to any peer Refresh Epoch 1 8283 6939 16591 2A02:898:0:300::3 from 2A02:898:0:300::3 (94.142.247.3) Origin IGP, localpref 100, valid, external Community: 0:714 0:2906 0:6939 0:12876 0:12989 0:13335 0:15133 0:15169 0:16265 0:16276 0:16509 0:20940 0:22822 0:32590 0:48641 0:49029 0:57363 8283:1 8283:101 8283:102 unknown transitive attribute: flag 0xE0 type 0x20 length 0x30 value 0000 205B 0000 0000 0000 0001 0000 205B 0000 0005 0000 0001 0000 205B 0000 0005 0000 0002 0000 205B 0000 0008 0000 0DB8 path 7F15FFE82328 RPKI State valid rx pathid: 0, tx pathid: 0 Refresh Epoch 1 49788 6939 16591 2A02:D140:1::60 from 2A02:D140:1::60 (91.218.184.60) Origin IGP, localpref 100, valid, external path 7F158F908DB8 RPKI State valid rx pathid: 0, tx pathid: 0 Refresh Epoch 1 20912 6939 16591 2001:40D0::1E from 2001:40D0::1E (77.39.192.1) Origin IGP, localpref 100, valid, external Community: 20912:65002 20912:65021 path 7F15745050D8 RPKI State valid rx pathid: 0, tx pathid: 0 and many more i is as if they are announcing to rv but not peers. but that is pure conjecture. randy
Once upon a time, Randy Bush <randy@psg.com> said:
would appreciate some help. i suspect goog fiber is announcing inconsistently. i wrote to noc@googlefiber.net and crickets.
vm0.dfw.rg.net:/home/randy> traceroute6 2605:a601:f70:f0::1
I'm not able to reach that from my Google Fiber home connection in Huntsville, AL... it goes nowhere past my router. It doesn't appear that it's being routed even inside their network. I see the /31 on multiple route servers (and my home is in that /31). -- Chris Adams <cma@cmadams.net>
Chris Adams via NANOG wrote:
vm0.dfw.rg.net:/home/randy> traceroute6 2605:a601:f70:f0::1
I'm not able to reach that from my Google Fiber home connection in Huntsville, AL... it goes nowhere past my router. It doesn't appear that it's being routed even inside their network.
I see the /31 on multiple route servers (and my home is in that /31).
thanks! what do you see in a traceroute? i wonder if there is an acl randy
Once upon a time, Randy Bush <randy@psg.com> said:
Chris Adams via NANOG wrote:
vm0.dfw.rg.net:/home/randy> traceroute6 2605:a601:f70:f0::1 I'm not able to reach that from my Google Fiber home connection in Huntsville, AL... it goes nowhere past my router. It doesn't appear that it's being routed even inside their network.
I see the /31 on multiple route servers (and my home is in that /31).
thanks!
what do you see in a traceroute?
i wonder if there is an acl
All my traceroutes (from inside or out) stop at the last non-Google Fiber hop. For example, from my home router: traceroute to 2605:a601:f70:f0::1 (2605:a601:f70:f0::1), 30 hops max, 72 byte packets 1 * * * -- Chris Adams <cma@cmadams.net>
All my traceroutes (from inside or out) stop at the last non-Google Fiber hop. For example, from my home router:
traceroute to 2605:a601:f70:f0::1 (2605:a601:f70:f0::1), 30 hops max, 72 byte packets 1 * * *
i think that is because the target is google business fiber and you're home fiber. atlas TraceMON (for 128292864) from within google fiber sure looks this way https://archive.psg.com/250912.intra-gf-traces.jpg randy
On 12.09.2025 16:58 Randy Bush via NANOG <nanog@lists.nanog.org> wrote:
i think that is because the target is google business fiber and you're home fiber.
Why should that matter for routing tables? Should home users be unable to access business customer's services? -- kind regards Marco Send spam to abfall1757689109@stinkedores.dorfdsl.de
i think that is because the target is google business fiber and you're home fiber. Why should that matter for routing tables?
intra-AS bgp kink can be extreme, even without confed
Should home users be unable to access business customer's services?
yes. but the one i am trying to help diagnose seems not. randy
i think that is because the target is google business fiber and you're home fiber. Why should that matter for routing tables?
maybe you did not look at the ripe atlas tracemon https://archive.psg.com/250912.intra-gf-traces.jpg which is a set of traces from probes ONLY WITHIN GOOGLE FIBER AS. it shows one probe set able to reach the target and a lot of others not able to reach it. therefore the guess is that google fiber has at least two routing domains. the target is a google business fiber customer. and up-thread you will see a google home fiber unable to reach the target. oh, and this is v6 only. the target is reachable from anywhere in v4. and the user, a friend, says this has been going on for months, with google fiber unable to debug it. randy
FYI, my team is on it. Louie On Sat, Sep 13, 2025 at 3:35 AM Randy Bush via NANOG <nanog@lists.nanog.org> wrote:
i think that is because the target is google business fiber and you're home fiber. Why should that matter for routing tables?
maybe you did not look at the ripe atlas tracemon
https://archive.psg.com/250912.intra-gf-traces.jpg
which is a set of traces from probes ONLY WITHIN GOOGLE FIBER AS.
it shows one probe set able to reach the target and a lot of others not able to reach it. therefore the guess is that google fiber has at least two routing domains.
the target is a google business fiber customer. and up-thread you will see a google home fiber unable to reach the target.
oh, and this is v6 only. the target is reachable from anywhere in v4.
and the user, a friend, says this has been going on for months, with google fiber unable to debug it.
randy _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/ZXXDLZ2R...
just to close this. louie and crew fixed this problem. yay! and thanks. randy
participants (4)
-
Chris Adams -
Louie Lee -
Marco Moock -
Randy Bush