|
||||||||
I'm thinking about building a "m0n0AP" type distro. Something just for doing wireless access points. I run a WISP and I'm using m0n0wall on my relays. There are a lot of things that I would like to change. So the best thing to do is build a whole new type of distro. I like the m0n0wall interface, so it would be cool be able to keep it. This is all just a thought right now. But maybe I should start hacking on m0n0BSD. One thing that is true. The HostAP drivers are not very good. Still lots of problems with them. On Apr 3, 2004, at 3:28 PM, Chad R. Larson wrote: > At 02:22 AM 4/3/2004, you wrote: >> m0n0wall is a firewall, not an access point or a bridge. And IMHO, >> hostap >> isn't reliable, featureful and fast enough to be a complete >> replacement >> for a real commercial AP. > > The tone of this came off a bit testy. Not that I disagree with you > about > any of it, and I probably would have jumped in a lot sooner if I were > you. It's one thing for folks to want to fork or modify on their own, > it's > another for those not skilled enough to do so to push for it to be > part of > the formal project. > > Maybe cranking up a forked project space on SourceForge would satisfy > some > of those needs. That and the creation of a m0n0wall user's group? > > It'd make me nuts to have something fairly cool I built for myself and > then > decided to share to become a second, uncompensated job. > > -crl > -- > Chad R. Larson (CRL22) chad at eldocomp dot com > Eldorado Computing, Inc. 602-604-3100 > 5353 North 16th Street, Suite 400 > Phoenix, Arizona 85016-3228 > > -- CONFIDENTIALITY NOTICE -- > > This message is intended for the sole use of the individual and entity > to whom it is addressed, and may contain information that is > privileged, confidential and exempt from disclosure under applicable > law. If you are not the intended addressee, nor authorized to receive > for the intended addressee, you are hereby notified that you may not > use, copy, disclose or distribute to anyone the message or any > information contained in the message. If you have received this > message in error, please immediately advise the sender by reply email, > and delete the message. Thank you. > > --epgmakehjchdgbbjbhoa > Content-Type: message/rfc822 > Content-Disposition: inline; filename="m0n0wall_4688.ezm" |