HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.

[blommie]

. I have noticed something else when I start up my notebook I get for Kernels I can pick from I can't remember that before and it seemed the kernels were upgrade must have been when I did a auto update. The 4 I can choose from is:

Linux Mint Kernel 2.6.24-21
Linux Mint Kernel 2.6.24-21 Recovery Mode
Linux Mint Kernel 2.6.24-16
Linux Mint Kernel 2.6.24-16 Recovery Mode
Linux Mint Kernel memtest86+

There wont be a conflict will there?

[wieman01]

Hi wieman01

How secure will a combination of WEP and MAC Filtering be?

Completely useless. You can actually clone/fake Mac addresses:

ifconfig eth1 down hw ether 00:00:00:00:00:01
ifconfig eth1 up

As simple as that.

[wieman01]

There won't be any conflict, don't worry. But what system are you on? Ubuntu 8.10?

[blommie]

No sorry I'm on Linux Mint Elyssa.

[kevdog]

Weiman

Dont know if you are actively maintaining this thread, however with Ibex (yes I read the disclaimer and it didn't say specifically tested with ibex), however the driver named to be used with wpa_supplicant is now almost always wext. Due to the changes with the wireless tools package, wpa_supplicant is now no longer compiled against the madwifi or ndiswrapper or intel sources. They now all default to wext. I think atmel may be an exception, however if using Ibex, wpa_supplicant -h will show specifically the sources wpa_aupplicant was compiled against.

[blommie]

Guys Wieman01 and kevdog

I did another command on my linux box namely:

lshw -class network

Please have a look and see if anything sticks out please I'm getting desperate all I want is for the wireless WPA connection to work as before:

lshw -class network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1d:72:0e:1d:4e
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A ip=10.1.1.4 latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:17:c4:09:b1:47
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5211 driverversion=1.52+,05/02/2007,5.3.0.45 latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

[wieman01]

Hi Kevdog,

Nice to hear from you.

I am still maintaining this thread, or say, I mean to. Good point. From your perspective, is this thread still relevant for Ibex users?

I tried out Kubuntu 8.10 last night and was impressed to see that Network Manager (yes, that very tool) hooked up to my network immediately and even let me configure a static IP address. Amazing.

No need for "ndiswrapper" (Ralink) either... Quite impressed.

So what do you think? Your tutorial seem more appropriate for all related questions than this one.

[blommie]

Hi I'm thinking about starting all over again by re-installing Elyssa or even upgrading to Felicia or another distro.

Can you please give me suggestions on that road please. All I want is a reliable wireless connection in the OS also I have a problem with my CD /DVD COMBO player so I will have to do the re-install/upgrade via USB .... What are you thoughts on that please as a layman I am open for suggestions.

Thanks

[kevdog]

weiman

Not sure if you are hanging out in the networking section a lot these days -- I get kind of burnt out over there also -- however this thread is totally relevant. I found network manager to work out of the box with both my broadcom and atheros card, however a lot of people are still resorting to wicd to make things work. Still others are modifying the interfaces file as you have suggested.

Wireless support in my opinion is really screwed up. Just when I think I have a handle on the chipsets, a new kernel is released along with new chipsets, and the old solutions don't work any longer. As an example, the old way I used to use with my Broadcom card using ndiswrapper, no longer works with any wpa2 based encryption. The b43 and madwifi modules however do connect without any problems.

Please keep support of this thread as long as you can.

See you around.

[kevdog]

Guys Wieman01 and kevdog

I did another command on my linux box namely:

lshw -class network

Please have a look and see if anything sticks out please I'm getting desperate all I want is for the wireless WPA connection to work as before:

lshw -class network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1d:72:0e:1d:4e
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A ip=10.1.1.4 latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:17:c4:09:b1:47
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5211 driverversion=1.52+,05/02/2007,5.3.0.45 latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

Just a thought -- I know the atheros 242x chipset is a royal pai in the butt, but why do you want to use ndiswrapper??? There are plenty of threads posted within the last 2 days on the networking subforum that show how to use the native madwifi drivers (which I think you have to compile -- SCARY -- no not really at all). I really would take a look at these threads and save yourself a lot of later headache. If you get started in one of the threads I can help you since I've compiled madwifi drivers like 1000 times (but not for the 242x chipset).