 jfeise
join:2009-03-27 Santa Ana, CA
| reply to jfeise Re: AT&T 4to6 relay not working?
I now figured out that the problem was the Siemens Speedstream 4100 DSL modem that SBC/AT&T provides to DSL subscribers. That modem seems to block the IPv6-tunneled packets. Siemens has exited the DSL modem business, and there are no firmware updates available. Also, SBC apparently has their own configuration, which together cripples this modem. I bought a D-Link DSL-2320B today, and I can tunnel IPv6 just fine through it (it has another issue, though, only giving out the IP address for around 15 seconds...) |
|
 jfeise
join:2009-03-27 Santa Ana, CA
| An update: I returned the D-Link, after even their tech support couldn't help with the 15-second DHCP lease renew time, and after a detour with a Motorola 2210 which blocks incoming pings, I ended up with a 2-Wire 2701 which seems to be way less crippled than all the other DSL modems. Finally a manufacturer who doesn't think everybody is stupid... |
|
 awasser1
join:2004-03-30 Bloomfield, CT
| reply to jfeise Yep the SpeedStream 4100 does not work with IPV6. I found that out after three weeks. I switched to the UWire one I had and it seems to work better. I am still trying to make everything work with windows 7 and server 2008 R2. The server works on ipv6 just fine but the pc computer still tries to pickup ipv4 first. when u put ping -6 it works ok. so i am still trying to fix it.. fun fun fun.
Alec |
|
  Datlev Premium join:2002-02-15 Ashburn, VA
·Vonage
·Verizon FIOS
| said by awasser1 : I am still trying to make everything work with windows 7 and server 2008 R2. The server works on ipv6 just fine but the pc computer still tries to pickup ipv4 first. when u put ping -6 it works ok. This is usually caused by windows not *thinking* there is a valid global ipv6 address and route associated with an active network interface.
[snippet from MSDN] DNS Query Behavior
The DNS Client service in Windows Vista has been designed to minimize the impact on DNS servers when performing DNS name queries through the following behavior:
-If the host has only link-local or Teredo IPv6 addresses assigned, the DNS Client service sends a single query for A records.
-If the host has at least one IPv6 address assigned that is not a link-local or Teredo address, the DNS Client service sends a DNS query for A records and then a separate DNS query to the same DNS server for AAAA records. If an A record query times out or has an error (other than name not found), the corresponding AAAA record query is not sent.
[/snippet]
See here: »technet.microsoft.com/en-us/libr···035.aspx
You can see if this is indeed the case by using wireshark or netmon to examine the dns queries/responses.
Good Luck.
--Dave |
|