Hello,
I talked to marec last week on irc (I'm tahini). I have a linksys router that runs batman on the eth0 interface and other routers or laptops are connected to it. Problem is, even though the batman packets pass from the other machines to the linksys, it seems something weird happens on the linksys and the interface is not recognized as a batman neighbor.
As a follow-up with the discussion with marec, here is the detail of my configuration and the logs I get from 3 machines. It seems leon (the linksys router) receives the packets, but does not process them. I updated to latest batman 2012.2 and still the same.
Can anyone help?
Thanks, Geneviève
Hi,
I talked to marec last week on irc (I'm tahini). I have a linksys router that runs batman on the eth0 interface and other routers or laptops are connected to it. Problem is, even though the batman packets pass from the other machines to the linksys, it seems something weird happens on the linksys and the interface is not recognized as a batman neighbor.
the problem is that leon does not receive any packets from its neighbors. Its log only repeatedly states "Sending own packet" but no information about incoming packets is printed. If you compare it with the other logs you will see what I mean. A common mistake leading to this symptom is a bridge misconfiguration. Is eth0 on leon part of a bridge ?
Cheers, Marek
Hi,
On 12-06-21 04:28 AM, Marek Lindner wrote:
Hi,
I talked to marec last week on irc (I'm tahini). I have a linksys router that runs batman on the eth0 interface and other routers or laptops are connected to it. Problem is, even though the batman packets pass from the other machines to the linksys, it seems something weird happens on the linksys and the interface is not recognized as a batman neighbor.
the problem is that leon does not receive any packets from its neighbors. Its log only repeatedly states "Sending own packet" but no information about incoming packets is printed. If you compare it with the other logs you will see what I mean.
But doesn't the 'batctl td eth0' output show it receives the packets from the neighbors? What happens to those packets?
A common mistake leading to this symptom is a bridge misconfiguration. Is eth0 on leon part of a bridge ?
No, the bat0 interface is on the bridge, but eth0 is a vlan, I think. Maybe it is a vlan misconfiguration? Attached are some outputs and config files from leon. What other commands should I look for to help find the problem?
Thanks, Geneviève
Hi, it might be your VLAN configuration - as far as I know, 0 is not a valid VLAN id.
But I also found that batman-adv doesn't work on VLAN interfaces on my OpenWRT routers. As a workaround you can create a new bridge that only contains the VLAN interface and add the bridge to bat0 instead.
Regards, Matthias
On 06/22/2012 04:38 AM, Geneviève Bastien wrote:
Hi,
On 12-06-21 04:28 AM, Marek Lindner wrote:
Hi,
I talked to marec last week on irc (I'm tahini). I have a linksys router that runs batman on the eth0 interface and other routers or laptops are connected to it. Problem is, even though the batman packets pass from the other machines to the linksys, it seems something weird happens on the linksys and the interface is not recognized as a batman neighbor.
the problem is that leon does not receive any packets from its neighbors. Its log only repeatedly states "Sending own packet" but no information about incoming packets is printed. If you compare it with the other logs you will see what I mean.
But doesn't the 'batctl td eth0' output show it receives the packets from the neighbors? What happens to those packets?
A common mistake leading to this symptom is a bridge misconfiguration. Is eth0 on leon part of a bridge ?
No, the bat0 interface is on the bridge, but eth0 is a vlan, I think. Maybe it is a vlan misconfiguration? Attached are some outputs and config files from leon. What other commands should I look for to help find the problem?
Thanks, Geneviève
Wow! It works! I just added the line option 'type' 'bridge' to my mesh1 interface and my whole mesh is now working. Thanks!
Was that documented somewhere? It gave me quite a headache for such a simple solution.
Thanks, Geneviève
On 12-06-21 11:03 PM, Matthias Schiffer wrote:
Hi, it might be your VLAN configuration - as far as I know, 0 is not a valid VLAN id.
But I also found that batman-adv doesn't work on VLAN interfaces on my OpenWRT routers. As a workaround you can create a new bridge that only contains the VLAN interface and add the bridge to bat0 instead.
Regards, Matthias
On 06/22/2012 04:38 AM, Geneviève Bastien wrote:
Hi,
On 12-06-21 04:28 AM, Marek Lindner wrote:
Hi,
I talked to marec last week on irc (I'm tahini). I have a linksys router that runs batman on the eth0 interface and other routers or laptops are connected to it. Problem is, even though the batman packets pass from the other machines to the linksys, it seems something weird happens on the linksys and the interface is not recognized as a batman neighbor.
the problem is that leon does not receive any packets from its neighbors. Its log only repeatedly states "Sending own packet" but no information about incoming packets is printed. If you compare it with the other logs you will see what I mean.
But doesn't the 'batctl td eth0' output show it receives the packets from the neighbors? What happens to those packets?
A common mistake leading to this symptom is a bridge misconfiguration. Is eth0 on leon part of a bridge ?
No, the bat0 interface is on the bridge, but eth0 is a vlan, I think. Maybe it is a vlan misconfiguration? Attached are some outputs and config files from leon. What other commands should I look for to help find the problem?
Thanks, Geneviève
On Friday, June 22, 2012 20:53:57 Geneviève Bastien wrote:
Wow! It works! I just added the line option 'type' 'bridge' to my mesh1 interface and my whole mesh is now working. Thanks!
Was that documented somewhere? It gave me quite a headache for such a simple solution.
Do you mind explaining your solution in greater detail ? So far, I don't quite follow your approach.
Cheers, Marek
On 12-06-22 03:08 PM, Marek Lindner wrote:
On Friday, June 22, 2012 20:53:57 Geneviève Bastien wrote:
Wow! It works! I just added the line option 'type' 'bridge' to my mesh1 interface and my whole mesh is now working. Thanks!
Was that documented somewhere? It gave me quite a headache for such a simple solution.
Do you mind explaining your solution in greater detail ? So far, I don't quite follow your approach.
Cheers, Marek
As Matthias suggested, I just changed my mesh1 interface, which was just using the eth0 vlan interface, to a bridged interface. So my mesh1 is now a bridge interface with only eth0 on it. (mesh1 is the interface I add to the batman-adv file.)
In my /etc/config/network file, my mesh1 interface now looks like this
config interface 'mesh1' option proto 'none' option type 'bridge' # this line added from before, nothing else changed option ifname 'eth0' option mtu '1528'
It seems batman-adv really does have a problem with vlans on openwrt. Why? I don't know...
Cheers, Geneviève
b.a.t.m.a.n@lists.open-mesh.org
-
Geneviève Bastien -
Marek Lindner -
Matthias Schiffer