Debian Configuration :: Turning Wireless Interface Into Master Mode?
May 25, 2011
i am wanting to turn my Debian box into a wireless AP, but for some unknown reason the wireless card won't switch into master mode when i run the command #iwconfig wlan1 mode master i get this Error for wireless request "Set Mode" (8B06): SET failed on device wlan1 ; Invalid argument. what does this mean and what do i need to configure/install to get it to work my wirless card is supported i checked it's a zydas chipset using the zd1211rw driver SMC EZ Connect SMCWUSB-G [URL]
I try to set-up an Access point using ubuntu 11.04. I am using the minimal configuration file from [URL] together with a TP-Link TL-WN422G (Atheros chipset). I've installed the linux-backports-net-natty-generic drivers. But when trying to start hostapd I always get this output:
Code: # hostapd -dd -K test.conf Configuration file: test.conf Failed to set interface wlan0 to master mode. nl80211 driver initialization failed. wlan0: Unable to setup interface. ELOOP: remaining socket: sock=5 eloop_data=0x9b9440 user_data=(nil) handler=0x43d980 I have also disabled the network-manager for this device by adding this to /etc/network/interfaces:
I've searched for too many days and nights so many information went through my head. I want to buy a usb wireless which support master mode. (not monitor mode) Now I'm interested in Alfa AWUS036NEH. I like it because it is small an have a long antenna strong 1000mW. signal. (AWUS036H is a little bit big for me) However from what i have read AWUS036NEH is not supported in master mode (softAP)(or may be supported but with hostapd, but again some forum said it doesn't support and some say it does... Totally confused.) -> Actually AWUS036NEH is not expensive but I don't want to invest in something i'm not sure about so I won't buy it until I really know if it works. So I switch to find out what is for sure
1. supported in master mode in Ubuntu
2. Have a long antenna (like 5" or something. I have no idea about hardware but I think longer antenna should send signal more further)
3. small (about normal USB size don't count antenna)
Sadly I only find Alfa AWUS036NEH the only option for me , the others has no brand. However TL-WN722N is what most likely to fit. Only it has a shorter antenna. Can i replace the antenna with a longer one (with some others brand) by myself? (TL-WN722N can use master mode in kernel 3.0 ? already ? some say it should but i've not seen one that stated clearly) Ahh I think the above is totally messed up. I will make long story short.
1. Is AWUS036H or AWUS036NEH support master mode in ubuntu ? (if yes with hostapd or something?)
2. Is TL-WN722N or TL-WN722NC can work in master mode in Ubuntu ? (if yes with hostapd or something?)
3.Can I replace the original antenna with a longer one ?(with other brand or same brand) Will the signal be stronger?
I'm a student who is working on a wireless research project. I have a madwifi driver for Atheros chipset on Debian Linux. With having the wireless interface get into monitor mode, I want to forward the captured packets from the wireless interface to the other Ethernet interface so that a different computer which is connected to this machine via Ethernet receives those packets. I checked that alll packets are received in the wireless interface using TCPDUMP. I tried to forward those packets with IPTABLES like 'iptables -p FORWARD -i ath0 -o eth2 -j ACCEPT' However, I couldn't see any packets forwarded to eth2 using TCPDUMP.
I am trying to manually configure my wireless interface similar to how I manually configure my wired interfaces on Ubuntu 10.10 (Maverick Meerkat). I have two wired interfaces that use static IP addresses. I set up these interfaces using /etc/network/interface file. I disabled network manager (it was never working correctly to start with). Now, I want to connect my wireless interface (wlan0) to an unsecured wireless private network. I know/can find out all the information about the wireless network (ssid, etc). Also, I need to do this without disconnecting either of my wired interfaces.
I have looked all over the internet/forums for information about how to set up this interface, but nothing I found meets my need. Is there any way I can use iwconfig or the interface file to connect to this wireless connection? Or is there any other tool that will allow me to manually do this?
I installed Debian 5.04. The Debian installer picked the Ethernet card but not the wireless (Atheros 9285). I followed these instructions to install it (found at [URL]...
But there was no wireless interface shown in the network interfaces entry of hardinfo, even though I wrote modprobe ath_pci in terminal window. My questions are: 1. I followed the instructions regarding updating the madwifi sources, installing them etc. Does this guarantee that apt downloaded and installed the right madwifi driver? 2. Will I be better off if I try to install the driver downloaded from the Atheros website? 3. How can I activate the wireless interface (since the driver is running should not the wireless interface somehow show up automatically)? 4. When I am running Ubuntu 9.10 it picks up the wireless. Can I somehow copy all the files for the wireless from Ubuntu and paste them in the Debian filesystem?
I have b43 wireless. In network Configuration on system->administration the interface it appears as inactive it appers in hardware also as b43 associated to wlan0 but i cannot have access to any wireless network. What i have to do to put this b43 to work.
I started having this issue two days after installing openSUSE. When I try to boot it on battery (that is, without a energy plug) the laptop just turn off right at the beginning. I have other OS's installed and they are working properly and booting when in battery mode. I haven't got a clue of what I need to check to fix this, can anyone help me out? My laptop is a vostro V13.
Anybody have any idea that how to set the ath9k in master mode in fedora 11. I am unable to set the same. I am using the D-Link DWA556 card using the kernel built in ath9k.Find below the output I got while setting up it in master mode sudo iwconfig wlan0 mode master.Error for wireless request "Set Mode" (8B06):SET failed on device wlan0 ; Invalid argument.Does that mean that master mode is not supported?Also Want the information if there is any separate community or development group for ath9k development and download the source of same except linuxwireless.com.
I'm renting a server which comes with 5 IP addresses, but only one network device. From what I can understand I'm able to create aliases by adding entries to /etc/networks/interfaces, I haven't tried I'm in the planning stages. Hypothetically, 192.168.22.30 is my primary IP and I want to set eth0:1 to have 192.168.22.31, and then after that I want to create a virtual machine (using kvm/qemu) that is able to communicate bidirectionally to the internet over eth0:1, and leave eth0 strictly for administrating (not for VM traffic).
The qemu guides I'm finding seem to assume that I want to use TAP or VDE, what I want to use is a sub-ip/alias. One guide I saw had me eliminate everything from eth0 and put it under br0. That would leave me unable to ssh into my server (and unable to administrate). Is there a way I can do something along the lines of: qemu [options] -net [option] -netdev=eth0:1 ?
Is is possible, via iptables or something similar, to bind a service running on a specific port to a specific interface? My case: I use a VPN service for privacy. I would like to have all traffic except ftp and ssh to run over tun0. Ports 21 and 22 will need to be accessible to the outside world (eth0) while the VPN is running.
I am trying to get my wireless card working in master mode. I am running Jaunty server 2.6.28-11 x86_64. I have compiled hostapd with nl80211 enabled. The interface is using ath9k. I have tried to compile compat-wireless with this patch. However IEEE80211_IF_TYPE_AP was undefined along with IEEE80211_IF_TYPE_VLAN. In addition the latest version of compat-wireless needs to be patched for kernels < 2.6.31 with this. However when using this patch IRQ_WAKE_THREAD is still undefined.
I have got to this message:
$ sudo hostapd /home/jophish/.hostapd.conf Configuration file: /home/jophish/.hostapd.conf Failed to set interface wlan0 to master mode.
Suppose I have both a hardwired and a wireless network connection active on the same system at the same time. Can I tell my browser which one to use? Can I tell other programs which one to use? Or do they choose for themselves> Or does some automatic system protocol select which one to use for them?
after trying several pci and usb network cards none were able to have their ssid broadcasted. The question that i have is: Can a suse box be converted to act as an acces point without the use of atheros based hardware, without switching over to ubuntu and or debian, without the use of openwrt?
I'm running Ubuntu 10.10 and try to get my wifi to work in master mode. The dongle is a Asus 167g v3 and I'm using the rtl8192SU driver. I can connect to a network or put the dongle in Ad-hoc mode without a problem. It's when I try to put in master mode some problem occurs. When I do:
Code: sudo iwconfig wlan1 essid test mode master This is the output I'm getting: Code: wlan1 unassociated Nickname:"rtl_wifi" Mode:Master Access Point: Not-Associated Sensitivity:0/0
The dongle is in master mode but it fails to assign a SSID. I also tried to set it up in /etc/network/interfaces but the result is always the same... No SSID
I'm looking into assembling a debian based router/firewall system. Fortunately there is a great deal of documentation available on this subject, so I am confident the project is viable. I'm a bit stumped regarding a wireless card though, especially since I'd like to use a desktop form factor rather than one of the laptop style slots. At present, I'm going with a mini-itx board that has a couple of wired nics and a pci-e x4 expansion slot (supermicro's x7spa-h). So, I can connect an access point to one of the nics and that's job done. In the interests of having one fewer box to find space for, I'd like to use a pci-e card as a (wireless n) access point. To do this I need one capable of working as a "master", rather than only as a "client".
Google suggested D-link's dwa-556. Linuxwireless.org suggests the D-link DWA-556 uses ath9k. It also thinks the ath9k driver is capable of operating as an access point. Can I take this to mean that the DWA-556 will be usable as an access point? If so, all is well, and I may go forth and find any card that uses a driver marked AP capable. If not, say because it's a hardware limitation, how do I go about finding a card that'll do what I want it to?
I am having some troubles using iptable rules on two Servers that act as Gateways pointed to one backend server with only one interface.
To be more exact, i have 3 Servers, 2 of those have a public and a private interface, with different public ips but common private interface ( they connect to the same switch ), the last one only has 1 private interface and is connected to that same switch.
Those 2 servers also act as a gateway and a firewall for the private network.
My problem is that i cannot seem able to route traffic from both of those to the third one and back to the same public ip that the request came from ( effectivly using two gateways on the machine with only one interface ).
As a testing scenario i am using ferm for applying iptable rules that forward ssh traffic ( for example ) to the backend server, and it works well when i do it with one gateway.
When i apply something like this in /etc/network/interfaces on the backend server though:
Even though forcing selection of an interface from the backend server ( like curl --interface ) seems to work well, meaning that the request to the curl appear to happen from the correct public ip, i can still only use one of the public ips to access the server with the ferm rules. Ideally i should be able to ssh to the backend server from both public ips using their ferm rules for forwarding traffic to the backend server.
I feel like i am missing some details on routing that should happen on the firewalls as the backend server seems to be able to use both gateways to access the internet and receive replies from it.