This bug is now a year old but I was just bit by this.
Had a DHCP problem on my new Ubuntu install so like a good GUI-boy I
went to the Network config and made sure dhcp was configured for eth0.
Big mistake. That modified /etc/network/interfaces. I then spent an hour
figuring out how
Hi,
Brian Murray [2007-04-16 22:31 -]:
I believe you are missing 'auto ath0' and 'auto eth1' from your
'/etc/network/interfaces' file.
Confirmed. n-m will ignore non-auto interfaces on purpose, since not
doing so would act against your manual configuration.
--
NetworkManager can't find
All my interfaces are auto. I've attached my interfaces file.
** Attachment added: my interfaces file
http://librarian.launchpad.net/7339081/interfaces
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a
Same here. I'll paste mine instead:
[EMAIL PROTECTED]:/etc/network$ cat interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
auto eth0
iface eth0 inet static
address 192.168.1.1
netmask 255.255.0.0
auto eth1
iface eth1 inet dhcp
wireless-essid MyWirelessAP
--
Niran, you have a static configuration for eth0. Is this your primary
network interface? It should be ignored by network-manager, the other
interfaces should be managed by it.
NabLa, you *only* have statically configured interfaces, so it is
correct that network-manager ignores them all.
--
The intention was that I'd be able to have a static IP address for my
wired connection, but be able to switch between my wired and my wireless
connections using NetworkManager. This worked perfectly until I updated
earlier today.
--
NetworkManager can't find any interfaces
OK, so all I need to do is to take out the essid line and NM will show the
interface.
Something that puzzles me is why shouldn't NM allow re-configuring an
interface configured statically, as it used to do. I sometimes log in for a
quick task using BlacBox instead of KDE, so the reason I had my
Closing this one, since the last comments all indicate wanted behaviour
of n-m. Thank you!
** Changed in: network-manager (Ubuntu)
Status: Needs Info = Rejected
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because
NabLa [2007-04-17 9:17 -]:
Something that puzzles me is why shouldn't NM allow re-configuring an
interface configured statically, as it used to do.
It did that only for a very short period of time, and clobbering
static configurations with dynamic changes caused a *lot* of grief.
You can
OK then! Thanks guys!
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Very well, this is a feature, not a bug.
I very strongly suggest that NetworkManager should be patched to produce
some useful output in this case, something to syslog to the effect of I
see some interfaced but I am ignoring them because auto isn't set would
have been extraordinarily useful.
I
After some recent updates, if /etc/network/interfaces even exists,
network-manager borks. Even if there are only two lines inside:
[EMAIL PROTECTED]:~$ cat /etc/network/interfaces.foo
iface ath0 inet dhcp
iface eth1 inet dhcp
If this file exists, nm-tool reports no interfaces and network-manager
I believe you are missing 'auto ath0' and 'auto eth1' from your
'/etc/network/interfaces' file.
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I had a static wired interface and a dynamic wireless interface
configured and working fine until the latest update. The wireless
networks still work for me, but the static wired interface doesn't show
up in nm-tool or the nm-applet menu as Wired Network like it used to.
This makes me sad.
Moving
It's also worth mentioning that, after deleting /etc/network/interfaces,
the moment I statically configure an interface using knetworkmanager,
NetworkManager gets totally stupid. Even if it switches to a non-
statically configured interface, it leaves the static interface default
route in place
I'm seeing this problem as well. I have a single Ethernet interface that
is configured with a static IP address, and network-manager reports that
I have no network interfaces. I'm running Feisty (newly upgraded from
Egdy, which was in turn newly upgraded from Dapper).
Brian Murray said:
By the way, I'm running Gnome, not KDE, so I don't have knetworkmanager.
I'd say this is a network-manager rather than an applet problem since nm-tool
cannot report any working interfaces.
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug
This route thing is quite surprising, does that mean you lose
connectivity if the static interface connection is no longer available?
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a member of Ubuntu
Bugs,
It doesn't make network-manager unhappy rather it makes network-
manager ignore the interface and not configure it. There is a new patch
for network-manager that makes it now say Manual connection instead of
No network connection.
--
NetworkManager can't find any interfaces
I'd say this is a network-manager rather than an applet problem since
nm-tool cannot report any working interfaces.
Well, I guess it depends. The earlier comment seems to imply that the
problem is not with network-manager, but with the contents of
/etc/network/interfaces. It says that removing
Thanks, Brian. I didn't see your entry before I posted the last one.
Sounds like my issue is taken care of.
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I've revised the config of several other K/Ubuntu machines of people
around and they all have /etc/network/interfaces populated with relevant
stuff, and they are all default installations of Dapper or Edgy.
As n1ywb, this is going to bite quite a lot of people.
--
NetworkManager can't find any
Could you elaborate as to what in particular is going to bite a lot of
people?
--
NetworkManager can't find any interfaces
https://bugs.launchpad.net/bugs/103532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
The affected group is the intersection of users who use NetworkManager,
and those who want to configure a static interface. Everybody with a
laptop uses NetworkManager. The number of people who set up a static
interface is admittedly smaller, but not insignificant IMO.
--
NetworkManager can't
I'm not sure about Jeff's situation, but in my case the nm-tool output I
posted indicates that network-manager isn't just ignoring the static
interface but it is also ignoring the non-static interface. I suspect
that it's not ignoring anything but rather that it's barfing. I haven't
stepped the
I have renamed /etc/network/interfaces and restarted networkmanager and
dispatcher and now nm-tool reports correctly my network devices.
Even when this seems to be fixed it is very strange that I always had my
interfaces configured statically and NM stopped to see them suddenly on
monday after an
NabLa: Ditto that, when I remove /etc/network/interfaces and restart
NetworkManager and NetworkManagerDispatcher, it suddenly works and nm-
tool correctly reports my interfaces. This isn't good behavior. There
was nothing weird in my /etc/network/interfaces file beforehand and this
bug is probably
Hum, I reported just now the same on another bug... I will copy and
paste, since this bug seems newer than that one.
Having the same problem as Brian. Pretty much the same config as Brian
as well - except that I already had all my network cards in
/etc/interfaces. But it worked just fine until
Sorry, when I said Brian I meant n1ywb
nm-tool output:
[EMAIL PROTECTED]:~$ nm-tool
NetworkManager Tool
State: connected
print_devices(): didn't get a reply from NetworkManager.
There are no available network devices.
--
NetworkManager can't find any interfaces
NetworkManager will not manage any interfaces that are configured in
'/etc/network/interfaces' as yours is. If you leave only the 'auto' and
'iface' line you should be able to use knetworkmanager to statically
configure your interface.
--
NetworkManager can't find any interfaces
Which interface are you referring to? NetworkManager cannot see either
eth1 or ath0 as per the nm-tool output. I statically configured eth1
AFTER knetworkmanager stopped seeing it, not before, so that cannot be
the cause of the issue. ath0 is not statically configured at all and
already only has
31 matches
Mail list logo
