Netzwerk inaktiv nach Start

Brenner · 5. November 2012

Hallo,

habe jetzt yavdr0.5 installiert. Installation lief problemlos. Habe hier meine WLAN Verbindung eingerichtet. Diese wurde auch für updates genutzt. Wenn ich jetzt einschalte steht das Netzwerk nicht zur Verfügung. Erst nach einem "/etc/init.d/networking restart" ist das Netzwerk eingerichtet. Was kann die Ursache hierfür sein?

gda · 5. November 2012

Zitat von Brenner

Was kann die Ursache hierfür sein?

Ich würde ja im log danach suchen.

Gerald

Brenner · 5. November 2012

Das habe ich versucht fand allerdings nix womit ich etwas anfangen könnte.

Code

Nov  4 18:20:52 yavdr kernel: [ 2163.689322] init: Disconnected from system bus
Nov  4 18:20:52 yavdr dhclient: DHCPRELEASE on wlan0 to 192.168.21.100 port 67
Nov  4 18:20:52 yavdr wpa_supplicant[2305]: CTRL-EVENT-DISCONNECTED bssid=bc:05:43:a8:bc:ac reason=3
Nov  4 18:20:52 yavdr kernel: [ 2164.273581] wlan0: deauthenticating from bc:05:43:a8:bc:ac by local choice (reason=3)
Nov  4 18:20:52 yavdr kernel: [ 2164.354723] cfg80211: All devices are disconnected, going to restore regulatory settings
Nov  4 18:20:52 yavdr kernel: [ 2164.354735] cfg80211: Restoring regulatory settings
Nov  4 18:20:52 yavdr kernel: [ 2164.354745] cfg80211: Calling CRDA to update world regulatory domain
Nov  4 18:20:52 yavdr wpa_supplicant[2305]: Failed to initiate AP scan.
Nov  4 18:20:52 yavdr wpa_supplicant[2305]: CTRL-EVENT-TERMINATING - signal 15 received
Nov  4 18:20:54 yavdr kernel: Kernel logging (proc) stopped.
Nov  4 18:20:54 yavdr rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="1135" x-info="http://www.rsyslog.com"] exiting on signal 15.
Nov  4 18:21:30 yavdr kernel: imklog 5.8.6, log source = /proc/kmsg started.
Nov  4 18:21:30 yavdr rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="1087" x-info="http://www.rsyslog.com"] start
Nov  4 18:21:30 yavdr rsyslogd: rsyslogd's groupid changed to 103
Nov  4 18:21:30 yavdr rsyslogd: rsyslogd's userid changed to 101...
Nov  4 18:21:30 yavdr kernel: [   15.820451] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov  4 18:21:30 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4...
Nov  4 18:21:54 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Nov  4 18:22:04 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Nov  4 18:22:15 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Nov  4 18:22:25 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Nov  4 18:22:38 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Nov  4 18:22:56 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Nov  4 18:23:04 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Nov  4 18:23:13 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Nov  4 18:23:21 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
....
Nov  4 18:26:04 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
Nov  4 18:26:24 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Nov  4 18:26:28 yavdr dhclient: No DHCPOFFERS received.

Alles anzeigen

Das kommt dann, wenn ich manuel das Netzwerk neu starte

Code

Nov  4 18:53:12 yavdr wpa_supplicant[816]: CTRL-EVENT-TERMINATING - signal 15 received
Nov  4 18:53:12 yavdr wpa_supplicant[2214]: Failed to initiate AP scan.
Nov  4 18:53:12 yavdr kernel: [ 1922.513165] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov  4 18:53:12 yavdr dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Nov  4 18:53:14 yavdr wpa_supplicant[2214]: Trying to authenticate with bc:05:43:a8:bc:ac (SSID=xxxxx' freq=2412 MHz)
Nov  4 18:53:14 yavdr kernel: [ 1924.462143] wlan0: authenticate with bc:05:43:a8:bc:ac (try 1)
Nov  4 18:53:14 yavdr wpa_supplicant[2214]: Trying to associate with bc:05:43:a8:bc:ac (SSID=xxxxx' freq=2412 MHz)
Nov  4 18:53:14 yavdr kernel: [ 1924.464419] wlan0: authenticated
Nov  4 18:53:14 yavdr kernel: [ 1924.483886] wlan0: associate with bc:05:43:a8:bc:ac (try 1)
Nov  4 18:53:14 yavdr kernel: [ 1924.490506] wlan0: RX AssocResp from bc:05:43:a8:bc:ac (capab=0x431 status=0 aid=1)
Nov  4 18:53:14 yavdr kernel: [ 1924.490517] wlan0: associated
Nov  4 18:53:14 yavdr kernel: [ 1924.490527] wlan0: No basic rates in AssocResp. Using min supported rate instead.
Nov  4 18:53:14 yavdr wpa_supplicant[2214]: Associated with bc:05:43:a8:bc:ac
Nov  4 18:53:14 yavdr kernel: [ 1924.498429] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov  4 18:53:14 yavdr kernel: [ 1924.500352] cfg80211: Calling CRDA for country: DE
Nov  4 18:53:14 yavdr wpa_supplicant[2214]: WPA: Key negotiation completed with bc:05:43:a8:bc:ac [PTK=CCMP GTK=TKIP]
Nov  4 18:53:14 yavdr wpa_supplicant[2214]: CTRL-EVENT-CONNECTED - Connection to bc:05:43:a8:bc:ac completed (auth) [id=0 id_str=]
Nov  4 18:53:14 yavdr kernel: [ 1924.512991] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
Nov  4 18:53:14 yavdr kernel: [ 1924.513004] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov  4 18:53:14 yavdr kernel: [ 1924.513011] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
Nov  4 18:53:14 yavdr kernel: [ 1924.513020] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov  4 18:53:14 yavdr kernel: [ 1924.513026] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
Nov  4 18:53:14 yavdr kernel: [ 1924.513035] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov  4 18:53:14 yavdr kernel: [ 1924.513041] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
Nov  4 18:53:14 yavdr kernel: [ 1924.513050] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov  4 18:53:14 yavdr kernel: [ 1924.513056] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
Nov  4 18:53:14 yavdr kernel: [ 1924.513064] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)

Alles anzeigen

nc17 · 5. November 2012

Was steht in /var/log/upstart/network-interface-wlan0.log

Brenner · 5. November 2012

Was es so alles für logs gibt. Hoffe dir sagt das etwas?!

nc17 · 5. November 2012

Ändere bitte die /etc/network/interfaces in

Code

# The loopback network interfaceauto loiface lo inet loopback# Wired network interfaceauto eth0iface eth0 inet dhcp# Wireless network interfaceauto wlan0iface wlan0 inet dhcpwpa-conf /etc/wpa_supplicant.conf

und leg ne /etc/wpa_supplicant.conf an

Code

network={ssid="SSID-HIER"proto=RSNkey_mgmt=WPA-PSKpairwise=CCMP TKIPgroup=CCMP TKIPpsk="PASSWORT-HIER-REIN"}

edit: interfaces komplettiert, damit keine Missverständnisse passieren

Brenner · 5. November 2012

Hat erstmal funktioniert. Hoffe es ist reproduzierbar.

Danke!

nc17 · 5. November 2012

Bei mir ist es das.

Brenner · 6. November 2012

Hat jetzt mehrmals funktioniert. Das war es auch bei mir. Danke!

Netzwerk inaktiv nach Start

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema