touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #127385
[Bug 1532431] [NEW] NetworkManager interferes with unmanaged 802.11 monitor mode interfaces
Public bug reported:
If a virtual 802.11 interface of type monitor is created on a 802.11
physical interface that already has a virtual interface of type managed
created on it, then the managed interface is deleted. NetworkManager
sets the type of the monitor interface to managed. This can be
illustrated by the following commands. All the interface names have been
listed in /etc/network/interfaces as follows so NetworkManager should
not be managing them in any way.
# Disable network manager on interface names I want to use for monitoring
# related purposes
iface eth1 inet manual
iface BigTenda inet manual
iface LittleBelkin inet manual
iface LittleTenda inet manual
iface Sinmax inet manual
iface mon0 inet manual
iface phy0.mon manual
iface phy1.mon manual
iface phy2.mon manual
iface phy3.mon manual
iface phy4.mon manual
iface phy5.mon manual
iface phy6.mon manual
iface phy7.mon manual
iface phy8.mon manual
iface phy9.mon manual
root@dragon:/home/roger# systemctl start NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface Sinmax
ifindex 11
wdev 0x300000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x300000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# systemctl stop NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
root@dragon:/home/roger# iw dev
phy#4
Interface Sinmax
ifindex 13
wdev 0x400000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x400000002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x400000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x400000002
addr 00:0f:11:92:06:b2
type monitor
This stops any running or future network traces on this interface
working.
This is another example of network manager interfering with interfaces
it is not supposed to be managing. See bug #1314848 which is still
unresolved.
The above test was carried out on Ubuntu 15.10
network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
*** 1.0.4-0ubuntu5.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.4-0ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: iw mac80211 monitor networkmanager wifi
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1532431
Title:
NetworkManager interferes with unmanaged 802.11 monitor mode
interfaces
Status in network-manager package in Ubuntu:
New
Bug description:
If a virtual 802.11 interface of type monitor is created on a 802.11
physical interface that already has a virtual interface of type
managed created on it, then the managed interface is deleted.
NetworkManager sets the type of the monitor interface to managed. This
can be illustrated by the following commands. All the interface names
have been listed in /etc/network/interfaces as follows so
NetworkManager should not be managing them in any way.
# Disable network manager on interface names I want to use for monitoring
# related purposes
iface eth1 inet manual
iface BigTenda inet manual
iface LittleBelkin inet manual
iface LittleTenda inet manual
iface Sinmax inet manual
iface mon0 inet manual
iface phy0.mon manual
iface phy1.mon manual
iface phy2.mon manual
iface phy3.mon manual
iface phy4.mon manual
iface phy5.mon manual
iface phy6.mon manual
iface phy7.mon manual
iface phy8.mon manual
iface phy9.mon manual
root@dragon:/home/roger# systemctl start NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface Sinmax
ifindex 11
wdev 0x300000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x300000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# systemctl stop NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x300000002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
root@dragon:/home/roger# iw dev
phy#4
Interface Sinmax
ifindex 13
wdev 0x400000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x400000002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x400000001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x400000002
addr 00:0f:11:92:06:b2
type monitor
This stops any running or future network traces on this interface
working.
This is another example of network manager interfering with interfaces
it is not supposed to be managing. See bug #1314848 which is still
unresolved.
The above test was carried out on Ubuntu 15.10
network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
*** 1.0.4-0ubuntu5.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.0.4-0ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+subscriptions
Follow ups