On Wed, May 29, 2013 at 07:30:13PM -0400, cmsv wrote:

As i am about to try out alfred i already face myself with a couple issues:

http://www.open-mesh.org/projects/open-mesh/wiki/Alfred http://git.open-mesh.org/alfred.git/blob_plain/refs/heads/master:/README

I the past i had removed ipv6 support since i do not need it and it helps trimming up the final image. (most routers and people still use 4 mb flash)

I would like to use alfred and would also like to know if compiling the image with <*> kmod-ipv6................................................... IPv6 support

Leaving out : [ ] ping6 [ ] Enable IPv6 support [ ] Enable IPv6 support in packages

will allow Alfred to work as intended. As anyone tested?

You will only need basic support for alfred. I don't know if "Enable IPv6 support" is mandatory or not. alfred relies on link local addresses configured on your interface.

Another problem with using ipv6 is the final image size. kmod-ipv6_3.3.8-1_ar71xx.ipk is at least 138K An that is quite a bit ...

You can disable IPv4 in return. :D

Just kidding ... but IPv6 will become more popular, we can't deny it forever. Anyway, alfred is built on top of IPv6 link local multicast and there is no plan to change that.

What are exactly the reasons why alfred does not use ipv4 ?

We wanted to have alfred working without requiring user configuration of the interface (IP addresses etc). This left the choice to use either another Ethertype and special Ethernet frames, or IPv6 multicast. As we did not want to add more custom Ethernet types (some switches don't like that, and alfred is payload traffic and does not just stays in the Ad-Hoc WLAN), and IPv6 allows longer messages due to built-in fragmentation, we decided to go for IPv6.

Cheers, Simon