Size: 1167
Comment:
|
Size: 2589
Comment: converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
'''IPv6 Address Allocations''' | = IPv6 Addresses = |
Line 3: | Line 3: |
The most popular IPv6 tunnel broker seems to be http://www.freenet6.net/. Note that their tunnel routing servers are located in New York City, and may not be the most efficient endpoint. Contact KeeganQuinn if you're interested in a /64 with a Portland-based endpoint. Test your IPv6 connecivity by visiting http://www.ipv6.org/ - it will tell you if you're looking at that page over IPv4 or IPv6. This is a list of global scope IPv6 addresses for other PTP'ers to have some place interesting to reach on the "IPv6 Internet". |
<<TableOfContents>> |
Line 10: | Line 6: |
|| Owner || IPv6 || Notes || || Don Park || 3ffe:b80:9ce:1::1/64 || || || KeeganQuinn || 3ffe:bc0:449:1::1/48 || Glad to delegate /64 subnets to nodes; over 65,000 available || || The Basement (["Node471"]) || 3ffe:bc0:449:471::1/64 || Delegation from KeeganQuinn || || CapposCafe (["Node491"]) || 3ffe:bc0:449:491::1/64 || Delegation from KeeganQuinn || || WSMF (["Node236"])|| 3ffe:bc0:449:236::1/64 || Delegation from KeeganQuinn || || ["Node646"] || 2001:5c0:8316::/48 || From ["Freenet6"] || |
== Overview == |
Line 18: | Line 8: |
Also, don't forget NetworkAddressAllocations documents the PTP's IPv4 address space. |
This page acts as a registry to help manage subnet allocations within the `2001:4830:1248::/48` block which is reserved for PersonalTelco. See [[IPv6]] for background information. == History == Once upon a time, there was a long-running debate about the correct way of handling IPv6 addresses in the DNS, which mostly resulted in those addresses being left out of DNS entirely. That meant that you could generally only establish an IPv6 connection by using a literal address; this page was originally used to publish those literal addresses. That debate has since reached a conclusion. In DNS, `AAAA` records with IPv6 addresses now sit alongside `A` records with IPv4 addresses, allowing transparent, automatic usage of IPv6 connections when possible. As a result, it is no longer necessary to use literal IPv6 addresses except in rare situations; likewise, it is no longer necessary to list literal addresses here. == Guidelines == This page should be managed much like to the NetworkAddressAllocations page which acts as a registry for the allocation of assorted IPv4 subnets for Portland-based IPv4 sites within a `/16` block. In contrast to the IPv4 allocations page, all addresses listed here are global-scope and must be routed at a central point. In other words, NetworkAddressAllocations is an authoritative registry, but this list should be considered more of a quick reference; the central router is the real authority. == Subnets == || '''Node''' || '''Network (CIDR)''' || '''Tunnel (CIDR)''' || || Reserved for CoreServer use || `2001:4830:1248::/64` || || || [[NodeTB]] || `2001:4830:1248:1700::/64` || `2001:4830:1248::1700:1/112` || || [[NodeTB151]] || `2001:4830:1248:1740::/64` || `2001:4830:1248::1740:1/112` || || [[NodeLuckyLabNW]] || `2001:4830:1248:1800::/64` || `2001:4830:1248::1800:1/112` || || [[NodeEcotrust]] || `2001:4830:1248:2600::/64` || `2001:4830:1248::2600:1/112` || || [[NodeHawthorne]] || `2001:4830:1248:6400::/64` || `2001:4830:1248::6400:1/112` || == Hosts == || '''Host''' || '''Address (CIDR)''' || || `donk` || `2001:4830:1248::/128` || || `cornerstone` || `2001:4830:1248::1:1/112` || || `bone` || `2001:4830:1248::2:1/112` || || `spartan` || `2001:4830:1248::6:1/112` || ---- CategoryDocumentation CategoryEducation CategoryMan CategoryNetwork CategoryDamnYouKeegan |
IPv6 Addresses
Contents
Overview
This page acts as a registry to help manage subnet allocations within the 2001:4830:1248::/48 block which is reserved for PersonalTelco. See IPv6 for background information.
History
Once upon a time, there was a long-running debate about the correct way of handling IPv6 addresses in the DNS, which mostly resulted in those addresses being left out of DNS entirely. That meant that you could generally only establish an IPv6 connection by using a literal address; this page was originally used to publish those literal addresses.
That debate has since reached a conclusion. In DNS, AAAA records with IPv6 addresses now sit alongside A records with IPv4 addresses, allowing transparent, automatic usage of IPv6 connections when possible. As a result, it is no longer necessary to use literal IPv6 addresses except in rare situations; likewise, it is no longer necessary to list literal addresses here.
Guidelines
This page should be managed much like to the NetworkAddressAllocations page which acts as a registry for the allocation of assorted IPv4 subnets for Portland-based IPv4 sites within a /16 block.
In contrast to the IPv4 allocations page, all addresses listed here are global-scope and must be routed at a central point. In other words, NetworkAddressAllocations is an authoritative registry, but this list should be considered more of a quick reference; the central router is the real authority.
Subnets
Node |
Network (CIDR) |
Tunnel (CIDR) |
Reserved for CoreServer use |
2001:4830:1248::/64 |
|
2001:4830:1248:1700::/64 |
2001:4830:1248::1700:1/112 |
|
2001:4830:1248:1740::/64 |
2001:4830:1248::1740:1/112 |
|
2001:4830:1248:1800::/64 |
2001:4830:1248::1800:1/112 |
|
2001:4830:1248:2600::/64 |
2001:4830:1248::2600:1/112 |
|
2001:4830:1248:6400::/64 |
2001:4830:1248::6400:1/112 |
Hosts
Host |
Address (CIDR) |
donk |
2001:4830:1248::/128 |
cornerstone |
2001:4830:1248::1:1/112 |
bone |
2001:4830:1248::2:1/112 |
spartan |
2001:4830:1248::6:1/112 |
CategoryDocumentation CategoryEducation CategoryMan CategoryNetwork CategoryDamnYouKeegan