Should be fixed in Ubuntu 12.04.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320268
Title:
Wired network does not
after a last hal/network-manager update wired network does work again on dell
mini9 / 2.6.27-11
but now wireless is not present anymore..aarrgh
--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a member
Anton,
You are 100% correct I apologize. However, I think you may have
discovered something. Below is my original dhclient.conf file. Everything
except the send host-name and the request is commented out. I put the
erroneous supersede command "before" the send host-name which I think would
ah, it seems it doesn't like the option in the dhclient.conf:
sudo dhclient
/etc/dhcp3/dhclient.conf line 53: no option named nameserver in space dhcp
supersede nameserver 192.
^
/etc/dhcp3/dhclient.conf line 53: semicolon expected.
^
but i did like described, i added the line
superse
nothing changed. here is some part of my daemon.log:
Feb 4 18:34:02 mini NetworkManager: DHCP: device eth0 state changed
(null) -> preinit
Feb 4 18:34:02 mini NetworkManager: (eth1): supplicant interface state
change: 1 -> 2.
Feb 4 18:34:02 mini dhclient: Listening on LPF/eth0/00:21:70:
but my router is on 192.168.1.1, i will put this in and reboot.
--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I think maybe you and Anton have a different problem. I am using a wired
connection and my server never crashed it just did not connect to the
network. The supersede nameserver definately fixed the problem. I tried it
with and without it several times and it always worked with it and never
w
Anton,
Did you reboot after adding the supersede comand? It does not take effect
until the network is restarted or the system is rebooted. I found a reboot
was easier... In your case the suersede command should be: supersede
nameserver 192.168.0.1 (Do not put quotes around the IP address!
well, unfortunately I don't even have the old kernel. I was using wireless and
after deciding that the new kernel seems stable I removed the old one. then I
went home, connected to my wired network and vola nothing. I can't get it
to see my router or get any IP from eth0.
I searched around
I did the "supersede nameserver 192.168.2.1" thing but to no avail (that
is the correct gateway for me too).
The only workaround for me right now is booting into the previous kernel
(-9). This is especially frustrating for me as wireless crashes the
entire machine every few hours. Useless. Fed
it says
nameserver "192.168.0.1" although my router is on 192.168.1.1
my dhclient.conf is empty, meaning everything is commented out.
--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a member of Ubuntu
Anton,
I don't know if switching the Kernel is a good idea or not. (I would
guess not.) It would be very interesting to check the /var/log/daemon.log
file to see if you have the same before and after differences I found.
(Search the file for the word namerserver.) If you do, you might try
hi, I'm using a dell netbook (911 first edition) dual boot xp & 8.10.
since I upgraded to the latest kernel delivered automatically through software
update I can no longer connect to my wired connection AT ALL. It's exactly like
described above, ONLY I got a LinkSys Router. Windows can connect, L
Hang on, so all 3 of us are using a belkin router then... ?
Interesting...
--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
This happened to me when I upgraded a completely patched and working 8.04
installation to 8.10 I had no problem with 8.04 and have installed it on
three different machines. I also installed 8.10 from scratch and had the
same problem. I am using a wired network through a Belkin router to a cab
Sorry, let me be much clearer about this. The problem came with an
upgrade to the latest kernel or something that was updated with it. Its
not a difference between 8.04 and 8.10 as my 8.10 was working just fine
until this morning.
--
Wired network does not work after 8.10 upgrade
https://bugs.l
I confirm it!
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
+1 - same thing happens to me with the latest version of the kernel in
8.10. I'm on recommended updates only and my wired networking only
failed when I got the latest updates today. My 8.10 was working
previously.
What happens is that it tries to connect (whether there is actually a
cable in th
Jerry
- Original Message -
From: "Colin Watson"
To:
Sent: Tuesday, January 27, 2009 1:09 PM
Subject: [Bug 320268] Re: Wired network does not work after 8.10 upgrade
I don't know where this really belongs, but choose-mirror definitely
isn't it - that's a component of
I don't know where this really belongs, but choose-mirror definitely
isn't it - that's a component of the installer that deals with mirror
selection. Reassigning to network-manager for further analysis.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: choose-mirror => network-manager
--
20 matches
Mail list logo
