Ethernet connections go down until restart in mixed wired-wireless network

[der-nele]

not sure were to put this problem
i admin a libremesh in leipzig whis bmx7, batman and OpenWrt 19.07.6

the bug comes ca. all second month /also with older versions of OpenWrt

all ethernet connections in the lokal-mesh break down.
and do not come back by it one

the mesh is bild up out of ca 10x tplink 3600 and one loco-m (behinde the setra-5ghz are more ssid's)
8 from 11 nodes are connected via lan

see map downstairs
______=kabel/mesh
&&&= wifi/mesh

my problem is that the routers are isolatet if the ethernet gos down and i have to shout down the hole area (40 peaple) from
electricity ore walk to all routers and make on/off

my question is whitch things i have to lock up if it happend again. or are there other things i can try

thanks for interest
nele
ps: sorry for the bad spelling. is not my best skill.

[der-nele]

the map and 2 logreads

2logreads.txt

[der-nele]

it happend again. / i think there is a connection between bmx7 and a split of one ssid.
we have often that the fuse from elektricety came. so sometime a node in the middle turn of. i think this can trigger the bug. we had this also when we did update with a new communety file =(new ssid) as we update one node in the middle before the other notes were new. the same happens. wifi mesh= yes but no eternet at any node in the ssid
ethernet-bug.txt

feel free to correct or ask questions for better understanding...

[spiccinini]

Hi! Sorry for the delay, I've never used bmx7 myself. Do you think it is a bmx7 issue? Maybe it would be a good idea to report it to https://github.com/bmx-routing/bmx7/issues

Or do you think it is a libremesh issue?

I don't understand exactly, the issue is that when the ethernet goes down and then back online the mesh is split and does not rejoin and you have to unplug the ethernet cable and replug it manualy?

[der-nele]

jes can be bmx7

the ethernet interfaces fron every node are of at the same time and do not com back. althow no ping ff02::1%br-lan (just if there is a wifi-mesh neighbour)

[ilario]

@der-nele is this issue still happening?
We are planning to not support BMX7 in the next release (see #977), as we feel that its support in LibreMesh is not active. Do you agree or it is working well for you?

[der-nele]

@ilario
yes it still happens and i do not now how. but...
for me it would be nice to have one more update with bmx7 just to not be forced for such and learn about an other firmware.

[der-nele]

i already call out for helb to find an other firmware.
if you now some how is in Leipzig how like big challenge. and knows about libremesh "standard" or have an other stable firmware let me know.

[ilario]

Did you find a solution @der-nele ?

You can try using deferable-reboot package that reboots the routers periodically. You may want to add something like this script that delays the reboot until when some check fails:
#1023

As you are connecting LibreMesh routers by cable, you should really configure that ethernet port for being out of the br-lan bridge.
With DSA (modern routers with modern OpenWrt), you can usually easily configure the ethernet ports one by one. Read here:
#1121
and apply to those ports this interface-specific configuration:

lime-packages/packages/lime-docs/files/www/docs/lime-example.txt

Lines 231 to 235 in 6642f37

	## (optional) configure lan1 for connection to other nodes, not for users connection:
	config net
	option linux_name 'lan1'
	list protocols 'batadv:%N1' #needs to be specified if the other node is in the same mesh cloud i.e. same ssid
	list protocols 'babeld:17'

If you just have something like eth0.1 and it includes all of the LAN ports, you have two options:

1. configure all of the ports of that router for mesh-only (this is a problem if you have both a libremesh node and a cabled clients connected by cable on the same libremesh router).
2. find out how to split the eth0.1 interface and then configure them separately. I personally never did it.

Sometimes the speed autonegotiation on the cable gets crazy. It could change from fast ethernet to gigabit even if gigabit does not work. In that case you will need to include an ethtool command somewhere setting the speed to fast ethernet (100M) and disabling the autonegotiation.