Bug #392

Description

My router had become very unstable: it would lock up and I would often try rebooting to no avail. When I say “lock up”, I mean I could no longer send packets via the wireless interfaces (or get a new address from it); the box would continue to forward packets from another router just fine.

Specifically, the router has been running 3.3.0-rc6 and is a WNDR3700v2.

On the theory I should try to figure out what happened after CeroWrt had been up for a long time, I suffered in silence.

Today, in response to mail on the cerowrt mailing list, I finally noticed that /tmp/log/babeld.log was huge.
-rw-r-r- 1 root root 247936 May 24 12:27 babeld.log

As /tmp is a tmpfs, I suspect that this may be the cause of the unstableness.

root@gw-main:/tmp/log# tail babeld.log
Couldn’t determine channel of interface gw00: Invalid argument.
Couldn’t determine channel of interface gw10: Invalid argument.
Couldn’t determine channel of interface gw00: Invalid argument.
Couldn’t determine channel of interface gw10: Invalid argument.
Couldn’t determine channel of interface gw00: Invalid argument.
Couldn’t determine channel of interface gw10: Invalid argument.
Couldn’t determine channel of interface gw00: Invalid argument.
Couldn’t determine channel of interface gw10: Invalid argument.
Couldn’t determine channel of interface gw00: Invalid argument.
Couldn’t determine channel of interface gw10: Invalid argument.

Gives us another clue.

I should have squirreled away a copy of the whole file before nuking it, but I didn’t. /me bad.

Attachments

• babeld.conf (application/octet-stream; 1.8 kiB) cerowrt 3.3.2-6 babeld.conf Sebastian Moeller May 24, 2012

• babeld.log (application/octet-stream; 257.9 kiB) log for around one day of uptime, mesh routing not used Sebastian Moeller May 24, 2012