*** This bug is a duplicate of bug 139403 ***
https://bugs.launchpad.net/bugs/139403
fwiw,
blacklisting auto dhcp interfaces from being nm managed (which should fix this
bug) is now tracked in bug 139403 ...
** This bug has been marked a duplicate of bug 139403
network-manager should stop
On Sat, Sep 01, 2007 at 09:28:29PM -, Luka Renko wrote:
> I understand that n-m 0.6.x is very limited by design: only manages one
> connection at the time, no support for static IP config and per-user
> configuration only. This is why I think it has primary use only for desktop
> users with
I understand that n-m 0.6.x is very limited by design: only manages one
connection at the time, no support for static IP config and per-user
configuration only. This is why I think it has primary use only for desktop
users with simple setup, which more or less means one active connection. I
thi
On Fri, Aug 31, 2007 at 03:20:33PM -, Luka Renko wrote:
> Christian, I cannot agree with your assessment, particularly as
> GNOME/KDE tools by default write interface with auto + dhcp in the
> interfaces file and as this was the setting on previous Ubuntu releases
> that were supposed to work w
You are right, Luka, that it will cause problems if GNOME/KDE write such
default values.
I've installed my laptop during feisty development, when network-manager
wasn't installed by default. So the setting where there all the time and
NM didn't have any problem with them.
--
Network-Manager does
thanks christian, remove those lines brought eth0 back online. :-)
i do agree with luka though that this is still a bug, and should be
treated as such.
--
Network-Manager doesn't initially connect to wired network
https://bugs.launchpad.net/bugs/133374
You received this bug notification because
thanks christian, removing those lines brought eth0 back online. :-)
i do agree with luka though that this is still a bug, and should be
treated as such.
--
Network-Manager doesn't initially connect to wired network
https://bugs.launchpad.net/bugs/133374
You received this bug notification becaus
Christian, I cannot agree with your assessment, particularly as
GNOME/KDE tools by default write interface with auto + dhcp in the
interfaces file and as this was the setting on previous Ubuntu releases
that were supposed to work with n-m. So it is clear regression and will
cause problems with exis
I could fix this problem.
Any interface managed by NetworkManager shouldn't be stated in the
/etc/network/interfaces file.
@litmotiv: just remove these lines and network manager should bring up
the interface again.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
same problem here with a different driver, from syslog:
NetworkManager: eth0: Device is fully-supported using driver 'skge'.
NetworkManager: nm_device_init(): waiting for device's worker thread to
start
NetworkManager: nm_device_init(): device's worker thread started,
continuing.
Networ
can you please attach your /etc/network/interfaces configuration to this
bug report?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
Network-Manager doesn't initially connect to wired network
https://bugs.launchpad.net/bugs/133374
You received this bug notification be
11 matches
Mail list logo
