Ubuntu
gnome-nettool package

Wireless worked, but stopped working. How to investigate this and then solve it? Lucid.

Asked by Willem Hobers

I have been using Ubuntu 10.04 (32 bits) for some time now on my HP Pavilion DV9700 (4 bits). Quite happy. Thanks for the good work.
Everything worked, even wireless.
Then, a few days back, wireless stopped working. I turned the laptop off. Turned it on a few hours later. And then the wireless didn't work any more.
I *think* there may have been an update during the last session that still had a working wireless. Not quite sure though.

Question is:
- how do I go about finding out what the problem is and where?
- is there a specific log that I can use to troubleshoot this issue?

Any help appreciated.

Mark you: I am a Linux/Ubuntu newby (-ish).

The wireless is set up to connect to a wireless router which I know is up.
It is set up to request an ip-address from the router's DHCP-server.
It is set up to use WPA2 preshared key.
And -as I said- it has worked up until a few days ago.

I did a few things so far:
- clicked on Network Manager. It only shows the wired connection.
- turned the hardware switch for wireless/bluetooth off and on (reboot in between).
- reinstalled (through System -> Admin -> Closed Drivers (not sure what it is in English) the BMC STA driver.) (Including a reboot).
- ran lshw -C network [1]
- ran ifconfig [2]
- had a look in etc/network/interfaces [3]

[1]
willem@PC10-135:~$ sudo lshw -C network
[sudo] password for willem:
  *-network
       description: Ethernet interface
       product: MCP65 Ethernet
       vendor: nVidia Corporation
       physical id: 6
       bus info: pci@0000:00:06.0
       logical name: eth0
       version: a3
       serial: 00:1e:68:26:ed:c4
       size: 100MB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.64 duplex=full ip=192.168.123.10 latency=0 link=yes maxlatency=20 mingnt=1 multicast=yes port=MII speed=100MB/s
       resources: irq:20 memory:f2487000-f2487fff ioport:30e0(size=8)
  *-network UNCLAIMED
       description: Network controller
       product: BCM4312 802.11a/b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
       resources: memory:f2000000-f2003fff

[2]
willem@PC10-135:/etc$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:1e:68:26:ed:c4
          inet addr:192.168.123.10 Bcast:192.168.123.255 Mask:255.255.255.0
          inet6 addr: fe80::21e:68ff:fe26:edc4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:42902 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46999 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:27264484 (27.2 MB) TX bytes:16662014 (16.6 MB)
          Interrupt:20 Base address:0x8000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1495 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1495 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:227277 (227.2 KB) TX bytes:227277 (227.2 KB)

[3]
auto lo
iface lo inet loopback

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Mark Rijckenberg
Solved:
Last query:
Last reply:
Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#1

Hi,

Please first connect your network card to the wireless router using an ethernet cable (also known as a LAN cable).

In order to gather essential troubleshooting information about your wireless card, please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->Terminal"

Step 2: Please copy-paste the following command from the https://answers.launchpad.net/ubuntu website in Firefox into the Linux Terminal. Do NOT copy-paste from the Email message into the Terminal, as that will only copy PART of the command. The command STARTS with the word sudo and ENDS with the word restart. So please copy-paste the ENTIRE command below from Firefox into a Terminal, press <enter>, then enter password when sudo asks for password, then press enter again.

Tip: If you have a wheel mouse or 3 button mouse you do not need to type commands into the Terminal. Highlight the command written on the page. Move your cursor anywhere in the Terminal and press the wheel or middle button. Automatic Copy and paste! No spelling mistakes! No Typos! No other errors!

sudo lshw -C network; rfkill list; sudo iwlist scanning; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -short; uname -a; dmesg | grep ound; dmesg | grep irmware ; dmesg | grep ipw; dmesg | grep eth; dmesg | grep ath; dmesg | grep b43; dmesg | grep wl; dmesg | grep witch; iwconfig; grep b43 /etc/modprobe.d/*; grep wl /etc/modprobe.d/*; sudo hwinfo --netcard ; sudo /etc/init.d/networking restart

Step 3: Please post results (copy/paste terminal output) on this thread. The troubleshooters here need to see the full Terminal output from running the above command.

Regards,

Mark

Revision history for this message
Willem Hobers (whobers) said : 		#2

Thanks Mark,

I did as you asked. Here's the output.
There is a difference however: as of today -suddenly- the wireless is working again! I changed nothing to my system. Nor has there been an update as far as I know. I *had* run the commands you suggested, when I noticed that the wireless was working again.

Can you see in the output below what may have caused the initial problem, and what may have happened for that issue to be resolved out of the blue? Is there a command below which may have caused the issue to be resolved?

Thanks!

Willem

willem@PC10-135:~$ sudo lshw -C network; rfkill list; sudo iwlist scanning; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -short; uname -a; dmesg | grep ound; dmesg | grep irmware ; dmesg | grep ipw; dmesg | grep eth; dmesg | grep ath; dmesg | grep b43; dmesg | grep wl; dmesg | grep witch; iwconfig; grep b43 /etc/modprobe.d/*; grep wl /etc/modprobe.d/*; sudo hwinfo --netcard ; sudo /etc/init.d/networking restart
[sudo] password for willem:
  *-network
       description: Ethernet interface
       product: MCP65 Ethernet
       vendor: nVidia Corporation
       physical id: 6
       bus info: pci@0000:00:06.0
       logical name: eth0
       version: a3
       serial: 00:1e:68:26:ed:c4
       size: 100MB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.64 duplex=full ip=192.168.123.10 latency=0 link=yes maxlatency=20 mingnt=1 multicast=yes port=MII speed=100MB/s
       resources: irq:20 memory:f2487000-f2487fff ioport:30e0(size=8)
  *-network
       description: Wireless interface
       product: BCM4312 802.11a/b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth1
       version: 02
       serial: 00:1a:73:fa:7f:ea
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 ip=192.168.123.135 latency=0 multicast=yes wireless=IEEE 802.11abg
       resources: irq:16 memory:f2000000-f2003fff
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Failed to read scan data : Invalid argument

pan0 Interface doesn't support scanning.

auto lo
iface lo inet loopback

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04 LTS"
00:00.0 RAM memory [0500]: nVidia Corporation MCP65 Memory Controller [10de:0444] (rev a3)
00:01.0 ISA bridge [0601]: nVidia Corporation MCP65 LPC Bridge [10de:0442] (rev a3)
00:01.1 SMBus [0c05]: nVidia Corporation MCP65 SMBus [10de:0446] (rev a1)
00:01.3 Co-processor [0b40]: nVidia Corporation MCP65 SMU [10de:0447] (rev a1)
00:02.0 USB Controller [0c03]: nVidia Corporation MCP65 USB Controller [10de:0454] (rev a3)
00:02.1 USB Controller [0c03]: nVidia Corporation MCP65 USB Controller [10de:0455] (rev a3)
00:06.0 Ethernet controller [0200]: nVidia Corporation MCP65 Ethernet [10de:0450] (rev a3)
00:07.0 Audio device [0403]: nVidia Corporation MCP65 High Definition Audio [10de:044a] (rev a1)
00:08.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI bridge [10de:0449] (rev a1)
00:09.0 IDE interface [0101]: nVidia Corporation MCP65 IDE [10de:0448] (rev a1)
00:0a.0 IDE interface [0101]: nVidia Corporation MCP65 SATA Controller [10de:045d] (rev a3)
00:0b.0 PCI bridge [0604]: nVidia Corporation Device [10de:045b] (rev a1)
00:0c.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI Express bridge [10de:045a] (rev a1)
00:0d.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI Express bridge [10de:0458] (rev a1)
00:0e.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI Express bridge [10de:0459] (rev a1)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g [14e4:4312] (rev 02)
05:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [GeForce 8400M GS] [10de:0427] (rev a1)
07:05.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05)
07:05.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22)
07:05.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 12)
07:05.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12)
07:05.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev ff)
Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 04f2:b023 Chicony Electronics Co., Ltd Gateway USB 2.0 Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
H/W path Device Class Description
===================================================
                            system HP Pavilion dv9700 Notebook PC
/0 bus 30DA
/0/0 memory 101KiB BIOS
/0/4 processor AMD Turion(tm) 64 X2 Mobile Technology T
/0/4/5 memory 128KiB L1 cache
/0/4/6 memory 512KiB L2 cache
/0/3 memory 2GiB System Memory
/0/3/0 memory 1GiB DIMM DDR2 Synchronous 667 MHz (1.5
/0/3/1 memory 1GiB DIMM DDR2 667 MHz (1.5 ns)
/0/5 processor
/0/5/0 memory 128KiB L1 cache
/0/5/1 memory 512KiB L2 cache
/0/b memory RAM memory
/0/1 bridge MCP65 LPC Bridge
/0/1.1 bus MCP65 SMBus
/0/1.3 processor MCP65 SMU
/0/2 bus MCP65 USB Controller
/0/2.1 bus MCP65 USB Controller
/0/6 eth0 network MCP65 Ethernet
/0/7 multimedia MCP65 High Definition Audio
/0/8 bridge MCP65 PCI bridge
/0/8/5 bus R5C832 IEEE 1394 Controller
/0/8/5.1 generic R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter
/0/8/5.2 generic R5C592 Memory Stick Bus Host Adapter
/0/8/5.3 generic xD-Picture Card Controller
/0/8/5.4 generic Illegal Vendor ID
/0/9 scsi0 storage MCP65 IDE
/0/9/0.0.0 /dev/cdrom disk CDDVDW TS-L632N
/0/a scsi2 storage MCP65 SATA Controller
/0/a/0.0.0 /dev/sda disk 250GB Hitachi HTS54252
/0/a/0.0.0/1 /dev/sda1 volume 227GiB EXT4 volume
/0/a/0.0.0/2 /dev/sda2 volume 5896MiB Extended partition
/0/a/0.0.0/2/5 /dev/sda5 volume 5896MiB Linux swap / Solaris partition
/0/100 bridge nVidia Corporation
/0/c bridge MCP65 PCI Express bridge
/0/c/0 eth1 network BCM4312 802.11a/b/g
/0/d bridge MCP65 PCI Express bridge
/0/d/0 display G86 [GeForce 8400M GS]
/0/e bridge MCP65 PCI Express bridge
/0/101 bridge K8 [Athlon64/Opteron] HyperTransport Tec
/0/102 bridge K8 [Athlon64/Opteron] Address Map
/0/103 bridge K8 [Athlon64/Opteron] DRAM Controller
/0/104 bridge K8 [Athlon64/Opteron] Miscellaneous Cont
Linux PC10-135 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux
[ 0.000000] found SMP MP-table at [c00f8640] f8640
[ 0.183102] ACPI: No dock devices found.
[ 0.224576] pnp: PnP ACPI: found 12 devices
[ 0.261137] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.261188] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.261255] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.261320] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.261389] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.261463] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.305413] hub 1-0:1.0: USB hub found
[ 0.419173] hub 2-0:1.0: USB hub found
[ 0.433047] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 0.434689] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology TL-60 processors (2 cpu cores) (version 2.20.00)
[ 0.461430] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.634488] isapnp: No Plug & Play device found
[ 18.603554] lp: driver loaded but no devices found
[ 19.016105] ricoh-mmc: Ricoh MMC controller found at 0000:07:05.2 [1180:0843] (rev 12)
[ 19.021177] sdhci-pci 0000:07:05.1: SDHCI controller found [1180:0822] (rev 22)
[ 20.493616] uvcvideo: Found UVC 1.00 device HP Webcam (04f2:b023)
[ 21.100233] input: HDA NVidia Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input9
[ 21.100409] input: HDA NVidia Headphone as /devices/pci0000:00/0000:00:07.0/sound/card0/input10
[ 0.222985] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC0.PMIO._CRS] (Node f7015900), AE_AML_BUFFER_LIMIT
[ 0.223018] ACPI Error (uteval-0250): Method execution failed [\_SB_.PCI0.LPC0.PMIO._CRS] (Node f7015900), AE_AML_BUFFER_LIMIT
[ 0.983293] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[ 0.983648] forcedeth 0000:00:06.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20
[ 0.983653] forcedeth 0000:00:06.0: setting latency timer to 64
[ 1.501213] forcedeth 0000:00:06.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1e:68:26:ed:c4
[ 1.501218] forcedeth 0000:00:06.0: highdma pwrctl mgmt gbit lnktim msi desc-v3
[ 20.519558] eth1: Broadcom BCM4312 802.11 Hybrid Wireless Controller 5.60.48.36
[ 29.684023] eth0: no IPv6 routers present
[ 30.240021] eth1: no IPv6 routers present
[ 0.433044] device-mapper: multipath: version 1.1.0 loaded
[ 0.433047] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 19.051898] wl: module license 'MIXED/Proprietary' taints kernel.
[ 19.072637] wl 0000:03:00.0: PCI INT A -> Link[LK1E] -> GSI 16 (level, low) -> IRQ 16
[ 19.072644] wl 0000:03:00.0: setting latency timer to 64
[ 0.168092] Switch to broadcast mode on CPU1
[ 0.168417] Switch to broadcast mode on CPU0
[ 0.220005] Switching to clocksource hpet
[ 0.275764] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 0.276057] ACPI: Lid Switch [LID]
[ 20.514673] Console: switching to colour frame buffer device 80x30
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Access Point: Not-Associated
          Link Quality:4 Signal level:194 Noise level:199
          Rx invalid nwid:0 invalid crypt:1 invalid misc:0

pan0 no wireless extensions.

/etc/modprobe.d/blacklist-bcm43.conf:blacklist b43
/etc/modprobe.d/blacklist-bcm43.conf:blacklist b43legacy
/etc/modprobe.d/blacklist.conf:# replaced by b43 and ssb.
/etc/modprobe.d/blacklist-bcm43.conf:# Warning: This file is autogenerated by bcmwl. All changes to this file will be lost.
/etc/modprobe.d/blacklist-watchdog.conf:blacklist twl4030_wdt
sudo: hwinfo: command not found
 * Reconfiguring network interfaces... Ignoring unknown interface eth0=eth0.
Ignoring unknown interface eth1=eth1.
                                                                         [ OK ]

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#3

It is possible that the following part of the whole command TEMPORARILY fixed the issue (as a workaround):

sudo /etc/init.d/networking restart

But the worrying thing is the output of the command 'sudo iwlist scanning' which is:

eth1 Failed to read scan data : Invalid argument

So the wireless card is still unable to list any available wireless access points.....

Please try this procedure:

Try unplugging the laptop and removing the battery. Wait a few minutes and then try to power it back up. Right after booting, go into the BIOS and first choose the option "Load default values". Still in the BIOS, look for the wireless settings. If possible, choose the wireless option "By application", or else choose "enable" for wireless.

Then reboot and retest wireless. If wireless is still not working, please resend us output of the following command:

sudo lshw -C network; rfkill list; sudo iwlist scanning; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -short; uname -a; dmesg | grep ound; dmesg | grep irmware ; dmesg | grep ipw; dmesg | grep eth; dmesg | grep ath; dmesg | grep b43; dmesg | grep wl; dmesg | grep witch; iwconfig; grep b43 /etc/modprobe.d/*; grep wl /etc/modprobe.d/*; sudo hwinfo --netcard ; sudo /etc/init.d/networking restart

Revision history for this message
Willem Hobers (whobers) said : 		#4

Hi Mark,

Thanks for your quick reply.

I'm a bit hesitant to set my BIOS to "default values". Before I do that I would like to report that the wireless is still working.

As stated before it started working out of the blue, but I noticed it only after I had run the commands you suggested.
Since then I have had this laptop turned off for a couple of hours. And now wireless is still working. I am typing this whilst being wirelessly connected. So, it seems: problem solved?

I would also like to report that Network manager is reporting 6 AP's which I can connect to. Including my own.

The iwlist tells me:

willem@PC10-135:~$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Failed to read scan data : Invalid argument

pan0 Interface doesn't support scanning.

Ah, hold your horses and curse my feline whiskers: suddenly the wireless connection is gone again (as of now)! (A result of the iwlist scanning, do you think?)

I'll try sudo /etc/init.d/networking restart, and see what happens.

willem@PC10-135:~$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces...
Ignoring unknown interface eth1=eth1.
Ignoring unknown interface eth0=eth0.

Nope. No such luck. Wireless (Network manager) shows its scanning animation... (Hmmm, how come eth1 en 0 are unknown interfaces?)

Second attempt:
willem@PC10-135:~$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces... [ OK ]

(Hmmm, no unkown interfaces?)

Network Manager still showing its scanning animation.

Now (three? minutes later) it gives up and shows the red exclamation mark in the wireless network symbol.... but: there *is* a connection! And I have no cable plugged in.

Weird.

No, wait: connection gone again.

8-(

Well, let's see:

willem@PC10-135:~$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

pan0 Interface doesn't support scanning.

willem@PC10-135:~$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces...
Ignoring unknown interface eth0=eth0.
                                                                         [ OK ]

(Hmm, only one unknown interface...)

Wireless symbol scanning again.... nothing happens.
Another attempt:

willem@PC10-135:~$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces... [ OK ]

(No unknown interfaces!)

Network manager still shows the 6 access points.

Wireless connection remains down but still scanning.

And now it has given up.

Do you -with this extra information - still think tampering with my laptop's BIOS might help solve this issue? In what way might that be helpful? Please advice.

Thanks for your patience and help.

Revision history for this message
Willem Hobers (whobers) said : 		#5

I had a look in daemon.log. Perhaps the contents are helpful [1]

FYI: the "periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))" message I have reported elsewhere (bug 291760). Do you think this bug might be connected to the issue we are trying to resolve here?

[1]
May 30 15:29:31 PC10-135 avahi-daemon[712]: Found user 'avahi' (UID 104) and group 'avahi' (GID 111).
May 30 15:29:31 PC10-135 avahi-daemon[712]: Successfully dropped root privileges.
May 30 15:29:31 PC10-135 avahi-daemon[712]: avahi-daemon 0.6.25 starting up.
May 30 15:29:31 PC10-135 avahi-daemon[712]: Successfully called chroot().
May 30 15:29:31 PC10-135 avahi-daemon[712]: Successfully dropped remaining capabilities.
May 30 15:29:31 PC10-135 bluetoothd[719]: Bluetooth daemon 4.60
May 30 15:29:31 PC10-135 bluetoothd[737]: Starting SDP server
May 30 15:29:31 PC10-135 avahi-daemon[712]: No service file found in /etc/avahi/services.
May 30 15:29:31 PC10-135 avahi-daemon[712]: Network interface enumeration completed.
May 30 15:29:31 PC10-135 avahi-daemon[712]: Registering HINFO record with values 'I686'/'LINUX'.
May 30 15:29:31 PC10-135 avahi-daemon[712]: Server startup complete. Host name is PC10-135.local. Local service cookie is 905364938.
May 30 15:29:31 PC10-135 NetworkManager: <info> starting...
May 30 15:29:31 PC10-135 NetworkManager: <info> Trying to start the modem-manager...
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: init!
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: update_system_hostname
May 30 15:29:31 PC10-135 NetworkManager: SCPluginIfupdown: management mode: unmanaged
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:06.0/net/eth0, iface: eth0)
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:06.0/net/eth0, iface: eth0): no ifupdown configuration found.
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:0c.0/0000:03:00.0/net/eth1, iface: eth1)
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:0c.0/0000:03:00.0/net/eth1, iface: eth1): no ifupdown configuration found.
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: end _init.
May 30 15:29:31 PC10-135 NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
May 30 15:29:31 PC10-135 NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
May 30 15:29:31 PC10-135 NetworkManager: <info> WiFi enabled by radio killswitch; enabled by state file
May 30 15:29:31 PC10-135 NetworkManager: <info> WWAN enabled by radio killswitch; enabled by state file
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: (164266736) ... get_connections.
May 30 15:29:31 PC10-135 NetworkManager: SCPlugin-Ifupdown: (164266736) ... get_connections (managed=false): return empty list.
May 30 15:29:31 PC10-135 NetworkManager: Ifupdown: get unmanaged devices count: 0
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): carrier is OFF
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): new Ethernet device (driver: 'forcedeth')
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): now managed
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Ericsson MBM
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): bringing up device.
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Option
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Option High-Speed
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Gobi
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Sierra
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Longcheer
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Huawei
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Nokia
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Generic
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): preparing device.
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin Novatel
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): deactivating device (reason: 2).
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin MotoC
May 30 15:29:31 PC10-135 NetworkManager: Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:06.0/net/eth0
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin AnyData
May 30 15:29:31 PC10-135 modem-manager: Loaded plugin ZTE
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): driver supports SSID scans (scan_capa 0x01).
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): new 802.11 WiFi device (driver: 'wl')
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): now managed
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): device state change: 1 -> 2 (reason 2)
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): bringing up device.
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): preparing device.
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth1): deactivating device (reason: 2).
May 30 15:29:31 PC10-135 NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): carrier now ON (device state 2)
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 30 15:29:31 PC10-135 NetworkManager: <info> modem-manager is now available
May 30 15:29:31 PC10-135 NetworkManager: <info> Trying to start the supplicant...
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 30 15:29:31 PC10-135 NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 30 15:29:31 PC10-135 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)
May 30 15:29:32 PC10-135 bluetoothd[737]: Starting experimental netlink support
May 30 15:29:32 PC10-135 bluetoothd[737]: Failed to find Bluetooth netlink family
May 30 15:29:32 PC10-135 bluetoothd[737]: Failed to init netlink plugin
May 30 15:29:32 PC10-135 NetworkManager: <info> dhclient started with pid 779
May 30 15:29:32 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
May 30 15:29:32 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 30 15:29:32 PC10-135 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:0c.0/0000:03:00.0/net/eth1, iface: eth1)
May 30 15:29:32 PC10-135 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:0c.0/0000:03:00.0/net/eth1, iface: eth1): no ifupdown configuration found.
May 30 15:29:32 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
May 30 15:29:32 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
May 30 15:29:32 PC10-135 NetworkManager: <info> (eth1): supplicant manager state: down -> idle
May 30 15:29:32 PC10-135 NetworkManager: <info> (eth1): device state change: 2 -> 3 (reason 0)
May 30 15:29:32 PC10-135 dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 30 15:29:32 PC10-135 dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 30 15:29:32 PC10-135 dhclient: All rights reserved.
May 30 15:29:32 PC10-135 dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 30 15:29:32 PC10-135 dhclient:
May 30 15:29:32 PC10-135 NetworkManager: <info> (eth1): supplicant interface state: starting -> ready
May 30 15:29:32 PC10-135 bluetoothd[737]: bridge pan0 created
May 30 15:29:32 PC10-135 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan0, iface: pan0)
May 30 15:29:32 PC10-135 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found.
May 30 15:29:32 PC10-135 NetworkManager: <WARN> device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
May 30 15:29:32 PC10-135 bluetoothd[737]: HCI dev 0 registered
May 30 15:29:32 PC10-135 NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: No such adapter
May 30 15:29:32 PC10-135 bluetoothd[737]: HCI dev 0 up
May 30 15:29:32 PC10-135 bluetoothd[737]: Starting security manager 0
May 30 15:29:32 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
May 30 15:29:32 PC10-135 dhclient: Listening on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:29:32 PC10-135 dhclient: Sending on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:29:32 PC10-135 dhclient: Sending on Socket/fallback
May 30 15:29:32 PC10-135 gdm-binary[820]: WARNING: Unable to load file '/etc/gdm/custom.conf': Bestand of map bestaat niet
May 30 15:29:32 PC10-135 bluetoothd[737]: probe failed with driver input-headset for device /org/bluez/719/hci0/dev_00_17_E6_C3_78_C6
May 30 15:29:32 PC10-135 bluetoothd[737]: probe failed with driver input-headset for device /org/bluez/719/hci0/dev_C8_7E_75_45_7E_28
May 30 15:29:32 PC10-135 bluetoothd[737]: Adapter /org/bluez/719/hci0 has been enabled
May 30 15:29:32 PC10-135 gdm-simple-slave[939]: WARNING: Unable to load file '/etc/gdm/custom.conf': Bestand of map bestaat niet
May 30 15:29:32 PC10-135 avahi-daemon[712]: Registering new address record for fe80::21a:73ff:fefa:7fea on eth1.*.
May 30 15:29:32 PC10-135 gdm-binary[820]: WARNING: Unable to find users: no seat-id found
May 30 15:29:32 PC10-135 init: apport pre-start process (976) terminated with status 1
May 30 15:29:32 PC10-135 acpid: starting up with proc fs
May 30 15:29:32 PC10-135 acpid: 36 rules loaded
May 30 15:29:32 PC10-135 acpid: waiting for events: event logging is off
May 30 15:29:32 PC10-135 init: apport post-stop process (989) terminated with status 1
May 30 15:29:33 PC10-135 avahi-daemon[712]: Registering new address record for fe80::21e:68ff:fe26:edc4 on eth0.*.
May 30 15:29:33 PC10-135 acpid: client connected from 1122[0:0]
May 30 15:29:33 PC10-135 acpid: 1 client rule loaded
May 30 15:29:34 PC10-135 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
May 30 15:29:34 PC10-135 dhclient: DHCPOFFER of 192.168.123.10 from 192.168.123.254
May 30 15:29:34 PC10-135 dhclient: DHCPREQUEST of 192.168.123.10 on eth0 to 255.255.255.255 port 67
May 30 15:29:34 PC10-135 dhclient: DHCPACK of 192.168.123.10 from 192.168.123.254
May 30 15:29:34 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
May 30 15:29:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 30 15:29:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
May 30 15:29:34 PC10-135 NetworkManager: <info> address 192.168.123.10
May 30 15:29:34 PC10-135 NetworkManager: <info> prefix 24 (255.255.255.0)
May 30 15:29:34 PC10-135 NetworkManager: <info> gateway 192.168.123.254
May 30 15:29:34 PC10-135 NetworkManager: <info> nameserver '212.54.35.25'
May 30 15:29:34 PC10-135 NetworkManager: <info> nameserver '192.168.123.254'
May 30 15:29:34 PC10-135 NetworkManager: <info> domain name 'xxxxx.xx.xxxx.xx'
May 30 15:29:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 30 15:29:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
May 30 15:29:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 30 15:29:34 PC10-135 avahi-daemon[712]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:29:34 PC10-135 avahi-daemon[712]: New relevant interface eth0.IPv4 for mDNS.
May 30 15:29:34 PC10-135 avahi-daemon[712]: Registering new address record for 192.168.123.10 on eth0.IPv4.
May 30 15:29:34 PC10-135 dhclient: bound to 192.168.123.10 -- renewal in 3446984 seconds.
May 30 15:29:34 PC10-135 init: ureadahead-other main process (1206) terminated with status 4
May 30 15:29:34 PC10-135 init: ureadahead-other main process (1208) terminated with status 4
May 30 15:29:35 PC10-135 NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 30 15:29:35 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:29:35 PC10-135 NetworkManager: <info> Activation (eth0) successful, device activated.
May 30 15:29:35 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 30 15:29:36 PC10-135 acpid: client connected from 1122[0:0]
May 30 15:29:36 PC10-135 acpid: 1 client rule loaded
May 30 15:29:37 PC10-135 ntpdate[1285]: adjust time server 91.189.94.4 offset -0.145796 sec
May 30 15:29:37 PC10-135 wpa_supplicant[764]: WPS-AP-AVAILABLE
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) starting connection 'Draadloze verbinding 1'
May 30 15:29:37 PC10-135 NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:29:37 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:29:37 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:29:37 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:29:37 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:29:37 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:29:37 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:29:37 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:29:37 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:29:37 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:29:37 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:29:37 PC10-135 gdm-session-worker[1321]: WARNING: Unable to load file '/etc/gdm/custom.conf': Bestand of map bestaat niet
May 30 15:29:37 PC10-135 polkitd[1340]: started daemon version 0.96 using authority implementation `local' version `0.96'
May 30 15:29:38 PC10-135 gdm-simple-greeter[1320]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.1/gtk/gtkwidget.c:5636: widget not within a GtkWindow
May 30 15:29:38 PC10-135 acpid: client connected from 1413[108:114]
May 30 15:29:38 PC10-135 acpid: 1 client rule loaded
May 30 15:29:39 PC10-135 gdm-session-worker[1321]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
May 30 15:29:42 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:29:45 PC10-135 gdm-session-worker[1423]: WARNING: Unable to load file '/etc/gdm/custom.conf': Bestand of map bestaat niet
May 30 15:29:46 PC10-135 gdm-session-worker[1423]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
May 30 15:29:47 PC10-135 wpa_supplicant[764]: Trying to associate with 00:50:18:3e:bb:c0 (SSID='drdls' freq=2462 MHz)
May 30 15:29:47 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating
May 30 15:29:47 PC10-135 wpa_supplicant[764]: Association request to the driver failed
May 30 15:29:52 PC10-135 wpa_supplicant[764]: Associated with 00:50:18:3e:bb:c0
May 30 15:29:52 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: associating -> associated
May 30 15:29:52 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: associated -> 4-way handshake
May 30 15:29:52 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> group handshake
May 30 15:29:52 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:29:53 PC10-135 wpa_supplicant[764]: WPA: Key negotiation completed with 00:50:18:3e:bb:c0 [PTK=TKIP GTK=TKIP]
May 30 15:29:53 PC10-135 wpa_supplicant[764]: CTRL-EVENT-CONNECTED - Connection to 00:50:18:3e:bb:c0 completed (auth) [id=0 id_str=]
May 30 15:29:53 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: group handshake -> completed
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'drdls'.
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
May 30 15:29:53 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 7 (reason 0)
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Beginning DHCP transaction (timeout in 45 seconds)
May 30 15:29:53 PC10-135 NetworkManager: <info> dhclient started with pid 1490
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) scheduled...
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) started...
May 30 15:29:53 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) complete.
May 30 15:29:53 PC10-135 dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 30 15:29:53 PC10-135 dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 30 15:29:53 PC10-135 dhclient: All rights reserved.
May 30 15:29:53 PC10-135 dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 30 15:29:53 PC10-135 dhclient:
May 30 15:29:53 PC10-135 NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit
May 30 15:29:53 PC10-135 dhclient: Listening on LPF/eth1/00:1a:73:fa:7f:ea
May 30 15:29:53 PC10-135 dhclient: Sending on LPF/eth1/00:1a:73:fa:7f:ea
May 30 15:29:53 PC10-135 dhclient: Sending on Socket/fallback
May 30 15:29:53 PC10-135 gnome-session[1463]: WARNING: Could not parse desktop file /home/willem/.config/autostart/drapes.desktop: Het sleutelbestand bevat geen sleutel ‘Type’
May 30 15:29:53 PC10-135 gnome-session[1463]: WARNING: could not read /home/willem/.config/autostart/drapes.desktop
May 30 15:29:54 PC10-135 dhclient: DHCPREQUEST of 192.168.123.135 on eth1 to 255.255.255.255 port 67
May 30 15:29:54 PC10-135 dhclient: DHCPACK of 192.168.123.135 from 192.168.123.254
May 30 15:29:54 PC10-135 dhclient: bound to 192.168.123.135 -- renewal in 3263727 seconds.
May 30 15:29:54 PC10-135 NetworkManager: <info> DHCP: device eth1 state changed preinit -> reboot
May 30 15:29:54 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 30 15:29:54 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started...
May 30 15:29:54 PC10-135 NetworkManager: <info> address 192.168.123.135
May 30 15:29:54 PC10-135 NetworkManager: <info> prefix 24 (255.255.255.0)
May 30 15:29:54 PC10-135 NetworkManager: <info> gateway 192.168.123.254
May 30 15:29:54 PC10-135 NetworkManager: <info> nameserver '212.54.35.25'
May 30 15:29:54 PC10-135 NetworkManager: <info> nameserver '192.168.123.254'
May 30 15:29:54 PC10-135 NetworkManager: <info> domain name 'xxxxx.xx.xxxx.xx'
May 30 15:29:54 PC10-135 NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
May 30 15:29:54 PC10-135 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete.
May 30 15:29:54 PC10-135 NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
May 30 15:29:54 PC10-135 avahi-daemon[712]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.123.135.
May 30 15:29:54 PC10-135 avahi-daemon[712]: New relevant interface eth1.IPv4 for mDNS.
May 30 15:29:54 PC10-135 avahi-daemon[712]: Registering new address record for 192.168.123.135 on eth1.IPv4.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully called chroot.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully dropped privileges.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully limited resources.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Running.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Watchdog thread running.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully made thread 1528 of process 1528 (n/a) owned by '1000' high priority at nice level -11.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Canary thread running.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Supervising 1 threads of 1 processes of 1 users.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully made thread 1540 of process 1528 (n/a) owned by '1000' RT at priority 5.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Supervising 2 threads of 1 processes of 1 users.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Sucessfully made thread 1543 of process 1528 (n/a) owned by '1000' RT at priority 5.
May 30 15:29:54 PC10-135 rtkit-daemon[1530]: Supervising 3 threads of 1 processes of 1 users.
May 30 15:29:55 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:29:55 PC10-135 NetworkManager: <info> (eth1): device state change: 7 -> 8 (reason 0)
May 30 15:29:55 PC10-135 NetworkManager: <info> Activation (eth1) successful, device activated.
May 30 15:29:55 PC10-135 NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
May 30 15:29:56 PC10-135 ntpdate[1588]: adjust time server 91.189.94.4 offset -0.136802 sec
May 30 15:30:20 PC10-135 NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 30 15:30:24 PC10-135 NetworkManager: <info> (eth0): device state change: 8 -> 2 (reason 40)
May 30 15:30:24 PC10-135 NetworkManager: <info> (eth0): deactivating device (reason: 40).
May 30 15:30:25 PC10-135 NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 779
May 30 15:30:25 PC10-135 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
May 30 15:30:25 PC10-135 avahi-daemon[712]: Withdrawing address record for 192.168.123.10 on eth0.
May 30 15:30:25 PC10-135 avahi-daemon[712]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:30:25 PC10-135 avahi-daemon[712]: Interface eth0.IPv4 no longer relevant for mDNS.
May 30 15:30:25 PC10-135 NetworkManager: <info> Policy set 'Draadloze verbinding 1' (eth1) as default for routing and DNS.
May 30 15:30:26 PC10-135 NetworkManager: <debug> [1275226226.000472] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:30:32 PC10-135 NetworkManager: <debug> [1275226232.001080] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:30:38 PC10-135 NetworkManager: <debug> [1275226238.002359] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:30:50 PC10-135 NetworkManager: <debug> [1275226250.010073] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:30:56 PC10-135 NetworkManager: <debug> [1275226256.002127] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:30:59 PC10-135 AptDaemon: INFO: Initializing daemon
May 30 15:31:14 PC10-135 NetworkManager: <debug> [1275226274.005418] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:31:20 PC10-135 NetworkManager: <debug> [1275226280.002946] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:31:26 PC10-135 NetworkManager: <debug> [1275226286.006923] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:31:38 PC10-135 NetworkManager: <debug> [1275226298.005003] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:31:56 PC10-135 NetworkManager: <debug> [1275226316.006801] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:32:02 PC10-135 NetworkManager: <debug> [1275226322.001194] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:32:08 PC10-135 NetworkManager: <debug> [1275226328.002675] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:32:14 PC10-135 NetworkManager: <debug> [1275226334.002868] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:32:32 PC10-135 NetworkManager: <debug> [1275226352.002021] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:32:44 PC10-135 NetworkManager: <debug> [1275226364.006724] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:32:56 PC10-135 NetworkManager: <debug> [1275226376.002744] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:33:02 PC10-135 NetworkManager: <debug> [1275226382.002929] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:33:20 PC10-135 NetworkManager: <debug> [1275226400.002818] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:33:26 PC10-135 NetworkManager: <debug> [1275226406.003755] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:33:38 PC10-135 NetworkManager: <debug> [1275226418.006983] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:33:44 PC10-135 NetworkManager: <debug> [1275226424.006729] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:34:26 PC10-135 NetworkManager: <debug> [1275226466.002922] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:34:32 PC10-135 NetworkManager: <debug> [1275226472.001861] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:34:38 PC10-135 NetworkManager: <debug> [1275226478.004906] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:35:08 PC10-135 NetworkManager: <debug> [1275226508.006316] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:35:14 PC10-135 NetworkManager: <debug> [1275226514.006624] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:35:26 PC10-135 NetworkManager: <debug> [1275226526.006360] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:35:32 PC10-135 NetworkManager: <debug> [1275226532.004979] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:35:44 PC10-135 NetworkManager: <debug> [1275226544.006737] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:35:50 PC10-135 NetworkManager: <debug> [1275226550.002858] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:35:56 PC10-135 NetworkManager: <debug> [1275226556.006875] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:36:00 PC10-135 AptDaemon: INFO: Quiting due to inactivity
May 30 15:36:00 PC10-135 AptDaemon: INFO: Shutdown was requested
May 30 15:36:08 PC10-135 NetworkManager: <debug> [1275226568.001124] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:36:20 PC10-135 NetworkManager: <debug> [1275226580.007055] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:37:08 PC10-135 NetworkManager: <debug> [1275226628.003559] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:37:14 PC10-135 NetworkManager: <debug> [1275226634.002872] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:37:26 PC10-135 NetworkManager: <debug> [1275226646.003353] periodic_update(): Roamed from BSSID (none) ((none)) to 00:50:18:3E:BB:C0 (drdls)
May 30 15:37:32 PC10-135 NetworkManager: <debug> [1275226652.002591] periodic_update(): Roamed from BSSID 00:50:18:3E:BB:C0 (drdls) to (none) ((none))
May 30 15:40:34 PC10-135 NetworkManager: <info> (eth0): carrier now ON (device state 2)
May 30 15:40:34 PC10-135 NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
May 30 15:40:34 PC10-135 NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 30 15:40:34 PC10-135 NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 30 15:40:34 PC10-135 NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)
May 30 15:40:34 PC10-135 NetworkManager: <info> dhclient started with pid 2113
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
May 30 15:40:34 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
May 30 15:40:34 PC10-135 dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 30 15:40:34 PC10-135 dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 30 15:40:34 PC10-135 dhclient: All rights reserved.
May 30 15:40:34 PC10-135 dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 30 15:40:34 PC10-135 dhclient:
May 30 15:40:34 PC10-135 dhclient: Listening on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:40:34 PC10-135 dhclient: Sending on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:40:34 PC10-135 dhclient: Sending on Socket/fallback
May 30 15:40:34 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed normal exit -> preinit
May 30 15:40:36 PC10-135 dhclient: DHCPREQUEST of 192.168.123.10 on eth0 to 255.255.255.255 port 67
May 30 15:40:36 PC10-135 dhclient: DHCPACK of 192.168.123.10 from 192.168.123.254
May 30 15:40:36 PC10-135 dhclient: bound to 192.168.123.10 -- renewal in 3179224 seconds.
May 30 15:40:36 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed preinit -> reboot
May 30 15:40:36 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 30 15:40:36 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
May 30 15:40:36 PC10-135 NetworkManager: <info> address 192.168.123.10
May 30 15:40:36 PC10-135 NetworkManager: <info> prefix 24 (255.255.255.0)
May 30 15:40:36 PC10-135 NetworkManager: <info> gateway 192.168.123.254
May 30 15:40:36 PC10-135 NetworkManager: <info> nameserver '212.54.35.25'
May 30 15:40:36 PC10-135 NetworkManager: <info> nameserver '192.168.123.254'
May 30 15:40:36 PC10-135 NetworkManager: <info> domain name 'xxxxx.xx.xxxx.xx'
May 30 15:40:36 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 30 15:40:36 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
May 30 15:40:36 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 30 15:40:36 PC10-135 avahi-daemon[712]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:40:36 PC10-135 avahi-daemon[712]: New relevant interface eth0.IPv4 for mDNS.
May 30 15:40:36 PC10-135 avahi-daemon[712]: Registering new address record for 192.168.123.10 on eth0.IPv4.
May 30 15:40:37 PC10-135 NetworkManager: <info> Policy set 'Draadloze verbinding 1' (eth1) as default for routing and DNS.
May 30 15:40:37 PC10-135 NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 30 15:40:37 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:40:37 PC10-135 NetworkManager: <info> Activation (eth0) successful, device activated.
May 30 15:40:37 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 30 15:40:37 PC10-135 ntpdate[2154]: adjust time server 91.189.94.4 offset 0.026307 sec
May 30 15:41:26 PC10-135 NetworkManager: <info> (eth1): device state change: 8 -> 3 (reason 0)
May 30 15:41:26 PC10-135 NetworkManager: <info> (eth1): deactivating device (reason: 0).
May 30 15:41:27 PC10-135 NetworkManager: <info> (eth1): canceled DHCP transaction, dhcp client pid 1490
May 30 15:41:27 PC10-135 avahi-daemon[712]: Withdrawing address record for 192.168.123.135 on eth1.
May 30 15:41:27 PC10-135 avahi-daemon[712]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.123.135.
May 30 15:41:27 PC10-135 avahi-daemon[712]: Interface eth1.IPv4 no longer relevant for mDNS.
May 30 15:41:27 PC10-135 wpa_supplicant[764]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
May 30 15:41:27 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) starting connection 'Draadloze verbinding 1'
May 30 15:41:27 PC10-135 NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:41:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: completed -> disconnected
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:41:27 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:41:27 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:41:27 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:41:27 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:41:27 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:41:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:41:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:41:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:41:27 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:41:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:42:27 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:42:27 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:42:27 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:42:27 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:42:27 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:42:27 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:42:27 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:42:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:42:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:42:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:42:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:42:27 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:42:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:42:42 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:43:02 PC10-135 NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 30 15:43:07 PC10-135 NetworkManager: <info> (eth0): device state change: 8 -> 2 (reason 40)
May 30 15:43:07 PC10-135 NetworkManager: <info> (eth0): deactivating device (reason: 40).
May 30 15:43:07 PC10-135 NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 2113
May 30 15:43:07 PC10-135 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
May 30 15:43:07 PC10-135 avahi-daemon[712]: Withdrawing address record for 192.168.123.10 on eth0.
May 30 15:43:07 PC10-135 avahi-daemon[712]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:43:07 PC10-135 avahi-daemon[712]: Interface eth0.IPv4 no longer relevant for mDNS.
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:43:27 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:43:27 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:43:27 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:43:27 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:43:27 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:43:27 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:43:27 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:43:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:43:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:43:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:43:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:43:27 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:43:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:43:42 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:44:27 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:44:27 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:44:27 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:44:27 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:44:27 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:44:27 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:44:27 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:44:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:44:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:44:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:44:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:44:27 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:44:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:44:42 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:45:27 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:45:27 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:45:27 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:45:27 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:45:27 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:45:27 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:45:27 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:45:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:45:27 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:45:27 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:45:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:45:27 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:45:27 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:45:42 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:46:27 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:46:27 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 9 (reason 7)
May 30 15:46:27 PC10-135 NetworkManager: <info> Activation (eth1) failed for access point (drdls)
May 30 15:46:27 PC10-135 NetworkManager: <info> Marking connection 'Draadloze verbinding 1' invalid.
May 30 15:46:27 PC10-135 NetworkManager: <info> Activation (eth1) failed.
May 30 15:46:27 PC10-135 NetworkManager: <info> (eth1): device state change: 9 -> 3 (reason 0)
May 30 15:46:27 PC10-135 NetworkManager: <info> (eth1): deactivating device (reason: 0).
May 30 15:46:27 PC10-135 NetworkManager: <WARN> nm_device_wifi_get_mode(): error getting card mode on eth1: Invalid argument
May 30 15:46:27 PC10-135 NetworkManager: <WARN> nm_device_wifi_set_mode(): error setting card eth1 to mode 2: Invalid argument
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) starting connection 'Draadloze verbinding 1'
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1/wireless): access point 'Draadloze verbinding 1' has security, but secrets are required.
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:48:15 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:48:15 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:48:15 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:48:15 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:48:15 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:48:15 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:48:15 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:48:15 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:48:15 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:48:31 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:48:43 PC10-135 NetworkManager: <info> (eth0): carrier now ON (device state 2)
May 30 15:48:43 PC10-135 NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
May 30 15:48:43 PC10-135 NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 30 15:48:43 PC10-135 NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 30 15:48:43 PC10-135 NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)
May 30 15:48:43 PC10-135 NetworkManager: <info> dhclient started with pid 2227
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
May 30 15:48:43 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
May 30 15:48:43 PC10-135 dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 30 15:48:43 PC10-135 dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 30 15:48:43 PC10-135 dhclient: All rights reserved.
May 30 15:48:43 PC10-135 dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 30 15:48:43 PC10-135 dhclient:
May 30 15:48:43 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed normal exit -> preinit
May 30 15:48:43 PC10-135 dhclient: Listening on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:48:43 PC10-135 dhclient: Sending on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:48:43 PC10-135 dhclient: Sending on Socket/fallback
May 30 15:48:47 PC10-135 dhclient: DHCPREQUEST of 192.168.123.10 on eth0 to 255.255.255.255 port 67
May 30 15:48:47 PC10-135 dhclient: DHCPACK of 192.168.123.10 from 192.168.123.254
May 30 15:48:47 PC10-135 dhclient: bound to 192.168.123.10 -- renewal in 3110341 seconds.
May 30 15:48:47 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed preinit -> reboot
May 30 15:48:47 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 30 15:48:47 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
May 30 15:48:47 PC10-135 NetworkManager: <info> address 192.168.123.10
May 30 15:48:47 PC10-135 NetworkManager: <info> prefix 24 (255.255.255.0)
May 30 15:48:47 PC10-135 NetworkManager: <info> gateway 192.168.123.254
May 30 15:48:47 PC10-135 NetworkManager: <info> nameserver '212.54.35.25'
May 30 15:48:47 PC10-135 NetworkManager: <info> nameserver '192.168.123.254'
May 30 15:48:47 PC10-135 NetworkManager: <info> domain name 'xxxxx.xx.xxxx.xx'
May 30 15:48:47 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 30 15:48:47 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
May 30 15:48:47 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 30 15:48:47 PC10-135 avahi-daemon[712]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:48:47 PC10-135 avahi-daemon[712]: New relevant interface eth0.IPv4 for mDNS.
May 30 15:48:47 PC10-135 avahi-daemon[712]: Registering new address record for 192.168.123.10 on eth0.IPv4.
May 30 15:48:48 PC10-135 NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 30 15:48:48 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:48:48 PC10-135 NetworkManager: <info> Activation (eth0) successful, device activated.
May 30 15:48:48 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 30 15:48:48 PC10-135 ntpdate[2270]: adjust time server 91.189.94.4 offset -0.044183 sec
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:49:16 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:49:16 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:49:16 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:49:16 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:49:16 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:49:16 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:49:16 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:49:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:49:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:49:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:49:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:49:16 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:49:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:49:31 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:50:16 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:50:16 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:50:16 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:50:16 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:50:16 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:50:16 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:50:16 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:50:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:50:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:50:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:50:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:50:16 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:50:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:50:31 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:51:16 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:51:16 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:51:16 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:51:16 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:51:16 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:51:16 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:51:16 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:51:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:51:16 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:51:16 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:51:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:51:16 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:51:16 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:51:31 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:52:07 PC10-135 NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 30 15:52:12 PC10-135 NetworkManager: <info> (eth0): device state change: 8 -> 2 (reason 40)
May 30 15:52:12 PC10-135 NetworkManager: <info> (eth0): deactivating device (reason: 40).
May 30 15:52:12 PC10-135 NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 2227
May 30 15:52:12 PC10-135 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
May 30 15:52:12 PC10-135 avahi-daemon[712]: Withdrawing address record for 192.168.123.10 on eth0.
May 30 15:52:12 PC10-135 avahi-daemon[712]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:52:12 PC10-135 avahi-daemon[712]: Interface eth0.IPv4 no longer relevant for mDNS.
May 30 15:52:16 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:52:16 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 9 (reason 7)
May 30 15:52:16 PC10-135 NetworkManager: <info> Activation (eth1) failed for access point (drdls)
May 30 15:52:16 PC10-135 NetworkManager: <info> Marking connection 'Draadloze verbinding 1' invalid.
May 30 15:52:16 PC10-135 NetworkManager: <info> Activation (eth1) failed.
May 30 15:52:16 PC10-135 NetworkManager: <info> (eth1): device state change: 9 -> 3 (reason 0)
May 30 15:52:16 PC10-135 NetworkManager: <info> (eth1): deactivating device (reason: 0).
May 30 15:52:16 PC10-135 NetworkManager: <WARN> nm_device_wifi_get_mode(): error getting card mode on eth1: Invalid argument
May 30 15:52:16 PC10-135 NetworkManager: <WARN> nm_device_wifi_set_mode(): error setting card eth1 to mode 2: Invalid argument
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) starting connection 'Draadloze verbinding 1'
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1/wireless): access point 'Draadloze verbinding 1' has security, but secrets are required.
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:52:40 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:52:40 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:52:40 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:52:40 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:52:40 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:52:40 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:52:40 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:52:40 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:52:40 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:53:41 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:53:41 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:53:41 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:53:41 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:53:41 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:53:41 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:53:41 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:53:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:53:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:53:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:53:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:53:41 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:53:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:53:56 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:54:41 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:54:41 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:54:41 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:54:41 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:54:41 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:54:41 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:54:41 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:54:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:54:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:54:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:54:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:54:41 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:54:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:54:44 PC10-135 NetworkManager: <info> (eth0): carrier now ON (device state 2)
May 30 15:54:44 PC10-135 NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
May 30 15:54:44 PC10-135 NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 30 15:54:44 PC10-135 NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 30 15:54:44 PC10-135 NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)
May 30 15:54:44 PC10-135 NetworkManager: <info> dhclient started with pid 2321
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
May 30 15:54:44 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
May 30 15:54:44 PC10-135 dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 30 15:54:44 PC10-135 dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 30 15:54:44 PC10-135 dhclient: All rights reserved.
May 30 15:54:44 PC10-135 dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 30 15:54:44 PC10-135 dhclient:
May 30 15:54:44 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed normal exit -> preinit
May 30 15:54:44 PC10-135 dhclient: Listening on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:54:44 PC10-135 dhclient: Sending on LPF/eth0/00:1e:68:26:ed:c4
May 30 15:54:44 PC10-135 dhclient: Sending on Socket/fallback
May 30 15:54:45 PC10-135 dhclient: DHCPREQUEST of 192.168.123.10 on eth0 to 255.255.255.255 port 67
May 30 15:54:45 PC10-135 dhclient: DHCPACK of 192.168.123.10 from 192.168.123.254
May 30 15:54:45 PC10-135 dhclient: bound to 192.168.123.10 -- renewal in 3380407 seconds.
May 30 15:54:45 PC10-135 NetworkManager: <info> DHCP: device eth0 state changed preinit -> reboot
May 30 15:54:45 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 30 15:54:45 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
May 30 15:54:45 PC10-135 NetworkManager: <info> address 192.168.123.10
May 30 15:54:45 PC10-135 NetworkManager: <info> prefix 24 (255.255.255.0)
May 30 15:54:45 PC10-135 NetworkManager: <info> gateway 192.168.123.254
May 30 15:54:45 PC10-135 NetworkManager: <info> nameserver '212.54.35.25'
May 30 15:54:45 PC10-135 NetworkManager: <info> nameserver '192.168.123.254'
May 30 15:54:45 PC10-135 NetworkManager: <info> domain name 'xxxxx.xx.xxxx.xx'
May 30 15:54:45 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 30 15:54:45 PC10-135 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
May 30 15:54:45 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 30 15:54:45 PC10-135 avahi-daemon[712]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.123.10.
May 30 15:54:45 PC10-135 avahi-daemon[712]: New relevant interface eth0.IPv4 for mDNS.
May 30 15:54:45 PC10-135 avahi-daemon[712]: Registering new address record for 192.168.123.10 on eth0.IPv4.
May 30 15:54:46 PC10-135 NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 30 15:54:46 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:54:46 PC10-135 NetworkManager: <info> Activation (eth0) successful, device activated.
May 30 15:54:46 PC10-135 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 30 15:54:46 PC10-135 ntpdate[2364]: adjust time server 91.189.94.4 offset -0.001673 sec
May 30 15:54:56 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:55:41 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May 30 15:55:41 PC10-135 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May 30 15:55:41 PC10-135 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): connection 'Draadloze verbinding 1' has security, and secrets exist. No new secrets needed.
May 30 15:55:41 PC10-135 NetworkManager: <info> Config: added 'ssid' value 'drdls'
May 30 15:55:41 PC10-135 NetworkManager: <info> Config: added 'scan_ssid' value '1'
May 30 15:55:41 PC10-135 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 30 15:55:41 PC10-135 NetworkManager: <info> Config: added 'psk' value '<omitted>'
May 30 15:55:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:55:41 PC10-135 NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
May 30 15:55:41 PC10-135 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May 30 15:55:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
May 30 15:55:41 PC10-135 NetworkManager: <info> Config: set interface ap_scan to 1
May 30 15:55:41 PC10-135 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
May 30 15:55:56 PC10-135 NetworkManager: <info> eth1: link timed out.
May 30 15:56:41 PC10-135 NetworkManager: <info> Activation (eth1/wireless): association took too long.
May 30 15:56:41 PC10-135 NetworkManager: <info> (eth1): device state change: 5 -> 9 (reason 7)
May 30 15:56:41 PC10-135 NetworkManager: <info> Activation (eth1) failed for access point (drdls)
May 30 15:56:41 PC10-135 NetworkManager: <info> Marking connection 'Draadloze verbinding 1' invalid.
May 30 15:56:41 PC10-135 NetworkManager: <info> Activation (eth1) failed.
May 30 15:56:41 PC10-135 NetworkManager: <info> (eth1): device state change: 9 -> 3 (reason 0)
May 30 15:56:41 PC10-135 NetworkManager: <info> (eth1): deactivating device (reason: 0).
May 30 15:56:41 PC10-135 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 30 15:56:41 PC10-135 NetworkManager: <WARN> nm_device_wifi_get_mode(): error getting card mode on eth1: Invalid argument
May 30 15:56:41 PC10-135 NetworkManager: <WARN> nm_device_wifi_set_mode(): error setting card eth1 to mode 2: Invalid argument

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#6

Try disabling security on the router and enabling SSID broadcasting on the router to see if it helps stabilize the connection. If it helps, then you will need to test various forms of encryption to see which encrypted connection (WEP or WPA) works in a stable way.

Still, I think it is also a good idea to disconnect the powerplug from the PC, remove the battery, wait a half an hour, then re-insert the laptop battery and then boot into the BIOS and set everything to "default values". It is not dangerous to set everything to default values. It is not tampering and definitely not like you are flashing the BIOS....

The more suggestions you follow, the higher the chance is that you will get this issue solved.....

Revision history for this message
Willem Hobers (whobers) said : 		#7

Thanks for your prompt suggestions; I appreciate it.

I'm a bit pressed for time, so have to keep it short.

The SSID is being broadcast by the router; I never have or had it disabled. I am sorry if I suggested otherwise.

There are more PC's using the AP to connect to the internet. (One of these is also running Lucid, and with a problem free wireless connection; the other is running an OS whose name shall not be mentioned-- also problem free, I am afraid to say.)

Anyway: disabling security on the router can only be done at a moment when the other PC's are not in use. I have to pick the right moment to disable security on the router and on the PC's. But I will be offline for a couple of days, so won't be able to follow up on this issue for now.

If you've got the time, I would like to know what it is that we are testing by turning off security on the AP. Is that a way to see if there is a hardware problem? Driver problem? Or have you already deduced from the information I provided that the encryption is possibly causing the instability?
And how about resetting the BIOS to default? Is that to find out whether there is a problem with the combination of this particular BIOS with this particular hardware/driver?
In short: what's the rationale behind these suggestions; also keeping in mind that this laptop had been having a problem free wireless connection for quite some time before this issue occurred?

Well, thanks for your time and effort.

I'll be back.

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#8

Concerning the rationale behind the suggestion to load "default values" in the BIOS: a very similar issue was solved by doing so as you can read here:

http://ubuntuforums.org/archive/index.php/t-1010751.html

Disabling wireless encryption to simplify the setup, is a matter of following the KISS principle (KISS = "keep it simple stupid")
It makes it easier to troubleshoot the issue, as there are less variables in the equation, if encryption is temporarily disabled....

Revision history for this message
Willem Hobers (whobers) said : 		#9

Hi Mark,

As of yesterday wireless is working again. Yesterday -after a few days of offlineness- I turned on the laptop. It reported some updates. Amongst which a new linux kernel and headers[1]. I duly ran the update, rebooted and from that moment on wireless is working again. Without flaw. <<Touching wood>>

I am no expert, believe me (well, you will, I am sure). But, being the simple user I am, it seems to me, that the wireless *was* working at first, then stopped working after an update. And now, after another update, the wireless is working again.
You being the expert, is there possibly any plausibility in this, my observation, do you think?

Do you think it is nonetheless useful to do any of the experiments you suggested earlier?
I am inclined to accept the fact that wireless is working again <<and touching wood again>>, and am inclined to not change anything for the moment. Would you concur?

Thanks.

[1]
willem@PC10-135:~$ uname -r
2.6.32-22-generic
willem@PC10-135:~$ dmesg | grep "Linux version"
[ 0.000000] Linux version 2.6.32-22-generic (buildd@vernadsky) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #35-Ubuntu SMP Tue Jun 1 14:17:36 UTC 2010 (Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2)

Revision history for this message
Best Mark Rijckenberg (markrijckenberg) said : 		#10

Yes, it is very plausible that a kernel update caused wifi to stop working and that an even newer kernel update fixed the issue.

My advice is:

"Never change a working configuration" (both on the hardware and software level)

Please set this thread to status "solved", if the issue is still solved.

Revision history for this message
Willem Hobers (whobers) said : 		#11

Mark,

thanks for your quick reply. Your advice seems sound.

Still: if only we'd know *what* it was that actually resolved the issue; one might feel a bit more confident, then, that the issue is indeed lastingly resolved.

Still: never change a winning team, as you suggest.

Marking the issue as solved.

Mark, Thanks for your help and advice; I appreciate it.

Revision history for this message
Willem Hobers (whobers) said : 		#12

Thanks Mark Rijckenberg, that solved my question.

Revision history for this message
Willem Hobers (whobers) said : 		#13

Not sure whether it is "done" to add a comment/question after a question has been closed, but:

Wireless is still working. Network manager is showing several AP's; including my own.

Yet: iwlist is still telling me it can't scan, due to an invalid argument[1].

Question: should I report this as a possible bug, do you think?
Please advice.

willem@PC10-135:~$ sudo iwlist scanning
[sudo] password for willem:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Failed to read scan data : Invalid argument

pan0 Interface doesn't support scanning.