Datlev
Premium
join:2002-02-15
Ashburn, VA
 ·Vonage
 ·Verizon FIOS
| reply to jfeise
Re: AT&T 4to6 relay not working?
A couple of pointers:
0) The specific ipv6 transition technology you are talking about is called 6to4 (not 4to6) »en.wikipedia.org/wiki/6to4. Many providers (including my ISP Verizon) do not provide 6to4 relays, so AT&T is not alone in this. Through the use of anycast, the closest relay is automatically chosen, but may not be terribly close, and may very from time to time.
1) Just because you can not traceroute to it, does not mean that the host is unreachable by all protocols. traceroute implementations can use tcp, udp, and/or icmp depending on OS, and flags passed. Many providers (or specific routers) will block (or deprioritize) specific icmp messages as well.
See also: »en.wikipedia.org/wiki/Traceroute
2) If you are serious about trying IPv6, my personal recommendation would be to look into a tunnel broker rather than using 6to4 or teredo. In my experience, you will see much better reliability. I happen to use and recommend the free sixxs.net tunnels, but just google "ipv6 tunnel broker" to see some of the options available.
Good Luck. |
|
jfeise
join:2009-03-27
Santa Ana, CA
2 edits | Yes, I know that it is called 6to4. It just stroke me as illogical, since on my side it is IPv6 to IPv4, and on the other side, it is 4 to 6.
Anyway, I tried to use the HE.net tunnel broker as well. And that doesn't work, either.
And the fact that AT&T is not alone in it only points to the sad state of things. They have a web page about providing IPv6, at least to the US government, including DSL access, though.
And I also know very well that a traceroute is not the definitive way to determine reachability. It is just the only tool available to _me_. I don't have personal connections into telcos. |
|
Datlev
Premium
join:2002-02-15
Ashburn, VA
·Vonage
·Verizon FIOS
| If you are willing to give it another try, I'm sure that someone here will be willing to help troubleshoot your he.net protocol 41 tunnel (aka 6in4 tunnel). It has been awhile since I used he.net, but their forums are probably the best place to start.
The most common problem with proto 41 tunnels are getting the local NAT to properly forward packets. (In your case, this may be your DSL modem and/or an additional router) »en.wikipedia.org/wiki/6in4
1) Do you have a static ipv4 address ? If not, then you may want to ensure that your current EXTERNAL ipv4 address is properly registered with he.net, and setup a script to automatically update he with your correct address. See »www.tunnelbroker.net/forums/inde···3#msg663
2) Does your DSL Modem do NAT, or do you have another device after the modem (router of some sort) ? What is the brand/model ?
3) Configure your NAT to forward protocol 41 to the internal ipv4 address associated with your linux machine. If you do not have the option for protocol 41 forwarding, try setting the linux machine into the DMZ for your NAT/Router.
4) Read »www.tunnelbroker.net/forums/inde···pic=18.0 for the sample linux configuration steps.
Good Luck. |
|
jfeise
join:2009-03-27
Santa Ana, CA | As it turns out, my Web hoster just announced that they are going to test IPv6, so I should be able to get a v6 address for my Web machine (also Linux). I'll test a tunnel with that then, which gives me the ability to control both endpoints. |
|
charlesnw
join:2008-05-28
El Monte, CA | Who do you use as your slice provider? |
|
jfeise
join:2009-03-27
Santa Ana, CA
| said by charlesnw  :Who do you use as your slice provider? My provider is a company called grokthis.net, out of Philadelphia. |
|
