This bug was fixed in the package network-manager - 0.7.1~rc3-0ubuntu1
---
network-manager (0.7.1~rc3-0ubuntu1) jaunty; urgency=low
* upstream 0.7.1 rc3
+ http://git.freedesktop.org/NetworkManager/NetworkManager/
+ NETWORKMANAGER_0_7 (branch)
* point Vcs-Bzr: to new 0.7.1
thanks for the debdiff ... i merged your changes with a tiny change to
the jaunty branch (see related branches section).
** Changed in: network-manager (Ubuntu Jaunty)
Status: Triaged = Fix Committed
--
Network manager shows and connects to virtual interfaces
thanks for the merge request i meant.
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here is a tentative debdiff for this issue. Alexander, do you see any
reason not to apply this patch?
** Attachment added: network-manager-199140.debdiff
http://launchpadlibrarian.net/23270646/network-manager-199140.debdiff
--
Network manager shows and connects to virtual interfaces
patch tested here, btw; works as intended.
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same behavior with hamachi and wippien VPN tools. May it be linked to
bug #329105 ?
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Not sure if this is the same bug. But using new jaunty on my Dell
m1210. BCM44 chipset. Network manager fails to manage the device, eth0.
Working previously. Now nm shows as NULL driver.
lshal, lspci and nm-tool out put attached
** Attachment added: logs.gz
On Mon, Feb 09, 2009 at 08:41:48AM -, aenertia wrote:
Not sure if this is the same bug. But using new jaunty on my Dell
m1210. BCM44 chipset. Network manager fails to manage the device, eth0.
Working previously. Now nm shows as NULL driver.
lshal, lspci and nm-tool out put attached
On Fri, Jan 23, 2009 at 11:36:03PM -, Steve Langasek wrote:
Hi Alexander,
As requested on bug #320652, here's the lshal output for my tap0 vs.
eth0 devices. The key difference I notice is the
net.originating_device, which shows only
'/org/freedesktop/Hal/devices/computer' for tap0 - I
well, you can only find the driver if you traverse the
net.originating_device field. Keying on that looks much more robust to
me...
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of
oh, sorry, reading to fast - you already said you would do that :-)
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: network-manager (Ubuntu Jaunty)
Target: None = jaunty-alpha-6
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Alexander,
As requested on bug #320652, here's the lshal output for my tap0 vs.
eth0 devices. The key difference I notice is the
net.originating_device, which shows only
'/org/freedesktop/Hal/devices/computer' for tap0 - I think this
corresponds to the fact that /sys/class/net/tap0/ has no
how does the virt device show up in hal?
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Triaged
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs,
Please note that the hal patch to show virtual network devices is in
Jaunty (coming from upstream).
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have the same bug when trying to use hamachi. The hamachi client
assigns a static IP, but networkmanager tries to run dhclient on the
address which fails. The underlying interface is a tun device which gets
a new mac address each time, so saving settings to tell NM to ignore it
don't work.
I have entry below in my /etc/network/interfaces, this caused NM to not
add any Auto ethX but instead present 'ifupdown tap0'
auto tap1
iface tap1 inet static
address 10.238.1.1
netmask 255.255.255.0
tunctl_user thnov
--
Network manager shows and connects to virtual
what capability does such a virtual interface have in hal? If its
net.80203 ... do we know that this is actually correct?
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug notification because you are a member of Ubuntu
Bugs,
ok, unmilestoning for hardy. Please bring this back to my attention once
it becomes relevant again.
Technically, filtering by hal udi should be fairly simple - if we really
need it.
** Changed in: network-manager (Ubuntu)
Target: ubuntu-8.04-beta = None
--
Network manager shows and
I have a feeling this problem is what was causing my vmnet interfaces to
not initialize correctly as well. I ended up having to add definitions
in interfaces for my vmnet1 and vmnet8 or they came up w/o IP
configured, as well in kdenetworkmanager they showed up in the list of
configurable devices
This regression was caused by the fix for bug 199269. In addition to
confusing network-manager, libvert is not correctly dealing with
assigning addresses for its virtual network devices.
** Changed in: network-manager (Ubuntu)
Target: None = ubuntu-8.04-beta
--
Network manager shows and
See bug 198541.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Alexander Sack (asac)
Status: New = Confirmed
--
Network manager shows and connects to virtual interfaces
https://bugs.launchpad.net/bugs/199140
You received this bug
FYI, I uploaded a new hal into hardy which reverts the recent patch to
detect virtual network interfaces. So this is at least not a blocker for
hardy any more, but one day it will come back, so it eventually needs to
get fixed.
--
Network manager shows and connects to virtual interfaces
23 matches
Mail list logo
