NM 0.7 tries incorrectly to manage openvpn tap0 device as an ethernet device
Bug #320652 reported by
Steve Langasek
This bug report is a duplicate of:
Bug #199140: Network manager shows and connects to virtual interfaces.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Confirmed
|
Critical
|
Unassigned | ||
| Jaunty |
Confirmed
|
Critical
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
After upgrading from intrepid to jaunty, nm-applet now shows Wired networks (tap0) in its list of networks. This is an openvpn interface, and NM should *not* touch it; in the process of managing it, NM grabs a default route and a DNS server via DHCP from this interface, which I have openvpn configured *not* to do.
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in network-manager: | |
| importance: | Undecided → Critical |
| milestone: | none → jaunty-alpha-6 |
| status: | New → Confirmed |
Revision history for this message
| Alexander Sack (asac) wrote | #2 |
Revision history for this message
| Alexander Sack (asac) wrote | #3 |
To post a comment you must log in.
Marking this as critical, since it completely botches my network configuration on upgrade with no way to override. AFAICS, network-manager should simply exclude all tap interfaces from management, unless maybe explicitly instructed to manage them using the VPN configuration tool.