7 replies to this topic

[rassilon]

currently i'm preparing to switch to openwrt with ipv6 firmware because

1) our service provider has started on october 10th to offer dual-stack, ipv4 and full NATIVE IPv6 support, with /64 routable prefixes offered via dhcpv6 prefix delegation, so that hosts behind routers have publicly-reachable ipv6 addresses

and also because
2) dd-wrt doesn't currently support AT ALL native ipv6 and dhcpv6 prefix delegation

any chance we can get the hotspot system to work with ipv4+ipv6 (on openwrt), preferably with dual ssid support ?

Edited by rassilon, 02 November 2011 - 08:18 PM.

[oliver]

The dual ssid (hotspot+internal) can be simply solved with dd-wrt. I don't think IPv6 will be supported in hotspots soon because 256*256=655536 (192.168.x.x) will be more than enough IP addresses for hotspot users..

[Roland]

Oliver is right, IPv6 may be only needed for communicating a radius server which has an IPv6 address but you don't have to care about this as you will use our hosted radius server.

Hotspot addresses are internal IP addresses always which are fine with IPv4.

[winkleburyctr]

If we keep hotspot users on ipv4 and not provide a gateway to ipv6 then as new sites appear that cannot get ipv4 addresses because of the now exhausted stockpile then these new sites will be invisible to our users. Ipv6 is a must for longterm viability! Also, with ip6 NAT has been deprecated in favour of proper routing. There is already a beta-quality software that supports ip6 called pepperspot. This is a fork of early chillispot source.

[Roland]

Again, hotspot addresses are internal addresses. The ipv6 gateway to the internet has to be provided by you with a gateway which can handle ipv6. Hotspot users only got an internal IP, they are not getting an internet IP address.

So if you can gets router which has ipv6 support and runs standard coovachilli or chillispot, it would be fine. Or you can have a router with ipv6 support and an other hotspot router which can be an ipv4 only.

[winkleburyctr]

I think you're missing the point that ipv4-space to ipv6-space traffic cannot happen unless the chillispot/coovachilli hotspot system supports it. you cannot just say "get a router has ipv6 support, and runs standard chillispot, it would be fine" because it doesn't work like that. ipv6 is not backwards compatible with ipv4, hence the need for dual-stacking. In the period where there are sites hosted on ipv4 addresses and other sites on ipv6 we need to provide our users the ability to connect to both systems. Once the ipv4 addresses have died out we still need to provide our users ipv6 addressing all the way to their system.

IPv4 NAT is not sufficient to map a public ipv6 address/subnet to our 192.168.182.0/24 range because:

1. ipv4 nat doesn't know how to map the networks and never will,
2. NAT is obsolete as stipulated by the ipv6 working group, and therefore there is no such thing as IPv6Nat (and there NEVER will be!),
3. the two networks are incompatible with each other,
4. if the client is given an ipv4 address only they will assume that they aren't connected to ipv6 networks and therefore will not issue AAAA requests to DNS,
5. even if they issued an AAAA request and received 2a00:1450:400c:c01::69 in response the routing tables in their host OS will complain that there is no route adequate for the network in question, (see point 3)
6. if somehow you could trick the routing tables in the client's OS to forward the packet to 192.168.182.1 we return to problem 1 & 2.

Edited by winkleburyctr, 05 February 2012 - 11:42 PM.

[cybermaus]

Long term I have to agree with winkleburyctr: A website that has a v6-only address will never be reachable by a client that has a v4 address. Also not if that V4 address is nat'ted onto a v6 network, so repeated claims about it being a ISP responsibility may not be on the mark.

Short term I am not too worried yet, I suspect we will soon see v6-only consumer addresses, but hosting like web pages will probably be on a mixed v4/v6 address for a while longer. At this point it is more important that underlying software is developed (like peperspot), services like HotSpotSystem can lag behind a bit.

Edited by cybermaus, 06 February 2012 - 11:49 AM.

[avibp]

Since there is no compatiblity between ipv4 and ipv6, the later will never be adobpted and the internet will die because the world will not all upgrade at the exact same time and the exact same moment, day, week, month year.

Obviously ipv6 IS going to be adopted and the net WON'T die.

Something is missing in the discussion beyond dual stack.  Maybe DNS cubed (squared?)

As far as hotspotsystem is related:  When is the drop dead ETA for ipv4 and ETA for full ipv6 to be implemented?  Hotspotsystem needs to be ready well before those dates indeed and it ain't this or next year and I bet not for another 3 (to maybe 8) years.

BUT, I don't know and I would like to know what is the missing part in the migration as well.
;-) Never mind 12-21-12 is coming first anyway. ;-)

Edited by avibp, 21 October 2012 - 04:56 AM.