I've contacted the freebsd-mobile list with the question, hopefully
we'll see some results out of there. Like you, googling/mailing list
searching yielded no results for me. :) I _really_ would NOT want to
switch from m0n0wall. It just doesn't make sense to get an embedded pc,
run m0n0wall, and still have to have a seperate AP. I might as well
just go get a cisco AP/router than can do it all. I'm shooting for as
small as possible here. :) I've been told the issue was fixed in 5.x,
but I don't have any experience with device drivers so cannot backport
the changes. From what I've read, the issue lies in the wi driver. It's
even mentioned as a bug in the wi(4) manpage on 4.x, but not on 5.x.
Maybe our beloved m0n0wall devs could look into it? ;) Thanks a bunch
On Oct 23, 2004, at 4:44, Michael Mee wrote:
> I've read there's fixes for the hostap drivers to mitigate this, but
> a few hours digging for them, I haven't found them. Someone with more
> knowledge could probably locate tthem more easily and then hopefully
> the m0n0wall hostap sources...
> However, realistically your best bet is to run a separate AP. Reading
> between the lines, I'm guessing this might not be possible for you?
> you deploying 500000 units of this? Wow!).
> Unless someone can locate the patches in your timeframe (sounds short
> hence unlikely), you might have to go to Pebble
> or wisp-dist or similar - as we've been forced to do for a couple of
> installs where m0n0wall was otherwise perfect :-(.
> Aspiring contributors: if you can find the right hostap patch, you'd be
> doing a great many people a real favor in the m0n0wall community!
> cheers, michael
> ----- Original Message -----
> From: "David Orman" <david dot orman at orbisphere dot net>
> To: <m0n0wall dash dev at lists dot m0n0 dot ch>
> Sent: Friday, October 22, 2004 11:13 PM
> Subject: [m0n0wall-dev] powersaving mode (on clients) causing lots of
> I finally got my senao ext2 card in (200mw prism), upgraded firmware
> to 1.1.1/1.5.6. I spent all day messing with it thinking there was a
> major problem. Let me explain.
> I have a 12" pb I normally use for testing. It was working flawlessly
> with the m0n0wall machine/wireless. Then, I whipped out a toshiba
> laptop w/ integrated wireless, intel mini-pci something or another. I'd
> try to load things, it barely worked sometimes, other times nothing
> worked at all. I spent hours changing firmware revisions etc trying to
> find the problem. Well, unfortunately searching on this list is an
> absolute joke, so that was no help, but I saw something in google
> concerning power saving for an unrelated issue. I said what the heck,
> and disabled power saving mode on the card in the laptop. Walla,
> everything is perfect again. The thing is, with powersaving mode on,
> there was no trouble with my other wireless network (mish mash of
> airport extreme base stations, various cisco 350s and so forth). It
> only has problems with m0n0wall when powersaving is enabled. This is a
> serious issue for me because when I've got 500,000 people attempting to
> login all over this state, and all those with centrino laptops and
> powersaving mode on by default can't connect, there is a problem.
> Unfortunately putting a page on the captive portal explaining it
> doesn't work, since 99% of the time it can't even be loaded w/
> powersaving mode on. I suspect it's some issue with the freebsd
> wireless drivers, has anybody come up with a fix for this yet? I'm not
> in-the-know when it comes to writing drivers, so I really can't assist.
> I really appreciate your time/input/suggestions, this is a show-stopper
> for me until I can get it resolved.
> Thank you as always,
> PS - I read somewhere 1.5.6 is the station firmware to use on fbsd 4.x,
> the others only work well with 5.x+. I've also read wireless got a nice
> overhaul in 5.x, and I suspect this issue was probably one of the
> things fixed. Maybe it's worth looking into? I saw a thread on 5.x
> here, and read some people had troubles. I've been running 5.x for over
> a year now on a few of my database servers which have constant 4+ load
> and no troubles. I guess it just depends on your setup. :) 5.x stable
> is on the way for production use though, so it might be a good option.
> Or, at the least, a backport of fixes to the wireless side of things.
> Also, ipf rocks, ipnat rocks, transparent redirection etc. Really nice
> setup. :) At least worth looking into (for the devs).
> Realized this belonged on the -dev list so here it is. Sorry about
> that. :)
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch