One problem as I see it is that the Network Manager applets/widgets
should have a simple option to changed "unmanaged" devices to "managed."
All it takes is for a "managed=true" line in nm-settings.conf to be
changed to "managed=false" and Network Manager is stuck! The only way
to fix it is to fix
Just a quick bit of info as I saw a similar problem...which may or may
not have been related on 9.10.
The problem as I see it was caused by have a static ip setup on eth0 -
but the network manager was 'swiping' the connection and attempting dhcp
(which is not available on the particular network).
I too have a static IP address config and got hit by this problem
attempting to upgrade from 8.04 to 9.04 (via 8.10). So I wiped and did
a clean install of 9.04 and static IP configuration then worked fine.
Not a fix for those that want to upgrade though.
--
[regression] devices/interfaces not s
I upgraded to Jaunty final release and the bug still persist. is someone
working at this or like in intrepid the bug will persist until the next
release.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (har
Really the easiest way is to just do a ip address reservation for your
NIC's MAC address on your DHCP server. That way when this long drawn
out bug is finally fixed, you won't have to do any special re-config
of anything.
On Thu, Dec 4, 2008 at 9:14 AM, Alexander Sack wrote:
> On Sat, Nov 08, 200
I upgraded from 8.10 to 9.04 beta and network worked but plasma-network-widget
showed unmanaged, I thought beacues ia had handly modified interfaces and
resolv.conf.
I decided to installa fresh 9.04 due the fact I was upgrading from a long time.
I was very disappointd to see netork work via dhcp
Those who need a static ip
Change your /etc/resolv.conf to something like below (replace the x's with ip
addresses of your dns servers)
with the command:
sudo gedit /etc/resolv.conf
#/etc/resolv.conf
search yourdomain
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.x
On Sat, Nov 08, 2008 at 07:44:40PM -, Dave Jakeman wrote:
> Just back from wiping/installing 8.10 (full) and trying to set up my
> static wired connections.
>
> On the first attempt, I configured my connections and they were accepted
> without a "read-only" error. Couldn't get onto the intern
Thanks Sokraates!
(https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/279262/comments/20)
Worked like a charm!
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.la
Network Manager is getting wirse. It now randomly does things like:
offering a wireless connection when there is a wired connection (both defined
as dhcp)
after requesting a WPA/WPA2 key, never connecting
ignoring DNS (in /etc/resolv.conf) but not allowing them in Network Manager
applet
not picki
After successful connection, is anyone else here having windows based
pptp vpn connection issues?
Is there a specific thread for this issue in Ibex?
Sorry if this is outside the realm of this thread.
-Brian
On Mon, 2008-11-10 at 14:53 +, Paul wrote:
> Yes Martin, I did. The work-around ab
Yes Martin, I did. The work-around above of deleting the existing
connection and re-adding didn't work either as Network-Manager still
wouldn't allow me to add a connection (no prompt for sudo access). The
only fix that works is to manually edit /etc/resolv.conf to add DNS
entries. Wicd nicely m
Paul, you didn't look at the gui for network manager very closely, did you?
Network manager does write to resolv.conf.
This is how you set up for a static IP connection:
Right click the icon, select "edit connections", highlight the connection you
want to tweak. Click Edit and then select th
The work around for this is easy. Simply edit /etc/resolv.conf so your
DNS lookup server is present. Check it out...
$ cat /etc/resolv.conf
# Generated by NetworkManager
OH LOOK IT'S BLANK. :/ I guess let's add our DNS server in /etc/resolv.conf:
$ sudo vi /etc/resolv.conf
$ cat /etc/resolv
Just back from wiping/installing 8.10 (full) and trying to set up my
static wired connections.
On the first attempt, I configured my connections and they were accepted
without a "read-only" error. Couldn't get onto the internet though.
Went back to check, and both connection definitions had vanis
Me too. I had two static wired interfaces before the upgrade. Tried
upgrading by CD and over the net and both made my post-upgrade
connections incorrectly configured and read-only. Fortunately, I took
an Acronis backup before the upgrade. I have other issues (PC hangs on
shutdown), so I'll try
Exact same problem here. Static IP config that worked fine in 8.04,
borked when 8.10 upgrade came. Can't alter using NM gui (no password
prompt - says I don't have permission). Connectivity to ISP is fine,
but DNS doesn't work.
Example:
$ ping google.com
ping: unknown host google.com
$ ping 6
Yes, it works fine.
I can configure it from the networkmanager applet.
Give it a try.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received
@NUCO
Can you use a static IP through eth0 with your new "interfaces"
configuration? This is my problem. DHCP works but not static IP.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
htt
This is my old "interfaces" configuration, the one that was left after
the upgrade to ibex:
auto lo
iface lo inet loopback
auto eth2
#iface eth2 inet dhcp
auto ath0
#iface ath0 inet dhcp
auto wlan0
#iface wlan0 inet dhcp
iface eth0 inet static
address 192.168
Do you mean removing eth0? My internet connection has always worked;
however, I've never had the nm-applet running in the notification area.
The only way to make it show up is to run command
"sudo /etc/init.d/NetworkManager restart". This puts the network manager
in the notification area although i
Do you mean removing eth0? My internet connection has always worked;
however, I've never had the nm-applet running in the notification area.
The only way to make it show up is to run command
"sudo /etc/init.d/NetworkManager restart". This puts the network manager
in the notification area although i
@Sergiu
Did you try removing the existing connection entry and create a brand
new one?
This worked for me. NM prompted me for the password and the new
connection is now persistent (i.e. is not lost on reboot)
Claudio
Il giorno 06/nov/08, alle ore 11:02, Sergiu Bivol ha scritto:
> Three mac
Three machines with Intrepid here. All of them fresh installs, updated. Each of
them has 3 network cards with static IPs.
None of them is manageable.
I randomly get any combination of these results when configuring the interfaces
with network manager:
- the settings are saved, but no connection
I think I have this bug as well. I upgraded from 8.04 to 8.10. I had a
static IP wired connection under 8.04 which worked but this stopped
working after upgrading to 8.10.
I followed advice from messages above and set
[ifupdown]
managed=true
In my /etc/NetworkManager/nm-system-settings.conf file
please double check that this bug is actually your bug and if you are in
doubt open a new one. refer to this one instead of commenting here.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before
mauriceplus, this is not the place to ask question. questions here will
make the bug unreadable and make it less likely that we can actually fix
something here.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0
This bug unavoidably impacts anybody using VirtualBox to run guest VMs
under Ubtuntu with Host Interface Networking (i.e. "real" networking),
since this calls for the installation of bridge-utils and modification
of /etc/network/interfaces with the addition of code like:
auto br0
iface br0 inet dh
mauriceplus: That also happened to me a few times. For example when I
bought a wlan router and tried to make it work. Nothing but skype
works.. Strange.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hard
HI, I'm using Kubuntu 8.10, upgraded from 8.04.
I want to confirm this bug, but I've experienced an interesting thing!!
Skype works fine, I can talk with anyone, but I can't surf on internet with
firefox and other programs, and apt-get doesn't work!!
but WHY Skype WORKS???
Thanks a lot to all tha
wont fix in intrepid.
** Changed in: network-manager (Ubuntu Intrepid)
Status: Triaged => Won't Fix
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs
On Mon, Nov 03, 2008 at 03:50:57PM -, Martin G Miller wrote:
> I think this is a different bug(s). I will start a new one for it.
ok if that is because you see the devices duplicated its bug 262974
... but i think you found it.
- Alexander
--
[regression] devices/interfaces not set to "a
"so its a feature that they get reused for multiple devices." If I only
have 1 nic and 1 connection type specified, there should only be 1 entry
in the drop down list. I have another machine running Intrepid from a
clean install of rc1 and it has 2 nics in it. The drop down correctly
shows 2 ent
sorry meant: ... that your description matches this bug ...
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received this bug notification becau
Martin, i dont think that your description is your bug. Anyway, the
connections are not bound to a physical device unless you lock them by
setting the HW address (MAC). so its a feature that they get reused for
multiple devices.
--
[regression] devices/interfaces not set to "auto" in /etc/network
Here is some follow up. After a reboot, I have the network manager
applet in the tray and it works, sort of. It was showing my DHCP entry
and my static IP entry twice.
It also kept defaulting to the Auto eth0 connection which is DHCP, even
though I had unchecked "connect automatically" for that
Here is the output you requested:
[EMAIL PROTECTED]:~$ ls -la /etc/network/interfaces*
-rw-r--r-- 1 root root 325 2008-10-31 07:53 /etc/network/interfaces
-rw-r--r-- 1 root root 537 2008-10-30 20:35 /etc/network/interfaces~
-rw-r--r-- 1 root root 496 2006-04-19 11:49 /etc/network/interfaces.dpkg-o
On Fri, Oct 31, 2008 at 11:51:46AM -, Martin G Miller wrote:
> I had only 1 nic defilned in Hardy with choices of a static IP address
> and DHCP, set up with the old network manager. Here is the contents of
> interfaces.dpkg-old, which I assume is my old interfaces file. There
> are no blank
I had only 1 nic defilned in Hardy with choices of a static IP address
and DHCP, set up with the old network manager. Here is the contents of
interfaces.dpkg-old, which I assume is my old interfaces file. There
are no blank lines and only 1 static IP nic is listed.
# This file describes the netw
i am not aware of any code that would touch /etc/network/interfaces
during hardy->intrepid update. How sure are you that you did not have
those empty lines before?
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed i
On Thu, Oct 30, 2008 at 12:32:57PM -, jOin3r wrote:
> Workaround is to remove network interface from
> /etc/udev/rules.d/70-persistent-net.rules
> and remove the interface from /etc/network/interfaces
why remove from persistent-net.rules? removing just from interfaces
should be enough.
- A
It didn't show clearly in my previous post.
here is what it looked like starting with what should have been the last
2 lines of the file:
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
The blank lines started here. There wer
Here is an update. I reexamined my /etc/network/interfaces and I found
a lot of blank lines that obscured the "phantom eth1 info"
***The file contents starts here
# This file describes the network interfaces available on your system
# and how to activate them.
Workaround is to remove network interface from
/etc/udev/rules.d/70-persistent-net.rules
and remove the interface from /etc/network/interfaces
Reboot and enjoy network manager.
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but
Here is my syslog from today.
** Attachment added: "syslog.txt"
http://launchpadlibrarian.net/19055066/syslog.txt
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpa
On Wed, Oct 29, 2008 at 03:18:22PM -, Martin G Miller wrote:
> Since upgrading from hardy to Intrepid I have a similar issue. I had
> set Hardy up with static IP and on upgrade to Intrepid, I have no nm-
> applet I am online, but can't manage my nic. It gives me the read
> only message ment
Since upgrading from hardy to Intrepid I have a similar issue. I had
set Hardy up with static IP and on upgrade to Intrepid, I have no nm-
applet I am online, but can't manage my nic. It gives me the read
only message mentioned above. Oddly, the Network Configuration shows I
have 2 nics, eth0
On Tue, Oct 28, 2008 at 11:02:11AM -, aussiebuddha wrote:
> I quotes the iface line for eth0 and now it works miraculously.
> hope a fix gets there before intrepid is out.
>
> laptop:~$ cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
> auto eth0
> #iface eth0 inet dhcp
>
thats
I quotes the iface line for eth0 and now it works miraculously.
hope a fix gets there before intrepid is out.
laptop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
#iface eth0 inet dhcp
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get
Thanks for the cogent summary, Alexander.
Questions:
- Is a fix available? (Can you post it to the bug?)
- Under what circumstances will a user have an /etc/network/interfaces with no
'auto' lines like this, that they want NM to manage? Will a user ever have
such a config as a result of Ubuntu
** Changed in: network-manager (Ubuntu Intrepid)
Target: ubuntu-8.10 => None
--
[regression] devices/interfaces not set to "auto" in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received thi
** Description changed:
the regression here is that devices are unmanaged even though they dont
have a "auto eth0" line in /etc/network/interfaces
Here an example of an interfaces configuration that should not set the
devices in unmanaged mode
https://bugs.edge.launchpad.net/ubuntu/+s
ubuntu-release: please decide whether we can get this this in intrepid.
** Description changed:
the regression here is that devices are unmanaged even though they dont
have a "auto eth0" line in /etc/network/interfaces
Here an example of an interfaces configuration that should not set th
** Description changed:
the regression here is that devices are unmanaged even though they dont
have a "auto eth0" line in /etc/network/interfaces
Here an example of an interfaces configuration that should not set the
devices in unmanaged mode
https://bugs.edge.launchpad.net/ubuntu/+s
54 matches
Mail list logo
