|
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
![[cz]](/s/countries/cz.gif) Shadow Hawkins on Friday, 28 March 2008 22:22:43
Hello,
I've got OpenWRT wifi router, that is the end of sixxs (aiccu, dynamic) tunnel. RADvd working, the winxp client successfully get IP address. I'm able to ping ipv6 sites from the winxp client successfully, but if I try to access web sites with AAAA records from IE7 or Firefox (with Ipv6 enabled in about:config screen) I get a big timeout and then the message that the browser can't connect to the site. Opera browser (latest - 9.26) works instantly. Has anybody experienced this? What am I missing?
- the ipv6 routing works, I can even ping the IPv6 address of winxp client from the notebook over couple of hops.
- I was configuring the ipv6 with help of the http://wiki.openwrt.org/IPv6_howto site. I did the windows xp set prefix policy stuff, but I guess it doesn't work much.
- if I tcpdump the ipv6 http connection, the three-way handshake is done, but the browser newer sends the HTTP GET request. It just sits there indefinitely. (again, only from IE and Firefox with ipv6 "not disabled") opera works
- I spend whole evening googling and reading the forum at sixxs.net.
Thanks for your time, have a nice day,
Honza Vlach
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Are you sure that Opera uses IPv6?
To force this, try www.ipv6.sixxs.net, this only has IPv6 and should be nearly as fast in all three browsers.
You should not have to touch the "prefix policy stuff", just do a "netsh int ipv6 reset", then maybe disable privacy addressing and teredo/6to4, but the rest should just work.
Then check for the following two possible problems:
- MTU
Check that the MTU on your tunnel is set correctly, that is matching the one on the PoP (default of 1280 which is also set by aiccu, if you have the correct version)
- DNS
Some DNS setups are broken. An upstream cache will then just ignore queries for AAAA or send back garbage. Your client thus needs to time out and then it can connect.
I guess the latter is not the case as you claim you can ping6 the destination.
Instead of tcpdumping the traffic, try wireshark, it also shows things like MTU issues, TCP reordering and other such common issues.
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Friday, 28 March 2008 23:43:00
Hello,
thank you for a really quick reply.
I see a dancing turtle at www.kame.net. (from opera)
If I visit a http://www.whatismyipv6.net/ site, I see "Your IP is 2001:15c0:669c:0:145:bb48:5e4d:22a2" message.
I've got:
<code>
interface br0
{
AdvLinkMTU 1280;
AdvSendAdvert on;
prefix 2001:15c0:669c::/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
</code>
in the /etc/radvd.conf and radvd daemon is running with it. I've even rebooted the router and the windows client couple of times the "windows way(tm)" just to be sure.
I've seen in the forum couple of references to the MTU problem, there was an URL linking to some really small GIF image on go6.net. (meaning data transfer lower than MTU) and it still didn't work.
I'm using dnsmasq on the openwrt (white russian stable 0.9; 2.4 kernel, no kamikadze )(router and did host & dig tests on the router and windows xp client. All the responses for AAAA DNS records are correct and immediate, so guess my provider doesn't have a buggy ISC BIND DNS daemon.
I did the
netsh interface ipv6 reset stuff
Now I can again access www.kame.net and www.go6.net without delay, but the site says I'm using ipv4. (my ipv4 address is shown)
<code>
netsh interface ipv6>reset
OK.
netsh interface ipv6>show prefixpolicy
Dotaz na aktivnà stav...
Priorita Popisek PÅedpona
---------- ----- --------------------------------
5 5 2001::/32
10 4 ::ffff:0:0/96
20 3 ::/96
30 2 2002::/16
40 1 ::/0
50 0 ::1/128
</code>
the messages are in czech, Priorita means priority, popisek means description, predpona means prefix. "Dotaz na aktivni stav" means "Query for actual state".
I would like to use ipv6 as much as possible and if there are no AAAA records available for destination site, use ipv6 without couple of minute's worth timeouts.
I did:
c:> netsh interface ipv6 set teredo disabled
and
c:> netsh interface ipv6 set privacy disabled
I tried googling around to get some tool to get me see what is the current MTU the windows client see, everything pointed to registry and I don't se the MTU key there. And as an unix admin, I'm kinda scared being in registry :-)
To sum it up:
I'm able to access sites with A and AAAA records again, but using ipv4 in firefox (with ipv6 enabled - the strange "disabled" option "disable ipv6" - I hate those double negatives) and in ie7, but opera still prefers ipv6 where AAAA records are available.
Again, thank you for your time. I really appreciate it.
I can post detailed dumps of anything, if you find it reasonable. I guess this post is long enough even without it. (sorry)
Honza Vlach
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Friday, 28 March 2008 23:47:36
wireshark on the windows xp client shows request length of 78 bytes while trying to access www.kame.net.
TCP three way handshake is okay, but again, the browser doesn't sent GET request and just sits there timing out.
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Saturday, 29 March 2008 00:01:18
just for the record:
accessing http://www.ipv6.sixxs.net/main/ in:
opera : works showing 2001:15c0:669c:0:ad13:b479:1573:d185 in the footer
ie7: shows connecting to 2001:838:1:1:210:... and times out
firefox: shows connecting to www.ipv6.sixxs.net and times out
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
You really only need:
interface eth0
{
AdvSendAdvert on;
prefix 2001:7b8:20d::/64
{
};
};
Those MTU things are not needed, as ICMP based Path MTU discovery should solve that for you. The MTU of your _tunnel_ should be correctly configured. Your eth0/br0 can use 1500 as it should, it is Ethernet after all. Of course, do check your firewall rules if they are correct (or better, disable them while testing).
so guess my provider doesn't have a buggy ISC BIND DNS daemon.
Actually BIND doesn't have this issue (unless heavily misconfigured, though I wouldn't know how one could do that).... but dnsmasq WAS broken at one point though.
You should do digs from your XP box. Also check your full "ipconfig /all" output, there might be stray DNS servers in there that sneaked in from another place. Then do a "nslookup" and in there "server a.b.c.d" to select each server and then do the query. Do note that the site you are querying might be cached. Also note that you have to do first an AAAA query for a host that is not cached (and might not even have an AAAA record) and then an A.
One way to exclude DNS issues is to add the IPv6 address temporarily to c:\windows\drivers\etc\hosts that way, it uses that and it should exclude DNS resolution.
Also, of course, again, check your firewall. The only IPv6-working firewall that I know of is the one included in Windows.
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Saturday, 29 March 2008 01:21:36
- Okay, I've deleted the line that sets MTU at openwrt router and restarted radvd on it. (/etc/radvd.conf)
- rebooted windows
- entered 2001:200:0:8002:203:47ff:fea5:3085 to c:\windows\system32\drivers\etc\hosts (www.kame.net)
- didtelnet 2001:200:0:8002:203:47ff:fea5:3085 80 and wrote GET / HTTP/1.0 and immediately got root http document.
- problem still the same - ie7 and firefox (2.0) timing out, opera gets the page immediately over ipv6.
- I've also found that only the firefox 3.0 prefers ipv6 over ipv4 on the web. I guess I'll give it a try ...
- I believe that the dnsmasq in openwrt 0.9 works fine, the answer is immediate without any delays:
Microsoft Windows XP [Verze 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\janus>nslookup -type=aaaa
Default server: maya.lan
Address: 192.168.1.1
server 192.168.1.1 Default server: maya.lan
Address: 192.168.1.1
vse.vse.cz Server: maya.lan
Address: 192.168.1.1
Unauthorized answer:
vse.vse.cz AAAA IPv6 address = 2001:718:1e02::2
Are there any differences in implementations of ipv6 in different browsers? e.g. ie7 vs. opera vs. firefox?
I've even tried putty 0.60 and it did connect over ipv6 (different timeout because of lacking PTR, but did connect eventually - timetout max ~30s)
- there are DNS servers with the fec0: prefix (don't really know what fec0 means - link local? ) e.g. ipconfig /all and pasting here the section that describes my wi-fi connection:
Adaptér sÃtÄ Ethernet Wi-Fi:
PÅÃpona DNS podle pÅipojenà . . . : lan
Popis . . . . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
Fyzická Adresa. . . . . . . . . . : 00-1B-77-80-C1-C3
Protokol DHCP povolen . . . . . . : Ano
Automatická konfigurace povolena : Ano
Adresa IP . . . . . . . . . . . . : 192.168.1.69
Maska podsÃtÄ . . . . . . . . . . : 255.255.255.0
Adresa IP . . . . . . . . . . . . : 2001:15c0:669c:0:7c7c:2595:72b7:c792
Adresa IP . . . . . . . . . . . . : 2001:15c0:669c:0:21b:77ff:fe80:c1c3
Adresa IP . . . . . . . . . . . . : fe80::21b:77ff:fe80:c1c3%12
Výchozà brána . . . . . . . . . . : 192.168.1.1
fe80::21a:92ff:fe7e:28fa%12
Server DHCP . . . . . . . . . . . : 192.168.1.1
Servery DNS . . . . . . . . . . . : 192.168.1.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
ZapůjÄeno . . . . . . . . . . . . : 29. bÅezna 2008 0:32:25
ZápůjÄka vyprÅ¡Ã . . . . . . . . . : 30. bÅezna 2008 0:32:25
should I try to boot some linux live CD on the notebook to see if it behaves differently?
I could as well use my girlfriend's win xp notebook to see if it differs. Obviously, I don't want to break too many stuff at once :-)
Thanks,
Honza Vlach
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
![[si]](/s/countries/si.gif) Shadow Hawkins on Saturday, 29 March 2008 14:46:36
Another detail:
Why does your NIC have 2 global IPv6 addresses ? radvd "assigns" only one. Did you configure it manually ?
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
![[be]](/s/countries/be.gif) Shadow Hawkins on Thursday, 03 April 2008 04:26:06
the second one is the windows "secure" adress; which is dynamic.
the idea is to make it so the sites you go can't know your return adress to attack you because it changes periodically.
if you don't like it, you can disable (I did it too) it by typing:
netsh int ipv6 set privacy disabled persistent
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Saturday, 29 March 2008 14:35:57
I suspect you did too much configuration:
> did the windows xp set prefix policy stuff
I just enabled the IPv6 protocol, that's it. Works terrific. On all Windows hosts.
I was configuring the ipv6 with help of the http://wiki.openwrt.org/IPv6_howto site. Not using aiicu ? Why not ? It is recommended by the FAQ here. And, again, works fine for me.
To summarize:
- Windows : just enable IPv6
- OpenWRT : aiccu + radvd (set local IPv6 interface address manually)
- everything works (inlcusding IE7 and Firefox 2.0.0.12
Did you do any settings on IE7 and FF ?
Firewalls (IPv6 related) ?
Regards,
David
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Saturday, 29 March 2008 14:38:33
Another thing: are the problems local to a single PC (and OS on it) ?
Can you try another PC ? Or OS (linux live CDs are very handy for this) ?
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 10:46:41
Just for completeness sake - I used zone alarm previously, I have uninstalled during the debug, ended up using windows integrated fw and disabled that one too.
will try a knoppix live cd now, but I might run into drivers issues, Dell Latitude D830 isn't one of the most supported machines :-(
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 10:44:42
Hello again,
firstly, I really appreciate your help and thanks again for your time. :)
I've tried girlfriend's computer, only issued netsh interface ipv6 install and it behaves the same, described way. Only opera connects using ipv6, anything else times out.
I did some research and it seems that opera actually ignores netsh interface ipv6 prefixpolicy settings.
if I issued 'set prefix policy ::1/128 5 5 (whatever that means), I was able to connect to all the sites using ipv4.
I've reinstalled the openwrt router as well, because I though I might have screwed something up. the current settings are:
(maya=openwrt router, lisa=linux in vmware bridged to physical interface of windows xp machine, windows xp machine=physical installation)
root@maya:~$ ip addr ls
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
2: eth0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:1a:92:7e:28:fa brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:92ff:fe7e:28fa/64 scope link
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 40:10:18:00:00:2d brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:1a:92:7e:28:fa brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:92ff:fe7e:28fa/64 scope link
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
6: br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 00:1a:92:7e:28:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br0
inet6 2001:15c0:669c::1/64 scope global
inet6 fe80::21a:92ff:fe7e:28fa/64 scope link
7: vlan0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> mtu 1500 qdisc noqueue
link/ether 00:1a:92:7e:28:fa brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:92ff:fe7e:28fa/64 scope link
8: vlan1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> mtu 1500 qdisc hfsc qlen 5
link/ether 00:17:08:41:06:e7 brd ff:ff:ff:ff:ff:ff
inet 84.42.135.143/24 brd 84.42.135.255 scope global vlan1
inet6 fe80::217:8ff:fe41:6e7/64 scope link
9: imq0: <NOARP,UP> mtu 1500 qdisc hfsc qlen 5
link/void
10: sixxs@NONE: <POINTOPOINT,NOARP,UP> mtu 1280 qdisc noqueue
link/sit 84.42.135.143 peer 212.18.63.73
inet6 fe80::542a:878f/64 scope link
inet6 2001:15c0:65ff:160::2/64 scope global
inet6 fe80::c0a8:101/64 scope link
root@maya:~$ cat /etc/radvd.conf
# For more examples, see the radvd documentation.
interface br0
{
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvSendAdvert on;
prefix 2001:15c0:669c::/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
root@maya:~$ ip -6 ro ls
2001:15c0:65ff:160::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2001:15c0:669c::/64 dev br0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1220
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth2 metric 256 mtu 1500 advmss 1220
ff00::/8 dev br0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
default via 2001:15c0:65ff:160::1 dev sixxs metric 1024 mtu 1280 advmss 1220
root@maya:~$ cat /etc/aiccu.conf | grep -v ^# | grep -v ^$
username XXXXXXXX
password XXXXXXXX
ipv4_interface vlan1
ipv6_interface sixxs
tunnel_id T14416
verbose true
daemonize true
automatic true
requiretls false
pidfile /var/run/aiccu.pid
defaultroute true
The openwrt is white russian 0.9, I read that aiccu is severely broken in that version, but I'm able to successfully ping from the windows xp machine ipv6 enabled machines, ipv6 putty works as well, the only problem is that firefox2 and ie7 are giving me headaches.
I'm setting up ipv6 address on br0 interface in /etc/init.d/S98radvd using:
ip -6 addr add 2001:15c0:669c::1/64 dev br0
how exactly is default route published for clients?
If I boot up linux client in vmware machine bridged to the physical interface, it has ipv4 connectivity, but it doesn't route and can't even ping machines on the same subnet. I don't see ipv6 default route with prefix 2001:15c0:669c::/64 there though ...
lisa:~# ip -6 addr ls
1: lo: <LOOPBACK,UP,10000> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qlen 1000
inet6 2001:15c0:669c:0:20c:29ff:fede:1313/64 scope global dynamic
valid_lft 2592000sec preferred_lft 604800sec
inet6 fe80::20c:29ff:fede:1313/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qlen 1000
inet6 fe80::20c:29ff:fede:131d/64 scope link
valid_lft forever preferred_lft forever
lisa:~# ip -6 ro ls
2001:15c0:669c::/64 dev eth0 proto kernel metric 256 expires 2592161sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21333511sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1 metric 256 expires 21333511sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 metric 256 expires 21333511sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth1 metric 256 expires 21333511sec mtu 1500 advmss 1440 hoplimit 4294967295
default via fe80::21a:92ff:fe7e:28fa dev eth0 proto kernel metric 1024 expires 29sec mtu 1500 advmss 1440 hoplimit 64
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
I'm also a bit mystified by the 2 ipv6 global addresses in windows xp, these apparently originate in radvd. Don't know why. I didn't even try to configure a static ipv6 address on the windows client machine.
What am I missing? Spent whole yesterday reconfiguring, googling around and trying to find some more detailed ipv6 setup info. Any good RTFM tips for me?
thank you & have a nice day,
jvl
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 12:44:04
First, consider upgrading aiccu to version 20070115-1. I use that myself under OpenWRT.
So lisa can not ping ? With IPv4 , IPv6 or both ? Because its settings seem OK.
David
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 13:14:32
Okay, another info.
I booted knoppix on girlfriend's notebook and ipv6 works there out of the box, without any delays.
In windows, I got rid of the second ipv6 address, it was due to enabled ipv6 privacy extensions (fixed with: netsh interface ipv6 set privacy disabled )
Also tried to turn on as many windows services on automatic start as possible, so I'm not missing any dependency.
Lisa not pinging was probably some glitch in the vmware.
Tried netsh interface ipv6 uninstall && reboot && netsh interface ipv6 install, it's still the same.
I can ping6, I can telnet6 ipv6 address of www.kame.net issue GET / HTTP/1.1 request in telnet session, get the contents of index.html.
I've also noticed that the default prefix windows use for ipv6 is 48bit (last line) - does this have something in common with the prefix in radvd.conf?
Truth is, that I have installed both Windows XP notebooks myself, so there may be some error or setting that disables correct functionality of ie & firefox over ipv6 ...
C:\Documents and Settings\janus>ipv6 if 14
Rozhranà 14: Ethernet: Bezdrátové pÅipojenà k sÃti
Guid {916C6426-6EB8-4C39-B0E1-0384578B7ADC}
použÃvá protokol Neighbor Discovery
použÃvá funkci pro zjiÅ¡Å¥ovánà smÄrovaÄů
adresa linkové vrstvy: 00-1b-77-80-c1-c3
preferred global 2001:15c0:669c:0:21b:77ff:fe80:c1c3, platnost 29d23h59m55s/
6d23h59m55s (veÅejná)
preferred link-local fe80::21b:77ff:fe80:c1c3, platnost infinite
vÃcesmÄrové vysÃlánà interface-local ff01::1, 1 odkazy, neuvedeno do zprávy
vÃcesmÄrové vysÃlánà link-local ff02::1, 1 odkazy, neuvedeno do zprávy
vÃcesmÄrové vysÃlánà link-local ff02::1:ff80:c1c3, 2 odkazy, poslednà zpravo
daj
jednotka MTU propojenà 1500 (skuteÄná jednotka MTU propojenà 1500)
aktuálnà limit smÄrovánà 64
doba dostupnosti 30500 ms (základnà 30000 ms)
interval opakovánà pÅenosu 1000 ms
pÅenosy DAD 1
výchozà délka pÅedpony sÃtÄ 48
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 13:15:53
I guess I already got correct version:
at the openwrt router:
root@maya:~$ aiccu version
AICCU 2007.01.15-console by Jeroen Massar
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 13:20:42
The incorrect site prefix theory could be supported by this:
netsh interface ipv6>show siteprefixes
Prefix Doba plat. Interface
------------------------ ------------ ------------------------------
2001:15c0:669c::/48 29d23h59m54s Wi-Fi
is there a way I could change it? radvdump says I'm propagating correct /64 prefix:
root@maya:~$ radvdump
#
# radvd configuration generated by radvdump 1.0
# based on Router Advertisement from fe80::21a:92ff:fe7e:28fa
# received by interface br0
#
interface br0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
prefix 2001:15c0:669c::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
}; # End of interface definition
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 14:07:06
The siteprefix is 48 for my too. I guess that is correct:
- site prefix : 48
- subnet prefix : 64
Makes sense.
(unrelated test, ignore; ÄÅ¡ÄÅ¾Ä Ã¤Ã«Ã©Ã¢)
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Sunday, 30 March 2008 13:46:06
Found Jeroen has already been commenting on this issue in microsoft newsgroups, the solution is missing :(
http://thesource.ofallevil.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.platformsdk.networking.ipv6&tid=58009b5c-4a34-4b00-94c9-4100bca3a929&cat=en_US_efbfb42b-d87e-48e6-935b-69a27452c365&lang=en&cr=US&sloc=&p=1
^-- describes the same problem.
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Thursday, 03 April 2008 04:31:22
it seems a problem of your browsers, not an IPv6 problem
Are the IE7 and Firefox using some different proxy settings than the Opera?
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
Shadow Hawkins on Friday, 05 September 2008 15:14:55
Okay, finally got it working - reinstalled the winxp notebook, then just issued ipv6 install at the command line and voila - dancing kame in ie7 :-D
Don't know what was wrong though. (Only thing I didn't do this time was messing with the ipv6 prefix policies - even though I've reset them when I was having problems before)
Thanks everyone for help and time, it is much appreciated.
Honza Vlach
IPv6 browser timeout in IE and firefox (no connectivity), but Opera works
avoid using "ipv6 install" the command is "netsh int ipv6 install", or even better, just use the Network Control Panel (start->settings... etc) to install it. "ipv6 install" does not fully (last time I heard) understand correctly how to configure IPv6 and thus might lead to broken installations.
|
![[ch]](/s/countries/ch.gif)
on Friday, 28 March 2008 22:41:54
Posting is only allowed when you are