I've tried iwpriv with the latest source code and it reports
wlan0 no private ioctls
Did the private ioctls go away? I've stepped through the code at device setup and I see
dev->wireless_handlers = &ieee80211_iw_handler_def (which has no private ioctls defined)
and the rt2x00 code never sets its own.
Am I doing something wrong? Is iwpriv only for the legacy drivers?
wlan0 no private ioctls[/quote1xmdosgy]
Yes, not having any private ioctls is a very cool feature that all wireless drivers should have.
Did the private ioctls go away?
Is iwpriv only for the legacy drivers?
There is no good reason for having private ioctls, it has no added benefit over the alternatives.
Ok, there is no more iwpriv. That is fine, but all the tutorials that I can find use iwpriv.
Can you point me to a how-to that will show me what I need in /etc/network/interfaces that does not use iwpriv?
here's something that might help
(available by default in most common distros)
Well you can use network manager, but that is based on wpa_supplicant.
But other then that, no you are stuck with wpa_supplicant until somebody writes something new....
I got the following problem
I want to use my wlan card as access point and client. I use Sebian SID and no matter how long i search google i do not find an answer how to configure /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf in a way that i can easily switch between both modes.
for now i start the access point mode with hostapd -d /etc/hostapd/hostapd.conf which works great. as long as i do not have any wpa-* lines in my interfaces file. So i thought the easiest way of configuring is running small bash scripts using ifconfig, iwconfig, iwpriv to set the card up to connect to remote an access points. With wpa_supplicant i feel like loosing a bit of control over what is done, which is probably caused by insufficient knowlege about wpa_supplicant. So i will continue reading about it an get my my head around the way it is working...
Could any of you give me some hints how to configure my system in a way that wpa_supplicant does not interfere with hostapd. Are virtual interfaces the way to go?
sincerely yours, herman
Well if you are using hostapd, shouldn't you use the WPA in that config?
As far as I know you don't need wpa_supplicant when using hostapd, so I guess you should check the hostapd manual, or ask about it on the hostapd mailinglist.