Hi Yeoh, I had done two radio interfaces on a single mesh node (say A), bridge them together (802.1d). If I turn off the STP, enable forwarding, and try to ping any other mesh node (say B), I used to get ping DUPS. Just FYI.
Hi Javier, I have one small problem with your idea. Shouldn't two interfaces (IFACE-1 and IFACE-2) be prohibited from talking over the air. Even if the hop cost of "internal forwarding is zero", if IFACE-1 and IFACE-2 join the same mesh, they will definitely setup peer links between themselves without any blocking. At a quick glance, the overhead of maintaining those inter-module links (specially if AUTHSAE is involved) over the air seems not to be a good idea (no gain). What do you think? ----- Original Message ----- From: "Yeoh Chun-Yeow" <[email protected]> To: "Javier Cardona" <[email protected]> Cc: [email protected], "Bishal Thapa" <[email protected]> Sent: Saturday, December 17, 2011 10:22:12 AM GMT -05:00 US/Canada Eastern Subject: Re: Question about joining meshes together Hi, Javier. Thanks for your explanation. It makes me clearer because I have no idea how should we manage two separate MAC addresses of two separate interfaces and found out that batman-adv uses the terms virtual switch port known as bat0 by using single MAC solution. But neighbors to the second interface would see two-hop paths to the originator interface (the internal forwarding between local interfaces would appear to other nodes as an extra hop with zero cost). Understand. Internal forwarding for two separates interfaces. Anyway, for the mesh node with 2 separate radio interfaces, is it still possible to bridge these two radio interfaces so that we have one single IP address? Please advice. Thanks Regards, Chun-Yeow _______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
