Hmmm okay, another idea ... redw9 could be my 10th AP which has the malfunction now, i wrote about in another post ... this one issnt connected and wassnt connected since the last reboot, maybe that is why we don't see it now ? Is there any configuration file or database where we can have a look about that device?
Every Access Point in the configuration daemon (regardless if it is currently inactive or not) has a related redw device. The actual order is not important, but the tunnel id (the first number in the /proc/net/red output) is always fixed to a certain access point id (the serial on the back of the AP).
If you have 9 APs in the confd, redw0-redw8 will be created; if you have 10 devices, it's 0-9, etc., so the broken AP is has either never been accepted, or was deleted / set to pending state afterwards.
You can check the data in the configuration daemon by doing
# cc get_objects awe device
on the command line, but I'd be very surprised if you find more APs in there than redw device created. [;)]
Every Access Point in the configuration daemon (regardless if it is currently inactive or not) has a related redw device. The actual order is not important, but the tunnel id (the first number in the /proc/net/red output) is always fixed to a certain access point id (the serial on the back of the AP).
If you have 9 APs in the confd, redw0-redw8 will be created; if you have 10 devices, it's 0-9, etc., so the broken AP is has either never been accepted, or was deleted / set to pending state afterwards.
You can check the data in the configuration daemon by doing
# cc get_objects awe device
on the command line, but I'd be very surprised if you find more APs in there than redw device created. [;)]
