Last night I transferred dude-3.10-mipsle.npk to my router so that I could begin using DUDE to monitor my network. When I rebooted, my router came up with only the hardwired interfaces defined. I have three wireless interfaces in the router, none of them show up. The router generates an autosupout.rif file every time it comes up, but since I have no way to decode them I have no clue as to what its issue is. I can't find any relevant error messages in /log print. I tried disabling the DUDE package and rebooting, then removing the DUDE package and rebooting, and this did not correct the problem.

Here's the real puzzler: I have the router configured to auto-mail autosupout.rif files to me. Every time I reboot, it mails me this file, and I receive it -- despite the fact that the only way for this mail to reach me is over one of the wireless interfaces! This proves that the interfaces must be working at some time in the boot process, but later become undefined.

How can I find out what this router's problem is? I have customers waiting for service. Thank you for any help.

Last night I transferred dude-3.10-mipsle.npk to my router so that I could begin using DUDE to monitor my network.

hopefully the router itself is running v3.10.

Assuming that there are no version conflicts, I would try to downgrade to a lower version, and then re-upgrade.

Otherwise....... it may be time for Netinstall
http://wiki.mikrotik.com/wiki/Netinstall

Everything on the router is 3.10. I certainly hope it won't come to needing NetInstall. This router is 50 feet up in a tower and I have no serial port access.

/system packages
see what is installed, wonder if your wireless package is not installed anymore!

Good guess, but it's there. One of the things I did last night to try to solve the problem was reinstall the entire routeros-mipsle-3.10.npk, so everything in there should be fresh. But it's still hosed.

The wireless hardware is still working, because one can telnet into the MikroTik over the public-side wireless connection using MAC Telnet, and the log shows customer client radios associating and disassociating from the private-side omni radio. It's the interface NAMES that seem to have disappeared and won't come back.

/system check-installation

might yield more clues or information.....

My local MikroTik guru has spent hours checking the config and software, and found nothing questionable except the router's behavior. We are in agreement that it is most likely a hardware failure, so he has taken it back to his shop to isolate components. Thanks to all who attempted to help.

in some cases where the interfaces disappear, it helps to hard powerdown by unplug for 30 seconds then plug back in.

Thank you. We did try this yesterday, with no effect.

Hardware passed all tests, but the ARP mechanism was totally fried. What solved the problem was re-flashing the BIOS. It looks like the culprit here may indeed have been the installation of DUDE 3.10, possibly in combination with the release and the particular motherboard (532) at my installation. I won't be attempting to reinstall this package.