Hello All;
I am truing to setup two batman openWRT nodes;
I have that topology br-lan 0002.001e8cc9451b yes bat0 eth0 eth1 wlan0
Counters of RX & TX packets are increase on wlan0, but no RX packets on Batman Iface Bat0 In logs first(ha00) node i am only see "[ 69443] Sending own packet (originator c4:17:fe:b4:0b:97 seqno 70438, TQ 255, TTL 50, IDF off) on interface wlan0 [c4:17:fe:b4:0b:97]". Second(ha01) node I am see "[ 69553] Sending own packet (originator c4:17:fe:b2:50:c8 seqno 70549, TQ 255, TTL 50, IDF off) on interface wlan0 [c4:17:fe:b2:50:c8]" What am i doing wrong?
First Node don't see Second Node. Bat Setup: ha00 - /etc/config/wireless: config wifi-device radio0 option type mac80211 option channel 1 option macaddr c4:17:fe:b4:0b:97 option hwmode 11g option htmode HT20 list ht_capab SHORT-GI-40 list ht_capab TX-STBC list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40
config wifi-iface option device radio0 option network lan option mtu 1527 option mode ahdemo option ssid g_mesh option encryption none /etc/config/batman-adv
config 'mesh' 'bat0' option 'interfaces' 'wlan0' option 'orig_interval' option 'log_level' option 'aggregated_ogms' option 'bonding' option 'vis_mode' ------------------------------------- ha01 - /etc/config/wireless config wifi-device radio0 option type mac80211 option channel 1 option macaddr c4:17:fe:b2:50:c8 option hwmode 11g option htmode HT20 list ht_capab SHORT-GI-40 list ht_capab TX-STBC list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40
config wifi-iface option device radio0 option network lan option mode ahdemo option ssid g_mesh option encryption none
/etc/config/batman-adv config 'mesh' 'bat0' option 'interfaces' 'wlan0' option 'orig_interval' option 'log_level' option 'aggregated_ogms' option 'bonding' option 'vis_mode' .
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Please check http://www.open-mesh.org/wiki/batman-adv-quick-start-guide and try starting with a simpler setup first.
Also have a look at http://www.open-mesh.org/wiki/batman-adv-troubleshooting, if there's anything missing in this one, we'll be happy to add it.
Cheers, Linus
On Thu, Jan 20, 2011 at 01:31:34PM +0600, Michael Y. Gluhovchenko wrote:
Hello All;
I am truing to setup two batman openWRT nodes;
I have that topology br-lan 0002.001e8cc9451b yes bat0 eth0 eth1 wlan0
Counters of RX & TX packets are increase on wlan0, but no RX packets on Batman Iface Bat0 In logs first(ha00) node i am only see "[ 69443] Sending own packet (originator c4:17:fe:b4:0b:97 seqno 70438, TQ 255, TTL 50, IDF off) on interface wlan0 [c4:17:fe:b4:0b:97]". Second(ha01) node I am see "[ 69553] Sending own packet (originator c4:17:fe:b2:50:c8 seqno 70549, TQ 255, TTL 50, IDF off) on interface wlan0 [c4:17:fe:b2:50:c8]" What am i doing wrong?
First Node don't see Second Node. Bat Setup: ha00 - /etc/config/wireless: config wifi-device radio0 option type mac80211 option channel 1 option macaddr c4:17:fe:b4:0b:97 option hwmode 11g option htmode HT20 list ht_capab SHORT-GI-40 list ht_capab TX-STBC list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40
config wifi-iface option device radio0 option network lan option mtu 1527 option mode ahdemo option ssid g_mesh option encryption none /etc/config/batman-adv
config 'mesh' 'bat0' option 'interfaces' 'wlan0' option 'orig_interval' option 'log_level' option 'aggregated_ogms' option 'bonding' option 'vis_mode'
ha01 - /etc/config/wireless config wifi-device radio0 option type mac80211 option channel 1 option macaddr c4:17:fe:b2:50:c8 option hwmode 11g option htmode HT20 list ht_capab SHORT-GI-40 list ht_capab TX-STBC list ht_capab RX-STBC1 list ht_capab DSSS_CCK-40
config wifi-iface option device radio0 option network lan option mode ahdemo option ssid g_mesh option encryption none
/etc/config/batman-adv config 'mesh' 'bat0' option 'interfaces' 'wlan0' option 'orig_interval' option 'log_level' option 'aggregated_ogms' option 'bonding' option 'vis_mode' .
Linus Lüssing wrote:
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Hi All
If I can jump in here, I had the same prob with batman L3 in wrt with the bridge!
Killing the Br-lan bridge kills everything, I eventually solved it by flashing a old kamakaze version : pre bridge version, which provides the simple ,
eth0, eth1 , scenario!
Wayne A
On Thu, Jan 20, 2011 at 10:37:47AM +0200, wayne wrote:
Linus Lüssing wrote:
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Hi All
If I can jump in here, I had the same prob with batman L3 in wrt with the bridge!
Killing the Br-lan bridge kills everything, I eventually solved it by flashing a old kamakaze version : pre bridge version, which provides the simple ,
eth0, eth1 , scenario!
Wayne A
Sorry, but I don't get it, how are the batman-adv and batmand bridge issues related? Why should an older OpenWRT "fix" this? In this scenario I'm 100% that using a different OpenWRT version will _not_ help Michael, as it is a conceptual issue, not a bug or so.
What kind of pre bridge version are you talking about?
Cheers, Linus
Linus is correct. You cannot bridge the wireless interface with bat0. The wireless interface is managed by bat0. bat0 gets bridged with your lan port(s).
If you remove the line 'option network lan' from /etc/config/wireless it should start working.
I have batman-adv running quite well on both kamikaze and backfire with atheros/madwifi.
I did, however have to play around with MTU settings to get it working at an acceptable throughput. Also, by default, the interface 'wlan0' is in /etc/config/batman-adv and I had to change that to 'ath0' for atheros..
On 1/20/2011 4:52 AM, Linus Lüssing wrote:
On Thu, Jan 20, 2011 at 10:37:47AM +0200, wayne wrote:
Linus Lüssing wrote:
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Hi All
If I can jump in here, I had the same prob with batman L3 in wrt with the bridge!
Killing the Br-lan bridge kills everything, I eventually solved it by flashing a old kamakaze version : pre bridge version, which provides the simple ,
eth0, eth1 , scenario!
Wayne A
Sorry, but I don't get it, how are the batman-adv and batmand bridge issues related? Why should an older OpenWRT "fix" this? In this scenario I'm 100% that using a different OpenWRT version will _not_ help Michael, as it is a conceptual issue, not a bug or so.
What kind of pre bridge version are you talking about?
Cheers, Linus
Linus Lüssing wrote:
On Thu, Jan 20, 2011 at 10:37:47AM +0200, wayne wrote:
Linus Lüssing wrote:
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Hi All
If I can jump in here, I had the same prob with batman L3 in wrt with the bridge!
Killing the Br-lan bridge kills everything, I eventually solved it by flashing a old kamakaze version : pre bridge version, which provides the simple ,
eth0, eth1 , scenario!
Wayne A
Sorry, but I don't get it, how are the batman-adv and batmand bridge issues related? Why should an older OpenWRT "fix" this? In this scenario I'm 100% that using a different OpenWRT version will _not_ help Michael, as it is a conceptual issue, not a bug or so.
What kind of pre bridge version are you talking about?
Cheers, Linus
Hi Linus
I understand the issue is unrelated, My point was for the beginner, the bridging concept (br-lan) used in later versions of wrt, can cause slight confusions.
Most of the howto's don't take this into account, and only refer to the Plain eth0,eth1, or wlan0.
It really is not ideal, but once one has Batman running this way, the light will come on!
My 2c.
Wayne A
b.a.t.m.a.n@lists.open-mesh.org
-
Linus Lüssing -
Michael Y. Gluhovchenko -
Tom Cannon -
wayne