Hi!
1) Also nach neuem Kernel update (2.6.29-ARCH #1 SMP PREEMPT) is die Sache nun wirklich nicht mehr lustig! Hier mal die Ausgaben von dmesg und ein ping versuch! Bei dmesg wurde die Adresse durch 00:00:... ersetzt. Hoff ihr wisst Rat! Übrigens funktioniert das ganze an 2 PCs mit unterschiedlicher Wlan Hardware nicht!!!
2 ) Noch eine Frage dazu: Der Kernel 2.6.28 von der Installation macht keinerlei Zicken. Wo könnt ich denn den herbekommen oder wie mach ich ein downgrade?
3 ) Wie mach ich den einen reinstall vom kompletten System?
Danke für eure Hilfe, MfG
[eric@desktop_pc ~]$ dmesg | tail -30
wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: disassociating by local choice (reason=3)
wlan0: authenticate with AP 00:00:00:00:00:00
wlan0: authenticated
wlan0: associate with AP 00:00:00:00:00:00
wlan0: RX AssocResp from 00:00:00:00:00:00 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: authenticate with AP 00:00:00:00:00:00
wlan0: authenticated
wlan0: associate with AP 00:00:00:00:00:00
wlan0: RX AssocResp from 00:00:00:00:00:00 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: direct probe to AP 00:00:00:00:00:00 try 1
wlan0: direct probe to AP 00:00:00:00:00:00 try 1
wlan0: direct probe to AP 00:00:00:00:00:00 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:00:00:00:00:00
wlan0: authenticated
wlan0: associate with AP 00:00:00:00:00:00
wlan0: RX AssocResp from 00:00:00:00:00:00 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: authenticate with AP 00:00:00:00:00:00
wlan0: authenticated
wlan0: associate with AP 00:00:00:00:00:00
wlan0: RX AssocResp from 00:00:00:00:00:00 (capab=0x411 status=0 aid=1)
wlan0: associated
[eric@desktop_pc ~]$ ping
www.google.de
PING
www.l.google.com (74.125.43.103) 56(84) bytes of data.
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=1 ttl=245 time=50.3 ms
64 bytes from 74.125.43.103: icmp_seq=2 ttl=245 time=49.8 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=6 ttl=245 time=55.4 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=7 ttl=245 time=50.2 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=8 ttl=245 time=49.5 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=9 ttl=245 time=51.4 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=18 ttl=245 time=57.7 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=19 ttl=245 time=48.2 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=20 ttl=245 time=49.1 ms
64 bytes from bw-in-f103.google.com (74.125.43.103): icmp_seq=21 ttl=245 time=50.2 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable