-
Notifications
You must be signed in to change notification settings - Fork 325
Troubleshooting
Martin Weinelt edited this page Feb 18, 2018
·
7 revisions
The device br0
complains, that it has seen packets from it's own mac address arrive on the bridge port bat0
, the batman-adv mesh interface.
Check batctl tg
for the mac address of br0
and find out who originates the mac address in the mesh. Resolve the originators mac address through respondd data, for example through a nodes.json
file.
# dmesg
[...]
[ 1877.476355] dom61-br: received packet on dom61-bat with own address as source address
[...]
# ip link show dev dom61-br
47: dom61-br: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether da:ff:61:00:02:04 brd ff:ff:ff:ff:ff:ff
# batctl -m dom61-bat tg | grep "da:ff:61:00:02:04"
* da:ff:61:00:04:04 -1 [....] ( 7) a6:fb:16:8d:c1:7b ( 7) (0x3b6ea962)
The offender in this case was a6:fb:16:8d:c1:7b
.
-
Usage
-
Community
-
Development
- Device Integration
- Roadmap
- Release-life-cycle
- Protocols
- Meeting 2024/05
- Meeting 2024/03
- Meeting 2024/02
- Meeting 2024/01
- Meeting 2023/06
- Meeting 2023/05
- Meetup-CCCamp
- Meeting 2023/04
- Meeting 2023/03
- Meeting 2023/02
- Meeting 2023/01
- Meeting 2022/06
- Meeting 2022/05
- Meeting 2022/04
- Meeting 2022/03
- Meeting 2022/02
- Meeting 2022/01
- Meeting 2021/01
- Meeting 2019/01
- Meeting 2018/03
- Meeting 2018/02
- Meeting 2018/01
- Meeting 2017/01
- Concepts
- Release Process
-
Debugging