WiFi Security
Does anyone know how the WiFi keys are set? I am using SBC and their little install/configure utility places all kinds of information in all four WEP keys, however I cannot figure out where to set these values or even more importantly, how to set any of the keys to some values that I would like. Thanks!
-Anthony |
Have you tried iwconfig? Here are some commands that I've had success with...
ifconfig eth0 up iwconfig eth0 essid wifoo iwconfig eth0 enc 1234567890 iwconfig eth0 mode managed dhclient eth0 ifconfig eth0 192.168.0.77 up route add default gw 192.168.0.1 ping 192.168.0.1 |
Thanks for the input, but that doesn't answer my question about how to go about setting the keys. I already have the card working in un-encrypted mode.
-Anthony |
I have had several people e-mail me directly looking to me to see if I have found an answer yet, and sadly I have to report that I have not.
Does anyone know how to go about setting these keys? Thanks! -Anthony |
Which driver are you using? Often `iwconfig key <your key>` works marvellously. See The Man for more details.
|
I of course checked the man pages before posting a query here. I have already figured out HOW to set the keys. What I am seeking as I am sure others are as well, WHAT do I set those keys to in order to memic the SBC settings. The "BASE" configuration is to input the serial number located at the bottom of the wireless router into the SBC software and then it generates 4 key codes. However these codes are never revealed to the user.
I know I can set my own key codes and get it to work, however if I forget them, its like pulling teeth to get it reset by going through the phone company to do so. And since they would be different than the windows configuration you can pretty much kiss support goodbye if you mention linux. The upshot here is that if we can get it configured easily enough, then we would be able to get SBC to start supporting Linux. |
Let me just clarify something, because despite your attempts to do so...well, I'm not following. Through normal configuration of this 'SBC' Wireless Router, you input some code written on the bottom of it (probably determined by the mfr.) and it spits out the WEP keys that you need and configures it correctly. (I hope I'm right so far) So...you are wanting to be able to figure _how_ the keys are being generated and/or figure out _what_ the keys are, so that you can input them into your linux rig and get some modicum of security out of this setup. (continuing to hope)
Now, assuming that I at least know _what_ you're trying to accomplish (and perhaps others may benefit from some clarity), I can try to decide on a solution. I would think in completely infeasible to try to determine how the mfr. derives the keys you need. This would take more effort than this really is worth. However, ascertaining the nature of the keys themselves should be rather straightforward. As for myself, I think I would use AirSnort, Kismet or some other tool, and generate enough traffic for them to determine the key for me. Thus avoiding support personnel involvement and too many hours of head-banging. If I have nailed your problem (at least the definition), do say so. Otherwise...well...:confused: |
Yes, you pretty much hit the nail on the head. I understand that the security is mediocre at best, not knowing how - for the moment, with how SBC generates their WEP codes based upon the manufactured serial number. However it is to serve two purposes. The first is to understand a little bit more about entering the WEP codes (HEX and all). The second is to understand more about how SBC can generate unlocking codes for your particular unit in case you forget your password.
Thanks! |
If this piece of equipment is from SBC, the Ma Bell Subsidiary, I would think that it would have some commercial derivation of it on the market. Is there anything else that you can tell me about the hardware?
Also, I assume that configuration is possible through a web interface (e.g. http://192.168.0.1 or similar). Have you looked at what is available there? Let me let you in on my train of thought... If this router/gateway/AP/whatever has some non-proprietary counterpart (same hardware, but not branded as SBC), there may be more information about the sucker on the Wibble. If the rig has a web-based interface, it _may_ allow you to choose a WEP key, or possibly *crosses fingers* even allow you to select a different encryption mechanism (WPA, RSN, 802.11X, etc.). If _so_, then we've solved the problem, because then you can just play with iwconfig until the two units are talking. Else, I'm serious about use a sniffer to try to reverse-engineer the problem... |
Well actually SBC doesn't even try to hide their equipment in this case. Its a 2Wire! And yes you can access it through a browser on the 192.168. network. Yes, you can set the keys.
Ok...ok..so I guess we are going to have to play with iwconfig and get the keys to match. Even so, the WEP keys appear to be in different formats on the router config utility as they appear to be needed in iwconfig. |
I have a netgear access point and you just connect to the the right 192.168.0.* address and it gives you a wep security option, which you access with a web browser.
You enter a 'pass phrase' or something like that and it creates a 26 character long code like 2JIFGTO87FTYDEH54JDUUY3BCA. or it creates 4 You can just use 1. Then just set your wireless device with iwconfig as described in the second posting: iwconfig wlan0 enc 2JIFGTO87FTYDEH54JDUUY3BCA Make sure both devices are using are using the same secure mode, ie restricted/shared key or open/ open key. maybe with: iwconfig wlan0 enc restricted 2JIFGTO87FTYDEH54JDUUY3BCA |
I've been running wifi for a while now and have NEVER had to use the iwconfig program to make settings. Make and entry in /etc/pcmcia/wireless.opts and it will work automatically when the card is plugged in. You people are working way too hard at this.
|
That all sounds good, but what options do you put in the file /etc/pcmcia/wireless.opts
|
Your file should have comments that explain how it works, I stripped them out of mine once it was working properly.
Code:
case "$ADDRESS" in |
Cool...Thanks! I'll give it a try and let everyone know my results.
-Anthony |
All times are GMT -5. The time now is 02:28 AM. |