IPv6 support
Status: Beta
Brought to you by:
bsl45
Menu
▾
▴
Need a bit more info on the issue. Could you please contact me by email (it's in the udpxy's README file).
Would love to have some background on the IPv6 environment you're running, please contact me via email.
Eather im blind or i didnt see email in README file :) anyway ill just write here what i tought:
Currently im runing dualstack (ipv4&ipv6) network on my LAN... IPv6 currently i just some standard Sixxs tunnel with own subnet, however my ISP is currently testing (in beta stage) native IPv6 for some users so it should be soon i guess. Also with it there might start to advartise IPTV on ipv6 multicast space, instead of ipv4 one.
I tought about something "simple" for start, no need to start with multicast ipv6 (since i guess we cant test it), i would start with something simple like http listening on ipv6. When you specify listetning intefrace it opens sockets on both ipv4 and ipv6 addresses if they are avilable.
No email in README - I was clearly mistaken & wrong - will correct that & make sure all headers have it & all files have a standard header. Added "Contact" section to usage text.
I see your point of making IPv6 transition, will experiment with it and see how easily/soon it could be added in. I must admit, not so many requests I got for IPv6 support. What *is* your ISP, btw?
I have fiber optics in Slovenia... ISP is T-2 and there isnt any public announcment of IPv6 yet, however there is some unoffical forum where there is lots of employees of ISP and we get "back channel" news what they are testing and things like that...
About requests around IPv6, what i think is that people are not generaly thinking about this issue, but fact is we will run out of IPv4 IPs in about half of year or so... even i only noticed this because like i said im runing dualstack IPv4&IPv6 with my own domain. My "router", where im also runing udpxy have both A and AAAA records. So Windows (since Vista onward i think) in case of "proper" dualstack network (and not teredo tunnel) preferes IPv6 over IPv4, so when i was trying to play some udpxy stream from host.domain.net it looked up for ipv6 address and ofc udpxy is not runing http server on ipv6 ip, but only on ipv4 one so it errored out and for a while i didnt got it what was wrong, until i finaly figured it out that Win7 resolves my domain in to ipv6 address and since udpxy is not listening on ipv6 it fails, ofc simple solution is to just go with ipv4 instead of host.domain.net, but i also wrote here like a reminder that ipv6 support will be needed at some point.
Ping …
It is 2014 now, and I just write here to say UPC is rolling out DSLite at least in Switzerland, Austria and probably the neighboring markets as default for new modems.
So even when DSLite is giving you access to CGN (NAT) outbound, It would be nice to have hosts in such networks do HTTP via IPv6 directly, not via nginx or apache listening on ::80 as there is no inbound port forwarding anymore. You need to ask (or buy business contract) now to get a public IPv4 address, which would obviously rule out the home user, or the udpxy user which isn't the main customer (shared living).
I have an environment where I could test IPv6 Multicast as well, so if there are changes on the source side, I'm happy to help out testing.
I still don't have IPv6 support in udpxy at this point (having diverted most of my efforts to another project, gigapxy). On the ISP side, gigapxy handles IPv6, but on the STB side udpxy still lacks IPv6. Cannot give you ETA on IPv6 in udpxy yet but I'll ask the community on the forum to consider making an IPv6 fork of udpxy.