packet 60% loss for after node disconnection
my configuration is the following :
+-------+ +---------------+ |laptop |<---->|batman GateWay |<----> batman nodes(A,B,C) +-------+ +---------------+
- the laptop is not a part of the batman network. it is connected to the GW via ethernet
- all the batman nodes are RocketM5 running batman 2017.1 BATMAN_V
- All nodes are connected to batman network.
- Node A is shut down
Ping to node B and C from laptop has about 65% packet loss
Updated by Sven Eckelmann over 3 years ago
- Status changed from New to Rejected
There is no batmand 2017.1.
The bug description is also quite odd. Why is it expected to have lower than 65% packet loss when you remove the nearest  node which had a good connection  to the batman-adv gateway? A bad connection  will result in packet loss - so nothing unexpected here.
The bug also doesn't describe whether this is a temporary problem (which could be expected until a node times out in the originator table) or is a stable problem over multiple hours.
 at least I would assume that A is the nearest. Bug description is missing any information about that
 at least I would guess that it had a good connection. Bug description is missing any information about that
 at least I would guess that the connection to B and C from the gateway is bad. Bug description is missing any information about that