** Description changed:
Binary package hint: network-manager
I was using Intrepid Beta, and wired & wireless networking used to work fine.
After (failed) resurrection from hibernation (don't know if it has something
to do, but it just might), networking is a mess.
+
+ ** NETWORK MANAGER ERRONEOUSLY REPORTS WIRED CONNECTION DOWN
* The wired connection, which has a fixed IP, is reported disconnected
by NM, but is reported correct by ifconfig.
* The network parameters shown by NM for eth0 are funny: the address is
OK and the setting is reported "manual", which is right, but no DNS
entry is shown, and the mask is set to "24" instead of "192.168.0.255"
as shown by ifconfig.
* Edition of these parameters in NM fails after the "accept" button with the
message dialog:
"failed updating connection: nm-ifupdown-connection.c:82 - connection update
not supported (read only).."
+ ** NETWORK MANAGER HAS WIPED OUT RESOLV.CONF
+
* resolv.conf has been wiped out, and now only contains the message "#
Generated by NetworkManager". Adding the line "nameserver 192.168.0.1"
- makes the web visible again, although NetworkManager still considers the
- network unavailable.
+ makes the web visible again, although NetworkManager still show the
+ network as unavailable.
+
+ ** WIRELESS IS CONFIGURED OK, BUT WORKS EXXXTTTRRREEEMMMLLLYYY
+ SLOWLY
* If wireless is activated, a link is established with the router, and
- resolv.conf is wiped again and replaced with something that works. Going
- back to wired blanks resolv.conf again.
+ resolv.conf is wiped again and replaced with something that looks like:
+
+ #Generated by NetworkManager
+ domain home
+ search home
+ nameserver 192.168.0.1
+
+ * NetworkManager now reports the network as available, but it does not
+ work right. A ping to a web address (say google.com) takes about 5
+ seconds to start, although then it proceeds at the normal rate and with
+ normal ping times. Pinging the resolved address is no faster. Web pages
+ take ages to load or more typically time out. apt-get update takes more
+ than an hour.
+
+ An internal ping to my network is instantaneous.
+
+ Going back to wired blanks resolv.conf again.
+
+ ** THERE MAY BE MORE THAN ONE PROBLEM. UNINSTALLING NM DOES NOT FIX IT
* uninstalling NM, wiping its traces and reinstalling does not fix the
problem. (maybe there are more traces left than I wiped out)
** Description changed:
Binary package hint: network-manager
I was using Intrepid Beta, and wired & wireless networking used to work fine.
After (failed) resurrection from hibernation (don't know if it has something
to do, but it just might), networking is a mess.
- ** NETWORK MANAGER ERRONEOUSLY REPORTS WIRED CONNECTION DOWN
+ ** NETWORK MANAGER ERRONEOUSLY REPORTS WIRED CONNECTION DOWN, DISALLOWS
+ EDITING
* The wired connection, which has a fixed IP, is reported disconnected
by NM, but is reported correct by ifconfig.
* The network parameters shown by NM for eth0 are funny: the address is
OK and the setting is reported "manual", which is right, but no DNS
entry is shown, and the mask is set to "24" instead of "192.168.0.255"
as shown by ifconfig.
* Edition of these parameters in NM fails after the "accept" button with the
message dialog:
"failed updating connection: nm-ifupdown-connection.c:82 - connection update
not supported (read only).."
- ** NETWORK MANAGER HAS WIPED OUT RESOLV.CONF
+ ** NETWORK MANAGER HAS WIPED OUT RESOLV.CONF
* resolv.conf has been wiped out, and now only contains the message "#
Generated by NetworkManager". Adding the line "nameserver 192.168.0.1"
makes the web visible again, although NetworkManager still show the
network as unavailable.
** WIRELESS IS CONFIGURED OK, BUT WORKS EXXXTTTRRREEEMMMLLLYYY
- SLOWLY
+ SLOWLY
* If wireless is activated, a link is established with the router, and
resolv.conf is wiped again and replaced with something that looks like:
#Generated by NetworkManager
domain home
search home
nameserver 192.168.0.1
* NetworkManager now reports the network as available, but it does not
work right. A ping to a web address (say google.com) takes about 5
seconds to start, although then it proceeds at the normal rate and with
normal ping times. Pinging the resolved address is no faster. Web pages
take ages to load or more typically time out. apt-get update takes more
than an hour.
- An internal ping to my network is instantaneous.
+ An internal ping to my internal network is instantaneous.
Going back to wired blanks resolv.conf again.
** THERE MAY BE MORE THAN ONE PROBLEM. UNINSTALLING NM DOES NOT FIX IT
+
* uninstalling NM, wiping its traces and reinstalling does not fix the
- problem. (maybe there are more traces left than I wiped out)
+ problem. (maybe there are more traces left than I wiped out). Totally
+ uninstalling NM and
