wpa_supplicant will nicht mit WPA und AD-HOC funktionerien!!!

[root_tux_linux]

Hi

Hab da ein kleines Problem mit wpa_supplicant und zwar versuch ich ein ad-hoc Netzwerk aufzubauen was nicht klappt!

Ich seh zwar den Rechner aber ich komm ned ins Netz und seltsamerweise wird mir anstelle von WPA WEP angezeigt was völliger quatsch ist.

Hier mal paar Infos:


gentoo angelus # cat /etc/conf.d/net

## Cable eth0
config_eth0=("dhcp")
dhcpcd_eth0="-t 5"
dhcp_eth0="release nodns nonis nontp"

## Cable eth1
#config_eth1=("192.168.1.1 netmask 255.255.255.0 brd 192.168.1.255")

## Wlan wlan0
modules=( "!iwconfig" "wpa_supplicant" )
wpa_supplicant_wlan0="-Dwext"
config_wlan0=("192.168.1.1 netmask 255.255.255.0 brd 192.168.1.255")
gentoo angelus #



gentoo angelus # cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
ssid="Linux Rockz"
mode=1
proto=WPA
key_mgmt=WPA-NONE
pairwise=NONE
group=CCMP
psk="fickdiekuhdannmachtsiemuh"
}
gentoo angelus #


gentoo angelus # /etc/init.d/net.wlan0 restart
* Bringing down interface wlan0
* Removing addresses
* 192.168.1.1/24
* Stopping wpa_cli on wlan0 ... [ ok ]
* Stopping wpa_supplicant on wlan0 ... [ ok ]
* Bringing up interface wlan0
* Starting wpa_supplicant on wlan0 ... [ ok ]
* Starting wpa_cli on wlan0 ... [ ok ]
* Backgrounding ... ...
* WARNING: net.wlan0 has started, but is inactive
gentoo angelus #



gentoo angelus # ifconfig wlan0
wlan0 Protokoll:Ethernet Hardware Adresse 00:16:01:9a:04:c2
inet Adresse:192.168.1.1 Bcast:192.168.1.255 Maske:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:3060 (2.9 KiB)

gentoo angelus # iwconfig wlan0
wlan0 IEEE 802.11bg ESSID:"Linux Rockz"
Mode:Ad-Hoc Frequency:2.422 GHz Cell: 72:14:81:FA:CB:DC
Tx-Power=off
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:E59D-3308-7FC3-B123-0639-3EC0-F0AC-7829
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

gentoo angelus #


gentoo angelus # iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: CE:D3:FB:32:EC:79
ESSID:"Linux Rockz"
Mode:Ad-Hoc
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=54/100 Signal level:-32 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000006f86146
Extra: Last beacon: 769ms ago

gentoo angelus #


gentoo angelus # ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=2 Destination Host Unreachable
From 192.168.1.1 icmp_seq=3 Destination Host Unreachable
From 192.168.1.1 icmp_seq=4 Destination Host Unreachable
From 192.168.1.1 icmp_seq=6 Destination Host Unreachable


Der Laptop ist identisch konfiguriert bis auf die IP die 192.168.1.2 ist.


wicd und network manager zeigt mir komischerweise an es wäre WEP was nicht sein kann und hängt sich bei "Linux Rockz: Validating authentication..." auf.


Bitte um Hilfe

[Ede]

Hast eine Möglichkeit, die ad-hoc Verbindung erstmal ohne WPA auszuprobieren?

[zyrusthc]

Am besten erst einmal ganz ohne Verschlüsselung testen, ob man überhaupt drauf kommt!

Greeez Oli

[root_tux_linux]

network={
ssid="plaintext-test"
mode=1
key_mgmt=NONE
}


Funktioniert auch nicht -.-'


network={
ssid="example wep network"
key_mgmt=NONE
mode=1
wep_key0="abcde"
wep_key1=0102030405
wep_tx_keyidx=0
}


WEP funzt aber ich brauch WPA :(

[Ede]

Kennst du wpa_passphrase? Das macht dir aus der SSID und aus jeder beliebigen passphrase ein sog. "256-bit pre-shared key used for key derivation".
Benutzung, wenn plaintext-test die SSID ist:
wpa_passphrase plaintext-test fickdiekuhdannmachtsiemuh
Mehr dazu in diesem Thread: http://www.linuxforen.de/forums/showthread.php?t=254919

[root_tux_linux]

Kennst du wpa_passphrase? Das macht dir aus der SSID und aus jeder beliebigen passphrase ein sog. "256-bit pre-shared key used for key derivation".
Benutzung, wenn plaintext-test die SSID ist:
wpa_passphrase plaintext-test fickdiekuhdannmachtsiemuh
Mehr dazu in diesem Thread: http://www.linuxforen.de/forums/showthread.php?t=254919


Also ich habs jetzt mit wpa_passpharse versucht tortzdem gehts nicht.

Ich bekomm über WPA im Ad-hoc modus einfach keine Verbindung hin.



gentoo angelus # wpa_passphrase "Linux Rockz" fickdiekuhdannmachtsiemuh
network={
ssid="Linux Rockz"
#psk="fickdiekuhdannmachtsiemuh"
psk=e59d33087fc3b12306393ec0f0ac78296b8ff9b64eccd6 3cdef0be8cbbb53100
}
gentoo angelus #



ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
ssid="Linux Rockz"
mode=1
proto=WPA
key_mgmt=WPA-NONE
pairwise=NONE
group=CCMP
psk=e59d33087fc3b12306393ec0f0ac78296b8ff9b64eccd6 3cdef0be8cbbb53100
}



Hat keiner nen USB Adapter mit rt73usb und WPA im ad-hoc? oO

[zyrusthc]

Benutze mal das in der wpa_supplicant.conf:

proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP

Greeez Oli

[root_tux_linux]

Benutze mal das in der wpa_supplicant.conf:

proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP

Greeez Oli


Hab ich auch versucht funzt aber nicht mit Ad-hoc.

In der example steht auch:


# mode: IEEE 802.11 operation mode
# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
# 1 = IBSS (ad-hoc, peer-to-peer)
# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
# to be set to 2 for IBSS. WPA-None requires following network block options:
# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
# both), and psk must also be set.



# IBSS/ad-hoc network with WPA-None/TKIP.
network={
ssid="test adhoc"
mode=1
frequency=2412
proto=WPA
key_mgmt=WPA-NONE
pairwise=NONE
group=TKIP
psk="secret passphrase"
}

[Rain_maker]

Im Example steht aber auch:



# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
# APs (i.e., external program needs to control association). This mode must
# also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
# enable operation with hidden SSIDs and optimized roaming; in this mode,
# the network blocks in the configuration file are tried one by one until
# the driver reports successful association; each network block should have
# explicit security policy (i.e., only one option in the lists) for
# key_mgmt, pairwise, group, proto variables
ap_scan=1
Und dann stellt sich die Frage, wie aktuell dieser Eintrag

http://www.linuxwireless.org/en/users/Drivers

und ob WPA für AdHoc überhaupt schon implementiert ist.

[root_tux_linux]

Im Example steht aber auch:



# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
# APs (i.e., external program needs to control association). This mode must
# also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
# enable operation with hidden SSIDs and optimized roaming; in this mode,
# the network blocks in the configuration file are tried one by one until
# the driver reports successful association; each network block should have
# explicit security policy (i.e., only one option in the lists) for
# key_mgmt, pairwise, group, proto variables
ap_scan=1
Und dann stellt sich die Frage, wie aktuell dieser Eintrag

http://www.linuxwireless.org/en/users/Drivers

und ob WPA für AdHoc überhaupt schon implementiert ist.

Ich ging immer davon aus das wenn WEP im Ad-hoc funzt das dann auch WPA im ad-hoc funzen müsste... oder seh ich da was falsch?