philderbeast Posted November 22, 2010 Share Posted November 22, 2010 well i have been using ipv6 on my desktop for a few days and i noticed that the froxlor website is extraordinarily slow at responding on this, but ipv4 is fine, you might want to take a look at that, it was painful. Link to comment Share on other sites More sharing options...
d00p Posted November 22, 2010 Share Posted November 22, 2010 we will, thank you Link to comment Share on other sites More sharing options...
atari Posted November 23, 2010 Share Posted November 23, 2010 Hi Is your ipv6 network proper set up? dns working? reverse dns? atari Link to comment Share on other sites More sharing options...
philderbeast Posted November 23, 2010 Author Share Posted November 23, 2010 currently using a tunnel provided by my ISP Link to comment Share on other sites More sharing options...
atari Posted November 23, 2010 Share Posted November 23, 2010 on the server you have a tunnel or on your client? Link to comment Share on other sites More sharing options...
philderbeast Posted November 24, 2010 Author Share Posted November 24, 2010 on my client workstation i connect to a server provided by my isp to receive the tunneled connection the IP 6 server is local (just tested it then ) and this then has a native ip6 connection to the internet. i can't get an accurate tracert or ping to your server as they time out on ipv6 (its fine on v4 though) Link to comment Share on other sites More sharing options...
atari Posted November 24, 2010 Share Posted November 24, 2010 the way you describe your connections it doesn't seem to be a problem of froxlor. It seems more like a problem of your network connection between server and client... Link to comment Share on other sites More sharing options...
philderbeast Posted November 24, 2010 Author Share Posted November 24, 2010 its defiantly only an issue with the froxlor server as every other ipv6 sites is just as quick as on ipv4 Link to comment Share on other sites More sharing options...
atari Posted November 24, 2010 Share Posted November 24, 2010 sorry. but do you mean the froxlor.org server or your froxlor server? if you mean froxlor.org, i can agree as we're on it at the moment ;-) Link to comment Share on other sites More sharing options...
philderbeast Posted November 24, 2010 Author Share Posted November 24, 2010 yes froloxor.org server sorry Link to comment Share on other sites More sharing options...
atari Posted November 24, 2010 Share Posted November 24, 2010 well. we have some problems... but we're on it... ;-) Link to comment Share on other sites More sharing options...
GraveR Posted December 11, 2010 Share Posted December 11, 2010 Any word on this? The whole site is still unreachable over IPv6 making it a pain in the ass to visit (without resorting to editing the hostfile) when one is IPv6-enabled. Link to comment Share on other sites More sharing options...
d00p Posted December 11, 2010 Share Posted December 11, 2010 EleRas said "should work"...I'll re-check Link to comment Share on other sites More sharing options...
GraveR Posted December 11, 2010 Share Posted December 11, 2010 From 2 different places it's unavailable, getting stuck at the same point: traceroute to 2001:470:1f0b:12d2::1337 (2001:470:1f0b:12d2::1337) from 2001:888:2234::2, 30 hops max, 24 byte packets 1 v6gate.radiotwenterand.nl (2001:888:2234::1) 0.502 ms 0.302 ms 0.28 ms 2 ge-1-2-0.xr4.d12.xs4all.net (2001:888:0:214::1) 0.364 ms 0.332 ms 0.338 ms 3 0.ge-0-2-0.xr1.sara.xs4all.net (2001:888:2:1::1) 1.263 ms 1.258 ms 10.929 ms 4 10gigabitethernet3-3.core1.ams1.he.net (2001:470:0:e8::1) 1.472 ms 0.575 ms 0.524 ms 5 10gigabitethernet1-1.core1.fra1.he.net (2001:470:0:47::2) 13.968 ms 7.444 ms 15.54 ms 6 gige-gbge0.tserv6.fra1.ipv6.he.net (2001:470:0:69::2) 14.007 ms 13.992 ms 13.574 ms 7 * * * 8 * * * 9 * * * 10 * * * and traceroute to 2001:470:1f0b:12d2::1337 (2001:470:1f0b:12d2::1337) from 2001:1af8:fe14:0:210:18ff:fe53:9d6e, 30 hops max, 24 byte packets 1 neo.dikhoed.net (2001:1af8:fe14::1) 0.218 ms 0.219 ms 0.16 ms 2 gw-110.haa-01.nl.sixxs.net (2001:1af8:fe00:6d::1) 12.937 ms * * 3 2001:1af8:1:f006:218:74ff:fe46:3200 (2001:1af8:1:f006:218:74ff:fe46:3200) 12.342 ms 11.441 ms 11.386 ms 4 be25.crs.evo.leaseweb.net (2001:1af8::19) 13.636 ms 14.239 ms 13.065 ms 5 20gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 29.381 ms 24.493 ms 24.062 ms 6 gige-gbge0.tserv6.fra1.ipv6.he.net (2001:470:0:69::2) 26.271 ms 25.436 ms 26.266 ms 7 * * * 8 * * * Link to comment Share on other sites More sharing options...
atari Posted December 13, 2010 Share Posted December 13, 2010 it's working now. there had been a bad route on the server... Link to comment Share on other sites More sharing options...
GraveR Posted December 13, 2010 Share Posted December 13, 2010 it's working now. there had been a bad route on the server... Confirmed working. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.