Re: Ad-Hoc with Windows?
"M. Warner Losh" <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.mobile |
|---|---|
| Message-ID | <[email protected]> |
: > - The BSDs are doing it wrong. We should be using IBSS mode, not demo : > ad-hoc. ad-hoc is insufficient. We should create a media option like OpenBSD has called master-ibss which does the right thing for the different types of hardware. : > - IBSS mode works with all systems I've tried it with. Assuming that you have new enough firmware in your lucent cards. : > - To set IBSS mode with Lucent cards, use -p 1 (just like managed mode : > or whatever we'll call it this time). Assuming that you have new enough firmware in your lucent cards. You need at least 6.0.3 to be able to use non-demo mode ad-hoc (IBSS). Otherwise, it won't work, according to reports I've seen. : > - On the Lucent cards, you don't get a signal strength indication. Lucent cards are the only ones I've seen that have good signal indication. However, it is in wicontrol -C only, not in the normal wicontrol output. : > One of the details about which Wes and I couldn't agree was whether an : > IBSS can route to the outside world. I say yes, because any system in : > the IBSS can have other interfaces as well. This isn't covered in the : > 802.11 standard, of course. Wes says no, because the 802.11 standard : > (available for free from : > http://standards.ieee.org/getieee802/download/802.11-1999.pdf, which : > is nevertheless a web page) says that interconnection only works with : > BSS (i.e. managed) mode. I claim that this just refers to link-level : > interconnection, and that IP routing has nothing to do with 802.11. : > Comments welcome. IBSS is a mode that you need to do routing with. It won't bridge for you. You need access point for that. Maybe that's what Wes is talking about: the ability to put the access point on a network and have it deal properly with bridging the traffic onto the lan. Finally, a lot of stuff is in flux right now :-) Warner To Unsubscribe: send mail to [email protected] with "unsubscribe freebsd-mobile" in the body of the message