I'm having the same problem on an up to date Jessie...
here're wlan0 related message from /var/log/kern.log
Mar 19 19:03:35 lambda-lambada kernel: [32092.991757] wlan0: authenticated
Mar 19 19:03:35 lambda-lambada kernel: [32092.994396] wlan0: associate
with 84:9c:a6:ed:0b:7d (try 1/3)
Mar 19 19:03:35 lambda-lambada kernel: [32092.998218] wlan0: RX
AssocResp from 84:9c:a6:ed:0b:7d (capab=0x411 status=0 aid=4)
Mar 19 19:03:35 lambda-lambada kernel: [32093.001784] wlan0: associated
Mar 19 19:03:35 lambda-lambada kernel: [32093.001809] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mar 19 19:20:54 lambda-lambada kernel: [33132.137344] wlan0:
deauthenticating from 84:9c:a6:ed:0b:7d by local choice (Reason:
3=DEAUTH_LEAVING)
Mar 19 19:20:54 lambda-lambada kernel: [33132.152518] cfg80211: Calling
CRDA to update world regulatory domain
Mar 19 19:20:54 lambda-lambada kernel: [33132.159351] cfg80211: World
regulatory domain updated:
Mar 19 19:20:54 lambda-lambada kernel: [33132.159356] cfg80211: DFS
Master region: unset
var/log/daemon.log:
...
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
supplicant interface state: authenticating -> associating
Mar 19 19:38:55 lambda-lambada wpa_supplicant[7915]: wlan0: Associated
with 84:9c:a6:ed:0b:7d
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
supplicant interface state: associating -> associated
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
supplicant interface state: associated -> 4-way handshake
Mar 19 19:38:55 lambda-lambada wpa_supplicant[7915]: wlan0: WPA: Key
negotiation completed with 84:9c:a6:ed:0b:7d [PTK=CCMP GTK=TKIP]
Mar 19 19:38:55 lambda-lambada wpa_supplicant[7915]: wlan0:
CTRL-EVENT-CONNECTED - Connection to 84:9c:a6:ed:0b:7d completed [id=0
id_str=]
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
supplicant interface state: 4-way handshake -> completed
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected
to wireless network 'EE-BrightBox-447f77'.
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 3 of 5 (IP Configure Start) started...
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
device state change: config -> ip-config (reason 'none') [50 70 0]
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> dhclient
started with pid 7937
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar 19 19:38:55 lambda-lambada NetworkManager[662]: <info> (wlan0):
DHCPv4 state changed nbi -> preinit
Mar 19 19:38:56 lambda-lambada dhclient: DHCPREQUEST on wlan0 to
255.255.255.255 port 67
Mar 19 19:38:56 lambda-lambada dhclient: DHCPACK from 192.168.1.1
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> (wlan0):
DHCPv4 state changed preinit -> reboot
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> address
192.168.1.17
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> plen 24
(255.255.255.0)
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> gateway
192.168.1.1
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> server
identifier 192.168.1.1
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> lease time
172800
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> hostname
'lambda-lambada'
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> nameserver
'192.168.1.1'
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> domain name
'default'
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 5 of 5 (IPv4 Commit) started...
Mar 19 19:38:56 lambda-lambada avahi-daemon[673]: Joining mDNS multicast
group on interface wlan0.IPv4 with address 192.168.1.17.
Mar 19 19:38:56 lambda-lambada avahi-daemon[673]: New relevant interface
wlan0.IPv4 for mDNS.
Mar 19 19:38:56 lambda-lambada avahi-daemon[673]: Registering new
address record for 192.168.1.17 on wlan0.IPv4.
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> (wlan0):
device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> (wlan0):
device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> (wlan0):
device state change: secondaries -> activated (reason 'none') [90 100 0]
Mar 19 19:38:56 lambda-lambada dhclient: bound to 192.168.1.17 --
renewal in 65188 seconds.
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> Policy set
'EE-BrightBox-447f77 1' (wlan0) as default for IPv4 routing and DNS.
Mar 19 19:38:56 lambda-lambada NetworkManager[662]: <info> Activation
(wlan0) successful, device activated.
Mar 19 19:38:56 lambda-lambada nm-dispatcher: Dispatching action 'up'
for wlan0
Mar 19 19:38:57 lambda-lambada avahi-daemon[673]: Joining mDNS multicast
group on interface wlan0.IPv6 with address fe80::6257:18ff:fe91:8d95.
Mar 19 19:38:57 lambda-lambada avahi-daemon[673]: New relevant interface
wlan0.IPv6 for mDNS.
Mar 19 19:38:57 lambda-lambada avahi-daemon[673]: Registering new
address record for fe80::6257:18ff:fe91:8d95 on wlan0.*.
Mar 19 19:39:02 lambda-lambada NetworkManager[662]: <info>
wpa_supplicant die count reset
Mar 19 19:43:00 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 4
Mar 19 19:43:04 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Mar 19 19:43:09 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Mar 19 19:43:14 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 11
Mar 19 19:43:25 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 16
Mar 19 19:43:41 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 18
Mar 19 19:43:59 lambda-lambada dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 2
Mar 19 19:44:01 lambda-lambada dhclient: No DHCPOFFERS received.
Mar 19 19:44:01 lambda-lambada dhclient: No working leases in persistent
database - sleeping.
Mar 19 19:44:01 lambda-lambada avahi-autoipd(eth0)[8230]: Found user
'avahi-autoipd' (UID 108) and group 'avahi-autoipd' (GID 117).
Mar 19 19:44:01 lambda-lambada avahi-autoipd(eth0)[8230]: Successfully
called chroot().
Mar 19 19:44:01 lambda-lambada avahi-autoipd(eth0)[8230]: Successfully
dropped root privileges.
Mar 19 19:44:01 lambda-lambada avahi-autoipd(eth0)[8230]: Starting with
address 169.254.5.197
Mar 19 19:44:06 lambda-lambada avahi-autoipd(eth0)[8230]: Callout BIND,
address 169.254.5.197 on interface eth0
Mar 19 19:44:06 lambda-lambada avahi-daemon[673]: Joining mDNS multicast
group on interface eth0.IPv4 with address 169.254.5.197.
Mar 19 19:44:06 lambda-lambada avahi-daemon[673]: New relevant interface
eth0.IPv4 for mDNS.
Mar 19 19:44:06 lambda-lambada avahi-daemon[673]: Registering new
address record for 169.254.5.197 on eth0.IPv4.
Mar 19 19:44:10 lambda-lambada avahi-autoipd(eth0)[8230]: Successfully
claimed IP address 169.254.5.197
ping returns after loosing the connection:
From lambda-lambada.local (169.254.5.197) icmp_seq=35 Destination Host
Unreachable
...
hope this gives some indications!
thanks & greets
Olsen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/550b28f8.70...@qmul.ac.uk
