nanog mailing list archives
Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32)
From: Ca By <cb.list6 () gmail com>
Date: Wed, 27 Apr 2016 13:04:37 -0700
On Wednesday, April 27, 2016, Baptiste Jonglez <baptiste () bitsofnetworks org> wrote:
Hi, While doing statistics on the participants of a public DHT, I was surprised to see some IP addresses that are not present in the DFZ: 2607:7700:0:25::4e00:605b 2607:7700:0:25::4e25:8ce8 2607:7700:0:25::c808:db2c 2607:7700:0:4::3294:6683 2607:7700:0:4::4c09:4d39 2607:7700:0:4::5985:87d1 2607:7700:0:4::5d7d:3df8 All those IP are in 2607:7700::/32, allocated to T-Mobile USA but never announced: https://stat.ripe.net/2607%3A7700%3A%3A%2F32#tabId=at-a-glance What could explain their usage in an application? Some form of address translation? Maybe these addresses have been used as source address in outgoing packets, which would indicate IPv6 tests in T-Mobile? (but obviously, nobody is able to answer such packets). Baptiste
You see these addresses because your DHT is not supporting IP correctly. Enable ipv6 and your flaw will be resolved and you will no longer see these addresses. CB
Current thread:
- IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Baptiste Jonglez (Apr 27)
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Ca By (Apr 27)
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Aaron Hopkins (Apr 27)
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Ca By (Apr 27)
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Baptiste Jonglez (Apr 27)
- Message not available
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Baptiste Jonglez (Apr 27)
- Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32) Aaron Hopkins (Apr 27)