*** This bug is a duplicate of bug 82335 ***
https://bugs.launchpad.net/bugs/82335
> Only devices that are *not* listed in /etc/network/interfaces or which have
> been configured "auto" and "dhcp" (with no other options) are managed by NM.
Just want to point to the related bug #92299, that NM
*** This bug is a duplicate of bug 82335 ***
Moving milestone forward.
** Changed in: network-manager (Ubuntu)
Target: 7.04-beta => ubuntu-7.04
--
network-manager does not take into account static configurations *properly*
https://launchpad.net/bugs/87941
--
kubuntu-bugs mailing list
k
*** This bug is a duplicate of bug 82335 ***
You're right, more precisely, here is the behavior I've noticed for the
network settings (I use ifconfig to check the network setting changes):
- If I run the Network settings dialog by left clicking the NM Icon:
. When changing from dhcp -> static:
*** This bug is a duplicate of bug 82335 ***
>Looks like this one is killed in Feisty Beta ?
>
>Gave a try in 7.04 beta, and after setting my static IP, the little NM icon :
>
>- briefly displays (.5 s) the network as disconnected,
>- then starts a sympatic animation with a green circle (2s)
>- an
*** This bug is a duplicate of bug 82335 ***
Looks like this one is killed in Feisty Beta ?
Gave a try in 7.04 beta, and after setting my static IP, the little NM
icon :
- briefly displays (.5 s) the network as disconnected,
- then starts a sympatic animation with a green circle (2s)
- and fina
*** This bug is a duplicate of bug 82335 ***
** Changed in: network-manager (Ubuntu)
Assignee: Martin Pitt => Tollef Fog Heen
--
network-manager does not take into account static configurations *properly*
https://launchpad.net/bugs/87941
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
*** This bug is a duplicate of bug 82335 ***
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tollef Fog Heen
** Changed in: network-manager (Ubuntu)
Assignee: Tollef Fog Heen => Martin Pitt
--
network-manager does not take into account static configurations *properly
*** This bug is a duplicate of bug 82335 ***
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => beta
--
network-manager does not take into account static configurations *properly*
https://launchpad.net/bugs/8794
*** This bug is a duplicate of bug 82335 ***
Hi Steve,
Thanks for the info. I kinda realized that after playing around with my
network interfaces configuration that I can only use DHCP in order for
the NetworkManager applet to work. Is this bug going to be fixed so that
Static Ips will work al
*** This bug is a duplicate of bug 82335 ***
I should point out that I don't have a static set-up. The set-up was in
/etc/network/interfaces, but it basically said eth1, auto, dhcp, and
explicitly gave the wireless essid I connect to.
--
network-manager does not take into account static configu
*** This bug is a duplicate of bug 82335 ***
I just had great confusion about this issue.
I upgraded to Feisty from Edgy.
Gaim was apparently not working. Nothing I did in the options in Gaim
instant messenger would make it go online, or even show my list of
buddies.
It apparently depends on n
*** This bug is a duplicate of bug 82335 ***
** This bug has been marked a duplicate of bug 82335
network-manager should not set offline mode when it manages no device
--
network-manager does not take into account static configurations *properly*
https://launchpad.net/bugs/87941
--
ubuntu-b
Yes I agree I spoke too soon in saying it was a duplicate, which is why
I didn't mark it as one right away. I'm going to try and duplicate it on
a virtual machine so I can confirm it but it's not cooperating at the
moment. I'll hopefully have more to add soon.
--
network-manager does not take int
Hi Chris! From what I read, I don't think this is the same issue. The
problem is not that NM doesn't work with a static interfaces (I know
that it "bypasses" them already, I used that since hoary).
The problem is that network manager does not REPORT a network when using
a static ip. Result? It *br
I'm going to leave it unmarked as a duplicate though for the moment, as
it seems it's having a much more direct effect on Feisty then previous
versions.
--
network-manager does not take into account static configurations *properly*
https://launchpad.net/bugs/87941
--
ubuntu-bugs mailing list
ub
The readme.debian explicitly states the following, which just confirms
your statement:
Only devices that are *not* listed in /etc/network/interfaces or which have
been configured "auto" and "dhcp" (with no other options) are managed by NM.
This way you can setup a custom (static) configuration f
--- Comment #3 from Dan Williams 2007-02-26 12:32 UTC ---
NM actually has some support for static IP settings already, but the distro
specific backend has to support it. Fedora, SUSE, and Debian support it. But
Ubuntu decided to make NM ignore _any_ interface that you have already
con
17 matches
Mail list logo
