Probably not an issue, but is is possible to use ipv6 instead of ipv4 for the flukso? I guess server-side would be something different, but using local 6to4 translation would enable me to go native ipv6 for all hardware.
The first step will be to IPv6-enable the Flukso server. Then we'll have to include some (kernel) modules on the FLM02's in a new firmware release. See [1] and [2] as an intro. Lastly, we'll need to adapt the local networking web page to accommodate those longer addresses.
IPv6 support on the flukso server might not be a big deal, but that depends on the provider you're using for hosting. Not to make it a small matter, but when the provider is ipv6 enabled, it would only take basic setup changes.
Adding the proper ipv6 kernel modules to the FLM02's and enabling ipv6 should not be much of a big deal either, afaik ipv6 networking works and routers will be discovered automagically.
Folks using ipv6 locally will probably be using a proper dns as it is impractical to not use names for ipv6 addressing. When the web pages are using relative paths, this should work.
I'm willing to do some testing, please contact me by email when you need some info. When DNS64 and NAT64 are setup here, we'll be no longer using ipv4 stacks.
Cheers!
limpens |
ps: installing kmod-ipv6 doesn't help here, apparently the kernel isn't able to do ipv6 (for now).
The first step will be to IPv6-enable the Flukso server. Then we'll have to include some (kernel) modules on the FLM02's in a new firmware release. See [1] and [2] as an intro. Lastly, we'll need to adapt the local networking web page to accommodate those longer addresses.
[1] http://wiki.openwrt.org/doc/howto/ipv6.essentials
[2] http://wiki.openwrt.org/doc/howto/ipv6
Happy IPv6 launch day!
IPv6 support on the flukso server might not be a big deal, but that depends on the provider you're using for hosting. Not to make it a small matter, but when the provider is ipv6 enabled, it would only take basic setup changes.
Adding the proper ipv6 kernel modules to the FLM02's and enabling ipv6 should not be much of a big deal either, afaik ipv6 networking works and routers will be discovered automagically.
Folks using ipv6 locally will probably be using a proper dns as it is impractical to not use names for ipv6 addressing. When the web pages are using relative paths, this should work.
I'm willing to do some testing, please contact me by email when you need some info. When DNS64 and NAT64 are setup here, we'll be no longer using ipv4 stacks.
Cheers!
ps: installing kmod-ipv6 doesn't help here, apparently the kernel isn't able to do ipv6 (for now).
Eric.