RM5.1 generates error when install new rule under 2.2.9.136

[starcom]

[bravenel]

136 is broken. We will get a fix out.

[bravenel]

Could you show that rule, and also you cut off the left side of the logs screenshot. This may be unrelated to the other thing with 136.

[starcom]

[bravenel]

Update to 137. That works for me as expected:

[starcom]

Thank you

[starcom]

Updated FW, nope; rbooted hub nope; deleted rule & recreated success

[starcom]

Ping always returns zero
RPi4 is PingData(rttAvg: 0.0, rttMin: 0.0, rttMax: 0.0, packetsTransmitted: 0, packetsReceived: 0, packetLoss: 0)

[thebearmay]

Packetloss = 0 normally says that the device responded without any issues, but when the packetsTansmitted is also zero my driver handles it as a no response received. (The system call started doing that occasionally with 2.2.7.121 - never could determine the pattern)

[starcom]

Shut down the RPi, which as two networks: LAN & WiFi

[thebearmay]

@starcom are you on a C-7 or ??

[starcom]

C5 running 2.2.9.137

[bcopeland]

Fix will be on next build

[starcom]

Thank you