** Changed in: network-manager
Importance: Unknown = Medium
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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).
** Tags added: iso-testing
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: network-manager
Status: Fix Released = Fix Committed
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: network-manager
Status: Fix Committed = Fix Released
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm somewhat confused from above connections. I have similar need to
that of Martin Jackson's. That is I would like network manager to
automatically connect to say wlan0, but on the same time, it would let
me do what ever I want on eth0. (It could just the same be other way
around).
Rationale is
I finally got a static IP to work using the Network Manager.
I had to do the following.
Set my /etc/network/interfaces as follows:
___ /etc/network/interfaces ___
# The loopback network interface
auto lo
iface lo inet loopback
# Wireless interface
auto wlan0
#iface wlan0
Using Ubuntu 8.10 amd64, updated from RC
I was able to setup VirtualBox Host Networking with this tutorial here:
https://help.ubuntu.com/community/VirtualBox#Networking
However, after using the system for a few days, I noticed instances
where the system would lose all connectivity and would not
@jokker :
As one of the early testers for intrepid, this was well tested. Had you
read through this bug, you already know that.
If you are on a server, it does not use a gui, thus does not use network
manager.
Most individuals working on Ubuntu are volunteers.
¨I can't get this to work.¨
correct, server + NM is currently a no go and the ubuntu server edition
definitly doesnt install NM by default.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No I use a desktop edition as a server, because I need it as a station too. It
worked like this for years, that an old dual athlon MP server. So no, I do not
use server edition, I have the GUI, it is just on 24/7 on a ups...
Here is my problem:
I installed cleanly a brand new intrepid by keeping
I'm having a similar problem.
I ran an upgrade from an 8.04 install, and lost network connectivity. I
tried fighting with it for a few hours and decided it would be less work
to just reinstall the system with the new OS. After the reinstall I
found that my system would not maintain the Static IP
It is not even similar, it is the same story... I forgot to mention that
I first upgraded from hardy... Seeing that I could not get the network
right and discovering that some people o the web had the same issue from
upgrading, I decided to reinstall the whole thing be keeping my $home,
but it is
jokker, dont add more info to this bug please. open a new one for your
particular issue and just mention in that bug that you think that it
belongs here. thanks a bunch!
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug
the same for anyone who feels like posting here is the right thing ;)
** Description changed:
+
+ NOTE: Instead of adding more information here, please open a new bug for your
particular issue and mention that you think that this bugs is related. Thanks!
+
+
The NetworkManager 0.7 preview
I can't get this to work. I am really upset, pissed off.. EVERYTHING! All my
ftp, apache, ssh, samba, cups servers and VPN are down PLEASE someone fix
this mess ! People like me can't afford to stay with dhcp on a server
Is there someone working on this already? Who is responsible for
Same here - no way to make it work :( The network manager always knows
better... :(
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Tue, Oct 28, 2008 at 09:20:29PM -, Filipe Sousa wrote:
Now I have the new connection renamed, but after a reboot I have the
connection that I renamed and Auto eth0. The Auto eth0 is the
default with dhcp :( Removing Auto eth0 doesn't work.
Well ... usually NM doesnt add a auto
On Wed, Oct 29, 2008 at 10:00:46AM -, kszys wrote:
Same here - no way to make it work :( The network manager always knows
better... :(
Could you please not put comments without any content in bug
reports. that makes the bugs unreadable and will make things become
even worse (e.g. nobody
I can't see anymore the NM icon on gnome-panel, but I see
NetworkManager running, did I turned off something? or is this normal?.
:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.1.6
netmask 255.255.255.0
gateway 192.168.1.1
:~$
Vladimir Durán
Did the notification area get accidentally removed from your panel?
Right click the panel Add applet(item?) scroll way down and add the
notification bar to your panel. See if that helps you out. :)
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
On Wed, Oct 29, 2008 at 12:53:30PM -, Vladimir Durán wrote:
I can't see anymore the NM icon on gnome-panel, but I see
NetworkManager running, did I turned off something? or is this normal?.
Thats normal. It is currently discussed in bug 289466 ... please
subscribe and lets continue
Nop :(, I have it visible (I use it a lot :) ). I have notification
area applet version 2.24.1 if it matters.
gnome-applets: 2.24.1-0ubuntu1
I see running:
/usr/sbin/NetworkManager
/usr/sbin/nm-system-settings --config
/etc/NetworkManager/nm-system-settings.conf
nm-applet --sm-disable
I did: $
Oh sorry Alexander Sack, I'll subscribe to that; if anybody can/wants to
delete my message go ahead.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Mon, Oct 27, 2008 at 10:05:06PM -, Filipe Sousa wrote:
I have both Connect automatically and System setting enabled.
If I rename the connection name from Auto eth0 to something else
doesn't work as after a reboot the connection name defaults to Auto eth0
$ groups
fsousa adm cdrom
Now I have the new connection renamed, but after a reboot I have the
connection that I renamed and Auto eth0. The Auto eth0 is the
default with dhcp :( Removing Auto eth0 doesn't work.
I'm giving up, it's easier to set up the network using the old
/etc/network/interfaces
--
[intrepid] new 0.7
On Thu, Oct 23, 2008 at 06:16:13PM -, Julien Aubin wrote:
Does not fix the issue for me.
A work around consists in rewriting the /etc/resolv.conf file.
Sorry, what exactly does not work for you?
- Alexander
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
On Fri, Oct 24, 2008 at 10:32:28PM -, Filipe Sousa wrote:
I have the same problem. After every reboot I have to setup the static
IP address in network manager applet. It's very annoying
Did you try to rename the (auto) connection or create a new one and
set that to auto connect?
Do you
I have both Connect automatically and System setting enabled.
If I rename the connection name from Auto eth0 to something else
doesn't work as after a reboot the connection name defaults to Auto eth0
$ groups
fsousa adm cdrom audio plugdev fuse lpadmin admin sambashare
** Attachment added:
I have the same problem. After every reboot I have to setup the static
IP address in network manager applet. It's very annoying
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
$ cat /etc/NetworkManager/nm-system-settings.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
Does not fix the issue for me.
A work around consists in rewriting the /etc/resolv.conf file.
Content of my /etc/network/interfaces file
-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see
Don't know how the duplicates are handled, but everything I reported in:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/270762
: works for me now.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug
hello,
a week ago I have upgraded my Hardy to Intrepid beta on 3 machines. the
oldest one is still with Intrepid but two new had to be downgraded to
Hardy since network did not work.
is it safe now to upgrade them to Intrepid beta or should I wait for
official release?
(I've posted the same
On Mon, Oct 13, 2008 at 08:33:46AM -, Richard Rickwood wrote:
Had I been able to simply set my static settings in the NM GUI
(including the DNS Server) without the afrementioned 'read-only' error
(what's that all about?), I would have been fine and would not have had
to boot into Windows
On Mon, Oct 13, 2008 at 08:51:50AM -, Richard Rickwood wrote:
Maybe my issue is related to this bug:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/281984
Looks like the reporter of that bug was as miffed as I was to suddenly
have their networking break.
Should I file a new
Maybe my issue is related to this bug:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/281984
Looks like the reporter of that bug was as miffed as I was to suddenly
have their networking break.
Should I file a new bug regarding the 'read-only' issue?
--
[intrepid] new 0.7 branch
I was aware that managed mode was not the default. I only changed to
managed mode because an update to NM (around about the 8th October)
stopped my internet connection working, and I was trying lots of things
to get it working again. Launching Firefox I found that offline mode was
checked (I had
Hi, I'm also having problems where my ethp0 is unmanaged.
Any idea what can I do, I've updated to the latest patches but still have
problems.
Here are my files:
laptop:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:41:e6:65:23
inet addr:192.168.1.2
After updating today:
:~$ apt-cache policy network-manager
network-manager:
Instalados: 0.7~~svn20081008t224042-0ubuntu2
Candidato: 0.7~~svn20081008t224042-0ubuntu2
Tabla de versión:
*** 0.7~~svn20081008t224042-0ubuntu2 0
500 http://sv.archive.ubuntu.com intrepid/main Packages
Why is the upstream bug set to #548114? There's little, if any,
relevance.
What is this dns-nameservers entry? As far as I can tell it's not
documented in interfaces(5). Is it some made up thing just for the
network manager ifupdown plugin? Alex, you realized that approximately
zero machines out
Also, should https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/255839 be reopened? system setting, as Richard pointed out,
doesn't work
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you
FWIW, dns-nameservers comes from the resolvconf package.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have a bridge device in my (attached) Interfaces file, for any VMs I
may run; this bridge device uses dnsmasq to serve up dns and dhcp, for
NAT. However, with the latest few versions of NetworkManager...
NetworkManager seems to try to connect as a _client_ on that
interface... which I am the
I think I reported a side effect of this fix. An upgrade from a perfectly
normal and fresh Hardy installation results in having eth0 unmanaged. Why a
*managed* network must become unmanaged by virtue of an upgrade?
By the way, KNetworkManager ignores not only Interfaces, but itself! There is
no
@Alexander Sack: Just to make it clear: I was running with the default
configuration as far as /etc/network/interfaces and /etc/NetworkManager
/nm-system-settings.conf is concerned.
The latter file looks like this:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
As far as I can tell,
Alexander, please let's make this clearer.
Previously static configuration was achieved by setting address,
netmask, network, broadcast and gateway in /etc/network/interfaces and
DNS servers where specified as nameserver in /etc/resolv.conf.
My networking was effectively 'broken' for the last
Richard, managed mode is not yet enabled by default. If you dont want
resolv.conf to be overwritten you have to use unmanaged mode and
configure all your devices in /etc/network/interfaces.
The bug about unmanaged mode that you appear to be offline all the
time is a bug that will be fixed for
On Tue, Oct 07, 2008 at 09:40:56PM -, Rick Allard wrote:
I made some changes a few weeks ago to get my (now) Ubuntu 8.04.1
(/etc/issue) going with a WPA access point. (That was a horrid
struggle.) I've been through some automatic updates since then including
one this morning after which
I upgraded from 8.04 to Intrepid this morning. No way to make NM work.
I tried all the hints above, none solved. I had problems both with NM and
/etc/network/interfaces interaction, and /etc/resolv.conf.
Disabling a (static) eth0 from interfaces, made NM work, except no resolver
could be used, I
On Thu, Oct 09, 2008 at 11:46:57AM -, cangia wrote:
I upgraded from 8.04 to Intrepid this morning. No way to make NM work.
I tried all the hints above, none solved. I had problems both with NM and
/etc/network/interfaces interaction, and /etc/resolv.conf.
Disabling a (static) eth0 from
On Tue, Oct 07, 2008 at 09:47:37PM -, Sokraates wrote:
Same problem here (Kubuntu Intrepid), though I found a different
solution: I commented out the iface XXX inet dhcp-lines and now NM
works like a charm again.
Yes, I if you have configurations in /etc/network/interfaces and dont
want NM
Thank you Rick Allard for comment #38, Firefox was driving me crazy with
goin offline each time.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
When I change in /etc/NetworkManager/nm-system-settings.conf:
from
[ifupdown]
managed=false
to
ifupdown]
managed=true
NM, after reboot show:
eth0 interface (this is O.K. - I have static config), and
ifupdown (eth0) interface ??? (not active, I can't delete this interface)
--
[intrepid]
Perhaps I'm missing the point here but it seems you have altered the network
manager applet to NOT manage the networks??
I have a static network here and this broke it totally.
As of today NetworkManager is unusable for me using any of the suggestions here.
Perhaps this helps for some thing
Since I'm upgrading from Hardy, it's not clear to me what is the currently
default for
/etc/network/interfaces
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Tue, Oct 07, 2008 at 10:20:03AM -, Ivan Nemet wrote:
Hi Alexander,
Sorry for my english
I use Ubuntu 8.04 and this source for update NM:
deb http://ppa.launchpad.net/network-manager/ubuntu hardy main
deb-src http://ppa.launchpad.net/network-manager/ubuntu hardy
Ivan, ifupdown (eth0) is the configuration your have in
/etc/network/interfaces. by turning on managed=true you opted-in to get
that system connection presented. If you dont want it to appear at all,
you can remove it from /etc/network/interfaces .. or just use it as it
should contain the static
Malac, please open a bug and give detailed information about your setup.
Attach your /etc/network/interfaces and your complete /var/log/syslog to
that bug.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification
Hi Alexander,
Sorry for my english
I use Ubuntu 8.04 and this source for update NM:
deb http://ppa.launchpad.net/network-manager/ubuntu hardy main
deb-src http://ppa.launchpad.net/network-manager/ubuntu hardy main
After todate update NM my network connection is broken. and
Same problem here (Kubuntu Intrepid), though I found a different
solution: I commented out the iface XXX inet dhcp-lines and now NM
works like a charm again.
Here's my /etc/network/interfaces, just to make it clear, what I mean:
# This file describes the network interfaces available on your
I made some changes a few weeks ago to get my (now) Ubuntu 8.04.1
(/etc/issue) going with a WPA access point. (That was a horrid
struggle.) I've been through some automatic updates since then including
one this morning after which Firefox seemed to stick with Work Offline
checked (even in a brand
This bug was fixed in the package network-manager -
0.7~~svn20081004t225044-0ubuntu1
---
network-manager (0.7~~svn20081004t225044-0ubuntu1) intrepid; urgency=low
new upstream snapshot: Sat 2008-10-04 22:50:44 (bzrrev 3602) from
lp:~vcs-imports/network-manager/main branch
*
fix committed to branch: https://code.edge.launchpad.net/~network-
manager/network-manager/ubuntu.0.7
** Changed in: network-manager (Ubuntu Intrepid)
Status: Triaged = Fix Committed
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You
I've just upgrade to network manager 0.7~~svn20081004t225044-0ubuntu1 version,
and still not working here.
I am not an expert so maybe i am missing something!... i looked into my
/etc/modprobe.d/blacklist file and i am sure e1000e is not there..
And i configure my network card with static IP but
On Mon, Oct 06, 2008 at 07:30:05PM -, cman wrote:
I've just upgrade to network manager 0.7~~svn20081004t225044-0ubuntu1
version, and still not working here.
I am not an expert so maybe i am missing something!... i looked into my
/etc/modprobe.d/blacklist file and i am sure e1000e is not
https://bugs.launchpad.net/ubuntu/+bug/279262
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi,
Anyway, the current default configuration shipped is:
/etc/NetworkManager/nm-system-settings.conf:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
Please ensure that your file looks similar to that and that you have
everything restarted (e.g. reboot).
If your
** Changed in: network-manager
Status: Confirmed = Fix Released
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On Fri, Sep 26, 2008 at 04:44:11PM -, Kees Cook wrote:
Will the ifupdown plugin get added to the list by default before
Intrepid releases?
Yes. I am making this Release-Fit right now. Hope to get this upstream
and into our archive by monday.
- Alexander
--
[intrepid] new 0.7 branch
On Sat, Sep 27, 2008 at 12:16:04AM -, Roland Dreier wrote:
I have a system connected to a wired network that requires a static IP
and 802.1x authentication, and I have an /etc/network/interfaces stanza
like
auto eth1
iface eth1 inet static
address 10.33.42.9
netmask
Ok. A quick heads up on what is planned. Please comment in case you
think it won't fit your need.
We will introduce a new config for /etc/NetworkManager/nm-system-settings.conf
that reads like:
[ifupdown]
managed=true/false
The default will be false for intrepid and depending on how well it
I can't get my internet working, i've tried the suggestion above to no help.
all i have is a loopback interface.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which
I am hitting the same issue, I use bridging with VirtualBox, I can't
have NetworkManager manage any interfaces listed in
/etc/network/interfaces. NetworkManager's old behavior was perfect. (I
don't have VirtualBox running yet because networking is all confused on
my test box ...)
--
[intrepid]
Jeremy, plesae post your interfaces file. Thanks!
** Changed in: network-manager (Ubuntu Intrepid)
Target: ubuntu-8.10-beta = ubuntu-8.10
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are
** Description changed:
- nm 0.7 branch is ignoring /etc/network/interfaces
+ The NetworkManager 0.7 preview shipped in the ubuntu 8.10 beta release does
+ not yet have a feature to unmanage devices configured in
/etc/network/interfaces.
+
+ Affected:
+ Users that have their network devices
I list eth0 1 as inet manual so that NetworkManager doesn't touch
them. It works very well with Hardy.
/etc/network/interfaces __
auto lo
iface lo inet loopback
# auto eth0
# iface eth0 inet static
# address 172.19.0.4
# netmask 255.255.0.0
#
Roland, thats an interesting configuration. have you tried to configure
the same in NM connnection editor as a system connection? for that
create a new wired connection and configure in the 802.1x security tab.
Remember to comment the complete stanza so ifupdown doesnt interfere.
--
[intrepid]
This bug may be a duplicate of bug #5364.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
- Binary package hint: network-manager
-
nm 0.7 branch is ignoring /etc/network/interfaces
Its ignoring my static IP settings and defaulting to dhcp. I can bypass
nm with the /etc/init.d/networking script.
See also:
Will the ifupdown plugin get added to the list by default before
Intrepid releases?
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Or there should be a button in NM interface to turn it on/off.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I have a system connected to a wired network that requires a static IP
and 802.1x authentication, and I have an /etc/network/interfaces stanza
like
auto eth1
iface eth1 inet static
address 10.33.42.9
netmask 255.255.255.0
gateway 10.33.42.1
wpa-driver wired
wpa-ap-scan 0
Hi, Alexander,
appending ,ifupdown to the plugins= line in
/etc/NetworkManager/nm-system-settings.conf works for me, making NM honor again
my /etc/network/interfaces file. NM, however, still erases my resolv.conf after
every boot, as per bug #259539.
--
[intrepid] new 0.7 branch ignores
Thank you, Alexander
I did a new installation of Xubuntu Intrepid 8.10 using the desktop CD.
Even though Network Manager still won't allow me to make any changes,
after following your suggestion and making the changes manually to
/etc/network/interfaces, I was able to connect. I am using static
I confirm this issue on a dist-upgrade from Hardy to Intrepid today.
I would appreciate if Ubuntu keeps a straightforward mechanism to edit
config file(s) (preferably /etc/network/interfaces, as it's extremely
well-understood and functional) and have network-manager honor them by
ignoring the
I'm willing to add confirmed here, too. I filed another report on this,
and the answer appears to be to unstall Network Manager. After doing
that, I can get online with my static IP address. It's working so far.
This after using static IP since Ubuntu 5.10.
I removed all four files after
On Tue, Sep 23, 2008 at 12:14:02AM -, Charlie Kravetz wrote:
I'm willing to add confirmed here, too. I filed another report on this,
and the answer appears to be to unstall Network Manager. After doing
that, I can get online with my static IP address. It's working so far.
This after
Confirmed. I had a machine go offline saturday because it went dhcp-hunting
instead of using the static IP (upgraded on friday). Highly annoying since I
was 300km away at that time and really didn't expect that behaviour, so I
couldn't find it... :p
(Yes, I've done the Right Thing now and added
** Tags added: regression-potential
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same problem here. However I have to rmmod ndiswrapper, modprobe ndiswrapper
and /etc/init.d/networking restart for the Wifi to work. Just doing the network
restart doesn't solve the problem.
Running:
[EMAIL PROTECTED]:~/network-manager-bug$ dpkg -l | grep network-manager
ii network-manager
moving to beta. to keep this off from release team radar for alpha-6
** Changed in: network-manager (Ubuntu Intrepid)
Target: intrepid-alpha-6 = ubuntu-8.10-beta
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug
system-settings will work even without X running. so thats not an
argument. not sure what you want to do with remote ssh.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
** Changed in: network-manager
Status: Invalid = Confirmed
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: network-manager
Status: New = Invalid
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #544069
http://bugzilla.gnome.org/show_bug.cgi?id=544069
** Also affects: network-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=544069
Importance: Unknown
Status: Unknown
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
** Changed in: network-manager
Status: Unknown = New
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
i linked the branch where i develop the eni/ifupdown system config
plugin to this bug.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this is known.
Depending on how stable the ifupdown/eni system setting plugin becomes
we will either:
1. make the ifupdown/eni system config plugin blacklist interfaces configured
there
2. conflict with ifupdown and instead support old configurations as good as
possible through the
Pardon me if I misinterpreted your comment:
I hope that cli/conf files won't be abandoned. The 2 should be able to
coexist and honor each others settings.
Regardless of preference: cli utils are needed in lack of X for numerous
occasions including... remote ssh, no X (ubuntu-server installs),
99 matches
Mail list logo
