On Sat, May 2, 2009 at 4:49 AM, Tom <[email protected]> wrote: > Same here. If I could do a proper test and debugging on this for furthering > the research to fix this, I would gladly do so. ifconfig ral0 debug seems to > give no useful information at time of crash. All I see are handshakes, auths, > and deauths. > > I would really love to know what is making it lock up solid. I can't even send > a > BREAK on the serial console to get into ddb when it locks up solid. All I > can > do is use my trust paperclip to reset the machine. > > I have used rtorrent as a test on the Soekris itself, and it works > fine using the > vr(4) driver. If I ifconfig ral0 down, or even disable ral after boot > -c, the box is > quite reliable and will stay up just fine with high amounts of traffic. > > It definitely seems to be ral(4) and the way that driver interacts with > OpenBSD > and everything else.
This is related to hostap mode and not a Soekris issue. I've had boxes that work fine as ral wireless clients, but once I turn them into ral APs, they dont work very well for long.
