|
IPv6 works on CMD, not in browser
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 21 October 2010 23:50:33
I have installed the latest tap-driver and aiccu.
My tunnel is working as I can tracert and ping ipv6-adresses at the command-prompt.
But either Firefox nor Opera nor Iexplore can resolve ipv6-adresses.
I am using Windows 7 32-bit.
Can you give me a hint how to make my Internet Browsers work with ipv6? I already got it working...but with Windows XP
IPv6 works on CMD, not in browser
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Friday, 22 October 2010 09:16:56
Check if you have (automatic?) proxysettings. If you go through a proxy, it might not know ipv6.
On my ipv6-enabled machines, ipv6 just work :-), no special settings for browsers.
IPv6 works on CMD, not in browser
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Sunday, 07 November 2010 04:01:06
Same problem as TS here.
I've disabled all proxies, or the "Automatically detect settings"-checkbox.
All no change.
Since I can do the ping's/traceroutes (see post to Jeroen), the routes look fine.
Maybe it's a Windows 7 related issue?
IPv6 works on CMD, not in browser
I have installed the latest tap-driver and aiccu.
But does it actually work?
My tunnel is working as I can tracert and ping ipv6-adresses at the command-prompt.
Show us the money... ehmm output. See the 'reporting problems checklist' for more details that might be important to show.
IPv6 works on CMD, not in browser
Shadow Hawkins on Sunday, 07 November 2010 03:58:45
I have exactly the same issue here (only with Windows 7 64bit).
My tunnel is working, since I can ping / tracert IPv6 addresses.
Here some result:
C:\Windows\system32>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2a00:1450:8003::6a] with 32 bytes of data:
Reply from 2a00:1450:8003::6a: time=19ms
Reply from 2a00:1450:8003::6a: time=19ms
Reply from 2a00:1450:8003::6a: time=20ms
Reply from 2a00:1450:8003::6a: time=18ms
Ping statistics for 2a00:1450:8003::6a:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 20ms, Average = 19ms
C:\Windows\system32>tracert -6 ipv6.google.com
Tracing route to ipv6.l.google.com [2a00:1450:8003::6a]
over a maximum of 30 hops:
1 11 ms 15 ms 14 ms gw-612.haa-01.nl.sixxs.net [2001:1af8:fe00:263::1]
2 15 ms 13 ms 13 ms 2001:1af8:1:f006:218:74ff:fe46:3200
3 15 ms 12 ms 11 ms be25.crs.evo.leaseweb.net [2001:1af8::19]
4 25 ms 25 ms 15 ms core1.ams.net.google.com [2001:7f8:1::a501:5169:2]
5 15 ms 23 ms 17 ms 2001:4860::1:0:8
6 17 ms 21 ms 20 ms 2001:4860::1:0:2a
7 16 ms 18 ms 19 ms 2001:4860::34
8 18 ms 18 ms 30 ms 2001:4860:0:1::2d
9 19 ms 19 ms 18 ms 2a00:1450:8003::6a
Trace complete.
I've tried Internet Explorer, Firefox.
It just doesn't make sense...
- Mike
IPv6 works on CMD, not in browser
![[us]](/s/countries/us.gif) Shadow Hawkins on Sunday, 07 November 2010 04:38:42
Same thing, did you give your local area connection a public IPv6 address?
IPv6 works on CMD, not in browser
Shadow Hawkins on Sunday, 07 November 2010 23:06:55
I'm not sure.
Here is what I did; I followed the step-by-step tutorial at the Wiki for 'Configuring on Vista'.
Thereby I also received the details by SixXS for the tunnel I applied for.
When I take a look at the interface for aiccu / sixxs tunnel, I do see an IP address there, although I'm not sure if it's a public or private IP.
IP address: 2001:1af8:fe00:263::2
Subnet prefix length: 64
Gateway: 2001:1af8:fe00:263::1
Above IP matches with the delivery notication for the tunnel.
IPv6 works on CMD, not in browser
Shadow Hawkins on Friday, 26 November 2010 18:32:17
What is the output of ipconfig (or Ifconfig if you're on linux)
IPv6 works on CMD, not in browser
Shadow Hawkins on Thursday, 04 November 2010 23:48:01
Did you add a global IPv6 address on your local area connection?
IPv6 works on CMD, not in browser
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Monday, 29 November 2010 06:48:14
I had the same problem... But when I added my ULA (calculated with the SIXXS ULA calculator) to the physical interface on my PC the problem went away. The tunnel is still configured with the global address. I assume it has something to do with the browsers not recognizing the tun0 interface as a real IPv6 interface.
IPv6 works on CMD, not in browser
Shadow Hawkins on Monday, 29 November 2010 15:00:50
Exactly.
|
on Friday, 22 October 2010 09:43:35
Posting is only allowed when you are