| 2011-12-24 07:05:25 |
Shade |
bug |
|
|
added bug |
| 2011-12-24 07:06:53 |
Shade |
description |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I scoured the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I examined the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
|
| 2011-12-24 07:11:06 |
Shade |
description |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I examined the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D/D, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I examined the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
|
| 2011-12-24 07:11:14 |
Shade |
description |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D/D, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I examined the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
Found that if I set the immutable bit on /etc/resolv.conf that wicd really doesn't like it. Behavior is odd. For example, when I start wicd-curses I can attempt to connect to a wireless ap, but it will hang at "Obtaining ip address..." even though actually I can use the interface. What happens, it seems (?), is that wicd is cycle reconnecting. However, if I try to end the connection C^D/D/Q, then wicd-curses crashes:
DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 915, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 810, in handle_keys
daemon.Disconnect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In the GUI, it doesn't crash precisely, just hangs and ultimately becomes unresponsive. You cannot disconnect or reconnect, it just hangs at "Connecting..." or "Obtaining ip address...".
Setting the immutable bit on /etc/resolv.conf was a really, really rough way to set my nameservers to what I wanted, so I don't think this is that big of a deal. But maybe some sort of check and output. I examined the logs, and there doesn't seem to be anything amiss in them when this freezing/crashing happens. This is the log:
Connecting to wireless network XXXXXX
2011/12/23 22:59:05 :: attempting to set hostname with dhclient
2011/12/23 22:59:05 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:19 :: attempting to set hostname with dhclient
2011/12/23 22:59:19 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Putting interface down
2011/12/23 22:59:31 :: Releasing DHCP leases...
2011/12/23 22:59:31 :: attempting to set hostname with dhclient
2011/12/23 22:59:31 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:31 :: Setting false IP...
2011/12/23 22:59:31 :: Stopping wpa_supplicant
2011/12/23 22:59:31 :: Flushing the routing table...
2011/12/23 22:59:31 :: Putting interface up...
2011/12/23 22:59:33 :: Generating psk...
2011/12/23 22:59:33 :: Attempting to authenticate...
2011/12/23 22:59:35 :: Running DHCP with hostname XXXXXX
2011/12/23 22:59:35 :: attempting to set hostname with dhclient
2011/12/23 22:59:35 :: using dhcpcd or another supported client may work better
2011/12/23 22:59:35 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/12/23 22:59:35 :: Copyright 2004-2010 Internet Systems Consortium.
2011/12/23 22:59:35 :: All rights reserved.
2011/12/23 22:59:35 :: For info, please visit https://www.isc.org/software/dhcp/
2011/12/23 22:59:35 ::
2011/12/23 22:59:35 :: Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
2011/12/23 22:59:35 :: Sending on Socket/fallback
2011/12/23 22:59:35 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
2011/12/23 22:59:36 :: DHCPOFFER of 192.168.1.103 from 192.168.1.1
2011/12/23 22:59:36 :: DHCPREQUEST of 192.168.1.103 on wlan0 to 255.255.255.255 port 67
2011/12/23 22:59:36 :: DHCPACK of 192.168.1.103 from 192.168.1.1
After this point, it has already crashed.
Version: 1.7.0
OS: Kubuntu 11.10 |
|
