IPv6 and facebook.com, health.govt.nz
I'm using IPv6 through a SixXS tunnel and apart from two sites it works well. The two problem sites are as mentioned above, Facebook is just insanely slow for the first connection and I'm not sure why, health.govt.nzis completely unreachable for me because they filter icmpv6. I've discussed this with various people and I'm fairly confident that the problem is not at my end. So, any thoughts on how I might configure my system (debian 6) to prefer IPV4 for just those two sites but use ipv6 for everything else?
On 8 June 2013 13:04, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
So, any thoughts on how I might configure my system (debian 6) to prefer IPV4 for just those two sites but use ipv6 for everything else?
No idea - but you've aroused my curiosity. What are the advantages of using ipv6 instead of ipv4? Michael
It's dirty but you could set the ipv4 ips in /etc/hosts Sent from my iPhone On 8/06/2013, at 5:33 PM, "Michael McDonald" <mikencolleen(a)gmail.com> wrote:
On 8 June 2013 13:04, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
So, any thoughts on how I might configure my system (debian 6) to prefer IPV4 for just those two sites but use ipv6 for everything else?
No idea - but you've aroused my curiosity. What are the advantages of using ipv6 instead of ipv4?
Michael _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
On 8 June 2013 13:04, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
So, any thoughts on how I might configure my system (debian 6) to prefer IPV4 for just those two sites but use ipv6 for everything else?
There seems to be some discussion around the problem over here http://forums.whirlpool.net.au/forum-replies.cfm?t=2110001 I'm IPv6 enabled at home, and am not seeing any problems accessing Facebook (using Chromium for Fedora 18, IPv6). I guess it depends on which Facebook web cluster you get directed too. On 08/06/13 15:32, Michael McDonald wrote:
No idea - but you've aroused my curiosity. What are the advantages of using ipv6 instead of ipv4?
My ISP (Internode in Australia) gives me a single IPv4 address, but 4,722,366,482,869,645,213,696 IPv6 addresses (a /56 block). Considering I usually only have 10 or so devices connected to the network, that is a bit overkill Moving to IPv6 is a bit like switching from analogue to digital tv. The word has run out IPv4 addresses, and so we need to start using IPv6 to fix this problem in the long run. It will be decades before IPv4 is 'switched off' (if it is at all) However, its very much a 'chicken and egg' problem where ISPs aren't moving because there is no demand, and providers aren't switching for the same reason. Most NZ ISP do have plans to enable IPv6 on their networks in the coming years. Snap Internet are the only ISP that are IPv6 enabled for all customers (assuming your router and hardware support it of course). http://computerworld.co.nz/news.nsf/news/is-your-rsp-ready-for-ipv6-revisite... -- simon (resending since I wasn't sending it from a subscribed address before, sorry if this gets dupped)
Advantages of using IPv6; none really. I can ssh directly to machines (I've set up aaaa records for everything, at home and at the community house) but other than that I only set it up for learning purposes. I've had to reconfigure our filtering system, learn how to use WPAD because I can't redirect ipv6 the same way as ipv4, and generally change all kinds of configuration. xnet supports native ipv6 and has for some time. I called them to ask, and apparently all I need is a better router but I'll probably wait until this one dies or I want to get UFB. And the community house is using Orcon. I've got bind9 set up as a DNS cache and could use it to override facebook's DNS but there are a lot of names, they probably change around all the time too; I just did a quick grep through the squid logs and I don't think this is even a complete list ... 0-act.channel.facebook.com 0-ect.channel.facebook.com 0-pct.channel.facebook.com 1-act.channel.facebook.com 1-ect.channel.facebook.com 1-pct.channel.facebook.com 2-act.channel.facebook.com 2-pct.channel.facebook.com 3-act.channel.facebook.com 3-ect.channel.facebook.com 3-pct.channel.facebook.com 4-act.channel.facebook.com 4-ect.channel.facebook.com 4-pct.channel.facebook.com 5-act.channel.facebook.com 5-ect.channel.facebook.com 5-pct.channel.facebook.com 6-act.channel.facebook.com 6-ect.channel.facebook.com 6-pct.channel.facebook.com act.channel.facebook.com api.ak.facebook.com api.facebook.com apps.facebook.com badge.facebook.com connect.facebook.net ect.channel.facebook.com facebook.com graph.facebook.com pct.channel.facebook.com pixel.facebook.com static.0.facebook.com static.ak.facebook.com www.facebook.com Still, it might be the best answer. I'll just have to keep a watch out for any more names I have to add. On 8 June 2013 19:04, Simon Green <simon(a)simongreen.net> wrote:
On 8 June 2013 13:04, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
So, any thoughts on how I might configure my system (debian 6) to prefer IPV4 for just those two sites but use ipv6 for everything else?
There seems to be some discussion around the problem over here http://forums.whirlpool.net.**au/forum-replies.cfm?t=2110001<http://forums.whirlpool.net.au/forum-replies.cfm?t=2110001>
I'm IPv6 enabled at home, and am not seeing any problems accessing Facebook (using Chromium for Fedora 18, IPv6). I guess it depends on which Facebook web cluster you get directed too.
On 08/06/13 15:32, Michael McDonald wrote:
No idea - but you've aroused my curiosity. What are the advantages of using ipv6 instead of ipv4?
My ISP (Internode in Australia) gives me a single IPv4 address, but 4,722,366,482,869,645,213,696 IPv6 addresses (a /56 block). Considering I usually only have 10 or so devices connected to the network, that is a bit overkill
Moving to IPv6 is a bit like switching from analogue to digital tv. The word has run out IPv4 addresses, and so we need to start using IPv6 to fix this problem in the long run. It will be decades before IPv4 is 'switched off' (if it is at all)
However, its very much a 'chicken and egg' problem where ISPs aren't moving because there is no demand, and providers aren't switching for the same reason.
Most NZ ISP do have plans to enable IPv6 on their networks in the coming years. Snap Internet are the only ISP that are IPv6 enabled for all customers (assuming your router and hardware support it of course).
http://computerworld.co.nz/**news.nsf/news/is-your-rsp-** ready-for-ipv6-revisited<http://computerworld.co.nz/news.nsf/news/is-your-rsp-ready-for-ipv6-revisited>
-- simon
(resending since I wasn't sending it from a subscribed address before, sorry if this gets dupped)
______________________________**_________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/**mailman/listinfo/wlug<http://list.waikato.ac.nz/mailman/listinfo/wlug>
participants (4)
-
Bruce Kingsbury -
Cameron Rangeley -
Michael McDonald -
Simon Green