SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1370076
Ticket Status: Resolved

PoP: brudi01 - (Uberlandia)

R10899 subnet allocated from (already in use) tunnel address space
[br] Shadow Hawkins on Tuesday, 02 March 2010 00:43:42
I have reported this issue by e-mail, but I think it is worth tracking it on the ticket system. I got the 2001:1291:200::/48 prefix allocated to my subnet (R10899), but this is the address range from which tunnel prefixes are being allocated, for the brudi01 PoP. From : """ This PoP provides tunnels from the following prefixes: 2001:1291:200::/48 of size /64 Subnets are allocated out of: 2001:1291:200::/40 of size /48 """ From : """ Subnet Configuration The configuration for this subnet looks like: IPv6 Them2001:1291:200:f::2/64 (T25828) Prefix2001:1291:200::/48 StateEnabled Created2010-03-01 21:39:27 CET Last Modified2010-03-01 22:07:35 CET """ I can ping addresses inside the subnet prefix, meaning that the prefix is really already in use by the PoP. e.g.: PING 2001:1291:200::1: 56 data bytes 64 bytes from (2001:1291:200::1): icmp_seq=0. time=263. ms 64 bytes from (2001:1291:200::1): icmp_seq=1. time=264. ms 64 bytes from (2001:1291:200::1): icmp_seq=2. time=267. ms 64 bytes from (2001:1291:200::1): icmp_seq=3. time=262. ms 64 bytes from (2001:1291:200::1): icmp_seq=4. time=261. ms (I don't have any host using addresses from new subnet yet, except for my tunnel address, 2001:1291:200:f::2, that is working as expected).
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 March 2010 12:29:04
Message is Locked
The state of this ticket has been changed to resolved

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker