[arin-ppml] FW: IPv6 Non-connected networks
mcr at sandelman.ca
Mon Mar 29 12:53:18 EDT 2010
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Matthew" == Matthew Kaufman <matthew at matthew.at> writes:
Matthew> The problem is that you weren't already advertising a
Matthew> /32. You were hoping to advertise your /48, which is all
Matthew> the PI space you could get and afford, but your ISP
Matthew> wouldn't let you. Just like they won't let you announce the
Matthew> /119 either.
All of this is IPv4 think.
IPv6 networks have multiple prefixes(%)
You were using the NCN for internal use.
You had a /48 from each ISP, split up into /64s. Most of your
internal-only operations had no visibility to the Internet.
(You might want to use good ol' fashion SOCKS and algorithm-gateways and HTTP
proxies to get your system patches. If you like I have Raptor Eagle,
Milkyway Blackhole, and TIS FWTK binaries from the early 1990s)
You let a /64 from one ISP through to some machine that external support
needs to access (no, it's not a /119. It's a /64). You might even run
this through a transparent firewall/packet filter too.
(%) While Owen has documented why he feels multiple prefixes won't work,
but I've never had the problems he describes.
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Finger me for keys
-----END PGP SIGNATURE-----
More information about the ARIN-PPML