Open-Mesh » batman-adv

Sounds interesting. You will have to add filters to different positions in the rx/tx path and parsing functions. You will not have the unicast optimisation... but I think that is not a big problem right now.

I agree with Sven. It doesn't sound too complex.
You would need to add a parsing function in the rx path of the announcement: if it comes from the best GW then you should instruct batman to accept it, otherwise the packet should be rebroadcasted only without being delivered to the interface.

Well, there is one other thing you should consider: How do you propagate a gateway change to your clients ?

When batman switches the gateway it would be nice to have a way to inform your client that the gateway changed. Otherwise they are using an outdated default route to some gateway that may not exist any longer. You will want to keep this time window as short as possible.

radvd have MaxRtrAdvInterval option, it is similar to dhcp timelease.

There is also another interesting option in radvd:

HomeAgentLifetime seconds
The length of time in seconds (relative to the time the packet is sent) that the router is offering Mobile IPv6 Home Agent services. A value 0 must not be used.

http://linux.die.net/man/5/radvd.conf

But, for now, i dont have experience with this option.

When accept_ra_rtr_pref is enabled, what each node needs to do is suggest best gw_server ipv6.
For the best dns nameserver, i think that this can be managed by a good resolvconf configuration

I think the ipv6 gw_mode and the ipv4 one should be separated features end configurable a part, because it can be that some nodes are ipv6 gateways but not ipv4 gateways, and vice versa, and also in the case of a node with both ipv4 and ipv6 gateway announced bandwidth can differ

Hi,

is there any progress on this issue?

• Routing in IPv6 / RA messages are more complex than IPv4 DHCP. A host may have multiple default routes and use 'em on a round robin basis.
• What is a IPv6-gateway mode supposed to do?

• Block foreign RA-Message?
• Mange foreign RA-Messages (Lower route priority, etc.)

• Blocking foreign RAs on gateways is the easiest option - but it is sufficient. (Am I missing sth.)?
• However, it would be nice, if a client (= gw_mode=client) is able to select more than one gateway for redundancy. The number of gateways to select ought to be configurable.

Is there any progress on this?
I'd happy so see an IPv6-Gateway-mode soon.

Jan n/a wrote:

Is there any progress on this?
I'd happy so see an IPv6-Gateway-mode soon.

We also would like to see this feature soon but as far as I know, nobody is working on it. Feel free to pick it up and propose patches.

IPv6 RA can pass through the mesh, for SSIDs that are bridged once the ip6tables FORWARD chain is modified. The default configuration is set to, more or less, forward almost nothing (this includes forwarding through the bridged interfaces) related to IPv6. I've modified my FORWARD chain and included a script file which runs every hour to make sure rules stay active.

Once configured properly, I can remote into any open mesh ssh server via its link local address and RAs propagate through out the mesh and any client will get a RA configured address.

@Eric, I am relative sure that you are writing in the wrong issue tracker. This here is the issue tracker of the open source project batman-adv from the open source developer community open-mesh*.org*. It is not about the commercial AP vendor from open-mesh.com/cloudtrax.com. Please contact their support when you have problems with their product.