Posted on 01-13-2009 12:12 AM
I am looking at just disabling the ability to create an ad hoc network. A simple look at the given command line tools says I can't do this. So, now I am venturing into the real of editing a plist to disable that function.
Any pointers or suggestions?
Thanks,
Posted on 01-13-2009 12:19 AM
For Airport? From Terminal, sudo /usr/libexec/airportd en1 - ibss_admin 1
or for remote deployment:
expect -c 'spawn /usr/libexec/airportd en1 -ibss_admin 1; expect eof'
johnd
--
John DeTroye Email: johnd at apple.com
Sr. Consulting Engineer Systems Management Specialist
Apple - Education iChat: johnd at mac.com
Systems Management Guide - http://www.apple.com/education/go/sysmgmt/
Tips and Tricks Docs - http://web.me.com/johnd/
Posted on 01-13-2009 12:55 AM
Thanks! Could you explain what the "-ibss_admin" switch means? How would
this be undone if you needed to?
If your airport interface is not "en1", would you need to discover the
correct value and substitute it in the command? Isn't airport en2 on Mac
Pros and en0 on MacBook Airs?
Such as:
airport_interface=`system_profiler SPNetworkDataType| grep -A 1 "Hardware:
AirPort"` airport_interface=${airport_interface: -3}
expect -c 'spawn /usr/libexec/airportd $airport_interface -ibss_admin 1;
expect eof'
Thanks again for the great info!
----------
Miles A. Leacy IV
? Certified System Administrator 10.4
? Certified Technical Coordinator 10.5
? Certified Trainer
Certified Casper Administrator
----------
voice: 1-347-277-7321
miles.leacy at themacadmin.com
www.themacadmin.com
Posted on 01-13-2009 12:59 AM
My guess...in the world of bits...
ibss_admin 0
;)
Craig E
Posted on 01-13-2009 01:05 PM
Awesome!
OK, so what file does this actually write to? I am thinking a one liner casper policy should suffice for this
Thanks,
Posted on 01-13-2009 01:28 PM
Craig, if I were a betting man, I'd bet you are most likely right
looking at the airportd daemon I want to know what other commands I can
use with it. The man page is seriously lacking. In fact it doesn't
display any information. I will search the Apple White pages and see if
I can come up with something else, but the documentation is really light
on this.
Thanks,
Posted on 01-14-2009 06:41 AM
After testing out that command it seems all it does is just require
admin rights to create ad hoc networks. So if you don't have admin
rights you can't create them.
Nifty
Posted on 02-12-2013 11:46 AM
after some messing around, I believe this is what will work on Mountain Lion:
/usr/libexec/airportd en1 prefs JoinMode=Preferred RememberRecentNetworks=NO RequireAdminIBSS=YES