Re: [Discuss] Recommendations for IPv6?
I registered for an account at SixXS.com on Friday evening, and then yesterday I requested a heartbeat tunnel. I just received the tunnel this afternoon. I deployed it as a hybrid system on a new server that we're planning to move our guest websites to in the near future, and I'm successfully pinging over IPv6 and, via vnc-over-ssh, I was able to browse several IPv6-only sites. I'm thinking I can deploy the other server as IPv6-only and have it route through the hybrid server, making it feasible to try out both types of environments. On Sat, Oct 15, 2011 at 9:36 AM, Edward Ned Harvey wrote: >> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- >> bounces+blu=nedharvey@blu.org] On Behalf Of John Abreau >> >> Any recommendations for the server OS? > > All OSes support IPv6 natively, very well now. Every flavor of Linux, > Windows, Mac, Solaris, etc. Um... Disclaimer: Not all the apps inside > your OS support it well. If people can sometimes get tripped up by IPv6 in > Firefox, just imagine how well it works for the zillion daemons you're > running, etc. There will be gotchas. But you can solve them all. > > The problem is connectivity. Most of the time you'll run into a problem > with the ISP, firewall, router, etc. One of these things won't support it, > and your traffic won't go anywhere. So then you have to do things like > tunneling IPv6 over IPv4. > > While you wouldn't want to do tunneling in a full fledged production system > (defeats the point of IPv6) you'll be able to learn everything you need to > learn that way. Ideally you would have your perimeter firewall do the > tunneling, so your internal OSes would simply think "Hey, I'm on a network > that supports IPv6." You become your own ISP providing IPv6 to yourself. I > know apple airport extremes have native tunneling available. Just enter > your tunnel endpoint settings (from hurricaine electric or whatever) and > voila, you have an IPv6 enabled LAN. I am certain many other devices can do > the same. > > -- John Abreau / Executive Director, Boston Linux & Unix OLD GnuPG KeyID: D5C7B5D9 / Email: abre...@gmail.com OLD GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 2011 GnuPG KeyID: 32A492D8 / Email: abre...@gmail.com 2011 GnuPG FP: ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > bounces+blu=nedharvey@blu.org] On Behalf Of John Abreau > > Any recommendations for the server OS? All OSes support IPv6 natively, very well now. Every flavor of Linux, Windows, Mac, Solaris, etc. Um... Disclaimer: Not all the apps inside your OS support it well. If people can sometimes get tripped up by IPv6 in Firefox, just imagine how well it works for the zillion daemons you're running, etc. There will be gotchas. But you can solve them all. The problem is connectivity. Most of the time you'll run into a problem with the ISP, firewall, router, etc. One of these things won't support it, and your traffic won't go anywhere. So then you have to do things like tunneling IPv6 over IPv4. While you wouldn't want to do tunneling in a full fledged production system (defeats the point of IPv6) you'll be able to learn everything you need to learn that way. Ideally you would have your perimeter firewall do the tunneling, so your internal OSes would simply think "Hey, I'm on a network that supports IPv6." You become your own ISP providing IPv6 to yourself. I know apple airport extremes have native tunneling available. Just enter your tunnel endpoint settings (from hurricaine electric or whatever) and voila, you have an IPv6 enabled LAN. I am certain many other devices can do the same. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
On Oct 14, 2011, at 7:21 PM, John Abreau wrote: > > I talked to the support department at our colo facility, and they tell me > that they currently do not provide any IPv6 at all. I was surprised to > learn this, as I would think a colo facility would be one of the first > places where it needs to be deployed. Actually, a colo is one of the last places I'd expect to see IPv6 deployed. One does not screw around with working systems when one has expensive service level agreements with large customers who have not requested such changes. --Rich P. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
I talked to the support department at our colo facility, and they tell me that they currently do not provide any IPv6 at all. I was surprised to learn this, as I would think a colo facility would be one of the first places where it needs to be deployed. I guess I'll have to put the project on hold for now, or find some other way to do it elsewhere. On Fri, Oct 14, 2011 at 1:41 PM, John Abreau wrote: > I'm thinking of deploying an IPv6-only server at our colo facility so I can > get some practical experience with IPv6. I've got server hardware available > for the project, so now I need to work out the remaining details. > > Any recommendations for the server OS? I'm used to CentOS, so my > initial thoughts are to use either CentOS 6.0 or Scientific Linux 6.1, > both of which are rebuilt editions of RHEL 6.x. Would these be my > best options, or would I be better off with something like FreeBSD, > OpenBSD, or OpenSolaris? > > For what it's worth, I used to use BSD in college back in the '80's, and > I worked with Solaris extensively in the '90's, but I haven't been using > either of them recently. So unless they'd be a really big win over > CentOS or SL, I think my more current experience would makes CentOS > or SL the better choices. > > > -- > John Abreau / Executive Director, Boston Linux & Unix > GnuPG KeyID: 0xD5C7B5D9 / Email: abre...@gmail.com > GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 > ___ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix Email j...@blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
OK, that makes sense. Thanks! On Fri, Oct 14, 2011 at 2:31 PM, Gregory Boyce wrote: > Starting with a hybrid system would probably make more sense to start > with. It matches what everyone else is doing so you're more likely to > find info online that will help you. It is also more likely to work. > I'm not sure if the various OS vendors have done much testing of an > IPv6 only system configuration. > -- John Abreau / Executive Director, Boston Linux & Unix GnuPG KeyID: 0xD5C7B5D9 / Email: abre...@gmail.com GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
On Fri, Oct 14, 2011 at 2:22 PM, John Abreau wrote: > A hybrid system might make sense if I were deploying a production > server, but at this point I'm not doing that. I can always experiment with > a hybrid server at a later date, after I've worked with the IPv6-only server > for a while. > > Or are you saying it would be easier to learn IPv6 if I start with a > hybrid system? Starting with a hybrid system would probably make more sense to start with. It matches what everyone else is doing so you're more likely to find info online that will help you. It is also more likely to work. I'm not sure if the various OS vendors have done much testing of an IPv6 only system configuration. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
The system wouldn't be a production server at all; it would be strictly for testing IPv6. If there's some breakage, that's not an issue, as the whole point of the thing is to gain some early experience with IPv6, so I can play around with it and get my head around it. I'm assuming that at some point in the future, we'll have to begin deploying IPv6, and I'd like to have some in-depth hands-on experience with it prior to that time. A hybrid system might make sense if I were deploying a production server, but at this point I'm not doing that. I can always experiment with a hybrid server at a later date, after I've worked with the IPv6-only server for a while. Or are you saying it would be easier to learn IPv6 if I start with a hybrid system? On Fri, Oct 14, 2011 at 2:07 PM, Gregory Boyce wrote: > On Fri, Oct 14, 2011 at 1:41 PM, John Abreau wrote: >> I'm thinking of deploying an IPv6-only server at our colo facility so I can >> get some practical experience with IPv6. I've got server hardware available >> for the project, so now I need to work out the remaining details. > > IPv6 only isn't a very feasible configuration right now. Most ipv6 > deployments are dual stack with both ipv6 and ipv4. At the very > least, expect some ipv6 breakage due to a general lack of ipv6 enabled > authoritative nameservers. If you're using a public resolver with > both ipv4 and ipv6 addresses, that might help to some degree. > >> Any recommendations for the server OS? I'm used to CentOS, so my >> initial thoughts are to use either CentOS 6.0 or Scientific Linux 6.1, >> both of which are rebuilt editions of RHEL 6.x. Would these be my >> best options, or would I be better off with something like FreeBSD, >> OpenBSD, or OpenSolaris? > > I have my house ipv6 enabled right now (dual stack). I've got an ipv6 > tunnel setup on a FreeBSD box which serves out a SIXXS subnet to the > rest of my devices. It works fairly well. > > For clients support, Linux seems to work fairly well. I did the > tunnel on FreeBSD instead due to the ease of use of pf compared to > iptables. No special ipv6 specific rules required, and the syntax is > very nice and clean. > -- John Abreau / Executive Director, Boston Linux & Unix GnuPG KeyID: 0xD5C7B5D9 / Email: abre...@gmail.com GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Recommendations for IPv6?
On Fri, Oct 14, 2011 at 1:41 PM, John Abreau wrote: > I'm thinking of deploying an IPv6-only server at our colo facility so I can > get some practical experience with IPv6. I've got server hardware available > for the project, so now I need to work out the remaining details. IPv6 only isn't a very feasible configuration right now. Most ipv6 deployments are dual stack with both ipv6 and ipv4. At the very least, expect some ipv6 breakage due to a general lack of ipv6 enabled authoritative nameservers. If you're using a public resolver with both ipv4 and ipv6 addresses, that might help to some degree. > Any recommendations for the server OS? I'm used to CentOS, so my > initial thoughts are to use either CentOS 6.0 or Scientific Linux 6.1, > both of which are rebuilt editions of RHEL 6.x. Would these be my > best options, or would I be better off with something like FreeBSD, > OpenBSD, or OpenSolaris? I have my house ipv6 enabled right now (dual stack). I've got an ipv6 tunnel setup on a FreeBSD box which serves out a SIXXS subnet to the rest of my devices. It works fairly well. For clients support, Linux seems to work fairly well. I did the tunnel on FreeBSD instead due to the ease of use of pf compared to iptables. No special ipv6 specific rules required, and the syntax is very nice and clean. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
