Description
Maintainer: @simonwunderlich
Environment: mediatek/filogic, Xiaomi Redmi Router AX6000 (OpenWrt U-Boot layout), OpenWrt SNAPSHOT r25589-f84ed09d2c
Description:
This my config below, I don't use VLANs, I also turned off dhcp for non-master nodes (by disabling dnsamsq, odhcpd)
For /etc/config/network
...
config device
option name 'br-lan'
option type 'bridge'
list ports 'bat0'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
...
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.x.2'
option netmask '255.255.255.0'
option ip6assign '60'
...
config interface 'bat0'
option proto 'batadv'
option routing_algo 'BATMAN_IV'
option aggregated_ogms '1'
option bridge_loop_avoidance '1'
option gw_mode 'client'
option hop_penalty '30'
option network_coding '0'
config interface 'bat0_mesh0'
option proto 'batadv_hardif'
option master 'bat0'
option mtu '2304'
...
For /etc/config/wireless
...
config wifi-iface 'mesh0'
option device 'radio1'
option mode 'mesh'
option mesh_id 'xxxxxxxx'
option encryption 'sae'
option key 'xxxxxxxx'
option mesh_fwding '0'
option mesh_rssi_threshold '1'
option network 'bat0_mesh0'
...
Now I see that my nodes will connect to mesh peers after booting, but the RX is always at a rate of 0, and at the same time I can't access the internet. I tested by batctl ping MAC on the master node and found Destination Host Unreachable. Then I set the gateway IP, manually connected to the non-master node, and after restarting bat0 and bat0_mesh0, the network is up!
I haven't used batman in a long time because the batman+dawn combo I had set up for myself at the time often made wireless unusable because of br-lan: received packet on bat0 with own address as source address
I thought batman by default was supposed to wait for mesh to get up before starting?
Activity