Re: IPv6 Tunnel Brokers?
Sure I was: [T]here seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. Eric On Aug 1, 2007, at 10:06 AMAug 1, 2007, Tuc at T-B-O-H.NET wrote: http://ipv6tb.he.net/index.php You aren't clear on the problems at the ISP, so not sure what to tell you. Tuc Hey list, While my ISP is rather geeky and more than willing to give me an IPv6 tunnel to the internet, there seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. So, I ask two things really. 1) Does anyone know of an ISP that'll give me a /48 or /64 they'll route across a gif tunnel? 2) What could I do to help remedy this routing problem? Thanks! Eric Crist ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel Brokers?
On Wed, 1 Aug 2007 09:52:45 -0500, Eric Crist wrote: Hey list, While my ISP is rather geeky and more than willing to give me an IPv6 tunnel to the internet, there seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. So, I ask two things really. 1) Does anyone know of an ISP that'll give me a /48 or /64 they'll route across a gif tunnel? http://www.tunnelbroker.net/ I use them and seem to be quite good. -jav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel Brokers?
Javier Henderson wrote: On Wed, 1 Aug 2007 09:52:45 -0500, Eric Crist wrote: Hey list, While my ISP is rather geeky and more than willing to give me an IPv6 tunnel to the internet, there seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. So, I ask two things really. 1) Does anyone know of an ISP that'll give me a /48 or /64 they'll route across a gif tunnel? http://www.tunnelbroker.net/ I use them and seem to be quite good. I second that recommendation. The ISP in question is Hurricane Electric and the process is 100% web driven. It took me less than a day to get a gif tunnel up and an ipv6 /64 assignment. -- Chris -- __o All I was doing was trying to get home from work. _`\,_ -Rosa Parks ___(*)/_(*)___ Christopher Sean Hiltonchris | at | vindaloo.com pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel Brokers?
I second that recommendation. The ISP in question is Hurricane Electric and the process is 100% web driven. It took me less than a day to get a gif tunnel up and an ipv6 /64 assignment. They are FAIRLY response to service issues (I had problems getting to FTP1.FREEBSD.ORG for a bit, and within 8 hours of putting a ticket in it was resolved). They also show exact configuration for 1/2 a dozen different OS/routers. Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel Brokers?
On Wed, August 1, 2007 16:12, Christopher Hilton wrote: Javier Henderson wrote: On Wed, 1 Aug 2007 09:52:45 -0500, Eric Crist wrote: Hey list, While my ISP is rather geeky and more than willing to give me an IPv6 tunnel to the internet, there seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. So, I ask two things really. 1) Does anyone know of an ISP that'll give me a /48 or /64 they'll route across a gif tunnel? http://www.tunnelbroker.net/ I use them and seem to be quite good. I second that recommendation. The ISP in question is Hurricane Electric and the process is 100% web driven. It took me less than a day to get a gif tunnel up and an ipv6 /64 assignment. I was up and running in a few hours! I'm using a Cisco rouer on my end, it was very easy to set up and get going. -jav (disclaimer: I work at Cisco) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel Brokers?
On Aug 1, 2007, at 4:41 PMAug 1, 2007, Javier Henderson wrote: On Wed, August 1, 2007 16:12, Christopher Hilton wrote: Javier Henderson wrote: On Wed, 1 Aug 2007 09:52:45 -0500, Eric Crist wrote: Hey list, While my ISP is rather geeky and more than willing to give me an IPv6 tunnel to the internet, there seems to be a large number of routing problems upstream from them that prevent us from accessing the majority of the IPv6 net. So, I ask two things really. 1) Does anyone know of an ISP that'll give me a /48 or /64 they'll route across a gif tunnel? http://www.tunnelbroker.net/ I use them and seem to be quite good. I second that recommendation. The ISP in question is Hurricane Electric and the process is 100% web driven. It took me less than a day to get a gif tunnel up and an ipv6 /64 assignment. I was up and running in a few hours! I'm using a Cisco rouer on my end, it was very easy to set up and get going. -jav (disclaimer: I work at Cisco) Thanks for the pointer to he.net! I signed up, and my tunnel was approved within a half hour. I've already setup reverse DNS and the tunnel, and, 2 hours after signing up, I'm routed and operational! What's weird, is that from the he.net tunnel, I can ping6 www.kame.net, and I can ping6 my other ip6 addresse (my other tunnel). But, from my old tunnel, I cannot ping6 www.kame.net. Must be a routing issue somewhere between... Thanks for the pointer guys! Eric Crist ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel issues...
On 3/20/07, Eric F Crist [EMAIL PROTECTED] wrote: My ISP tells me it should be prefixlen 126, not 128 On 3/20/07, Björn König [EMAIL PROTECTED] wrote: Eric F Crist schrieb: [...] I'm performing the configuration as follows: ifconfig gif0 create ifconfig gif0 tunnel my IPv4 address my ISP IPv4 address ifconfig gif0 inet6 alias ::a::a ::b::b prefixlen 126 When I execute the last command, I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument [...] Use a prefix length of 128 instead of 126. Regards Björn Sorry for the top post earlier. I've eliminated the second IP address on the inet6 ifconfig command, and prefixlen 126 is accepted. Now I just get no ping replies accross the gif0 interface. ifconfig shows all the correct information, and netstat -rn shows valid routes. What am I missing? I *did* have this working at one time this morning, but I tried to get things into rc.conf and haven't been able to get it back up. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel issues...
On Tuesday 20 March 2007 17:01, Eric F Crist wrote: On 3/20/07, Eric F Crist [EMAIL PROTECTED] wrote: My ISP tells me it should be prefixlen 126, not 128 On 3/20/07, Björn König [EMAIL PROTECTED] wrote: Eric F Crist schrieb: [...] I'm performing the configuration as follows: ifconfig gif0 create ifconfig gif0 tunnel my IPv4 address my ISP IPv4 address ifconfig gif0 inet6 alias ::a::a ::b::b prefixlen 126 When I execute the last command, I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument [...] Use a prefix length of 128 instead of 126. Regards Björn Sorry for the top post earlier. I've eliminated the second IP address on the inet6 ifconfig command, and prefixlen 126 is accepted. Now I just get no ping replies accross the gif0 interface. ifconfig shows all the correct information, and netstat -rn shows valid routes. What am I missing? I *did* have this working at one time this morning, but I tried to get things into rc.conf and haven't been able to get it back up. There is an errata notice about gif(4)s, don't know it affects you... http://www.freebsd.org/releases/6.2R/errata.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel issues...
Eric F Crist schrieb: [...] I'm performing the configuration as follows: ifconfig gif0 create ifconfig gif0 tunnel my IPv4 address my ISP IPv4 address ifconfig gif0 inet6 alias ::a::a ::b::b prefixlen 126 When I execute the last command, I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument [...] Use a prefix length of 128 instead of 126. Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel issues...
On 3/20/07, Nikos Vassiliadis [EMAIL PROTECTED] wrote: On Tuesday 20 March 2007 17:01, Eric F Crist wrote: On 3/20/07, Eric F Crist [EMAIL PROTECTED] wrote: My ISP tells me it should be prefixlen 126, not 128 On 3/20/07, Björn König [EMAIL PROTECTED] wrote: Eric F Crist schrieb: [...] I'm performing the configuration as follows: ifconfig gif0 create ifconfig gif0 tunnel my IPv4 address my ISP IPv4 address ifconfig gif0 inet6 alias ::a::a ::b::b prefixlen 126 When I execute the last command, I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument [...] Use a prefix length of 128 instead of 126. Regards Björn Sorry for the top post earlier. I've eliminated the second IP address on the inet6 ifconfig command, and prefixlen 126 is accepted. Now I just get no ping replies accross the gif0 interface. ifconfig shows all the correct information, and netstat -rn shows valid routes. What am I missing? I *did* have this working at one time this morning, but I tried to get things into rc.conf and haven't been able to get it back up. There is an errata notice about gif(4)s, don't know it affects you... http://www.freebsd.org/releases/6.2R/errata.html Yes, I saw that, my first post mentions I'm patched and good-to-go. I've also tried the work around mentioned, just to be sure. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IPv6 Tunnel
I haven't checked out freenet6, but, I have been using the HE.net tunnel broker (ipv6tb.he.net), they give you a /64 with reverse dns and everything, after using it for a while, I decided to get the commercial solution from them, but I don't want to have to buy it for each one of my boxes -Original Message- From: Robert Huff [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:36 AM To: Dukemaster Subject: IPv6 Tunnel Hello: At my first co-location my FreeBSD server has a native IPv6 onnection and a /64 subnet I have a second co-location with a different isp, that doesn't have IPv6. Is it possible to have my first FreeBSD box act as a tunnel to my second box, and get it on IPv6 over the existing IPv4 connection? Probably. Before you do so, check out the net/frennet6 port. Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 Tunnel
On Tue, Mar 16, 2004 at 12:13:26AM -0500, Dukemaster wrote:
At my first co-location my FreeBSD server has a native IPv6 connection
and a /64 subnet
I have a second co-location with a different isp, that doesn't have
IPv6.
Is it possible to have my first FreeBSD box act as a tunnel to my second
box, and get it on IPv6 over the existing IPv4 connection?
Yes -- that's possible, but perhaps not ideal as all of the IPv6
packets from the net for co-lo2 will first have to go to co-lo1 and
back again.
The way I'd configure this is to set up a gif(4) IPv6 over IPv4 tunnel
(as per RFC 2893) between the machine at co-lo1 and the machine at
co-lo2. You can do that entirely by fiddling with entries in
/etc/rc.conf:
gif_interfaces=gif0
gifconfig_gif0=${thisIP4} ${thatIP4}
ipv6_enable=YES
ifconfig_gif0_alias0=inet6 ${thisIP6}/64
where ${thisIP4} is the IPv4 network interface address on the local
machine, ${thatIP4} is the address of the machine in the other co-lo
and ${thisIP6} is the IPv6 address you assign to the the local
system. Do the same deal on the other system, where obviously, which
addresses are local and which are remote will be the other way round.
On the machine without the IPv6 connectivity, you'll additionally
need:
ipv6_defaultrouter=-interface gif0
and on the co-lo1 machine you may need to add a static route telling
it how to reach the machine at co-lo2 -- see the section on
'ipv6_static_routes' in /etc/default/rc.conf.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgp0.pgp
Description: PGP signature
