From: "Geneviève Bastien" <gbastien@versatic.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] packets not processed by batman on eth0
Date: Thu, 21 Jun 2012 22:38:19 -0400 [thread overview]
Message-ID: <4FE3DA9B.9040401@versatic.net> (raw)
In-Reply-To: <201206211028.18281.lindner_marek@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
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
[-- Attachment #2: leon_files --]
[-- Type: text/plain, Size: 1497 bytes --]
root@leon:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 8000.8a62a119c9ef no bat0
root@leon:~# batctl if
eth0: active
root@leon:/etc/config# cat batman-adv
config 'mesh' 'bat0'
option 'interfaces' 'mesh1'
option 'aggregated_ogms'
option 'ap_isolation'
option 'bonding'
option 'fragmentation'
option 'gw_bandwidth'
option 'gw_mode'
option 'gw_sel_class'
option 'log_level'
option 'orig_interval'
option 'vis_mode'
option 'bridge_loop_avoidance'
# yet another batX instance
# config 'mesh' 'bat5'
# option 'interfaces' 'second_mesh'
root@leon:/etc/config# cat network
config switch 'eth0'
option enable '1'
config switch_vlan 'eth0_0'
option device 'eth0'
option vlan '0'
option ports '0 1 2 3 4 5'
#option ports '0 1 2 3 5'
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config interface 'lan'
option proto 'static'
option netmask '255.255.0.0'
option ipaddr '172.16.11.1'
option type 'bridge'
option _orig_ifname 'eth0'
option _orig_bridge 'false'
option ifname 'bat0'
config interface 'wan'
option ifname 'eth1'
option macaddr '00:0c:41:14:e0:90'
option proto 'dhcp'
config interface 'wifi'
option 'proto' 'static'
option ipaddr '192.168.22.1'
option netmask '255.255.0.0'
config interface 'bat0'
option ifname 'bat0'
option proto 'none'
option mtu '1500'
config interface 'mesh1'
option proto 'none'
option ifname 'eth0'
option mtu '1528'
next prev parent reply other threads:[~2012-06-22 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 2:27 [B.A.T.M.A.N.] packets not processed by batman on eth0 Geneviève Bastien
2012-06-21 8:28 ` Marek Lindner
2012-06-22 2:38 ` Geneviève Bastien [this message]
2012-06-22 3:03 ` Matthias Schiffer
2012-06-22 18:53 ` Geneviève Bastien
2012-06-22 19:08 ` Marek Lindner
2012-06-23 3:08 ` Geneviève Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE3DA9B.9040401@versatic.net \
--to=gbastien@versatic.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox