Public bug reported: Binary package hint: network-manager
In Ubuntu Hardy (i386), using the Network Manager applet's "Disable Networking" button only disables IPv4. I was still able to ping6 another machine using a v6 address received from radvd. Similarly, other machines could make v6 UDP and TCP connections to the local machine when the user thought networking was disabled (although I didn't test that). I was tempted to mark this a security bug, but I didn't because the security breach is only based on an expectation of what unticking "Enable Networking" should do. Some users might well use that do disable networking while they configure a firewall or something, though. Also, disabling networking to prevent local programs accessing the network only works for IPv4 because of this. So there are obvious security implications, but I'm not sure if it's the sort of thing to bug the Security team about. My expectation for the behaviour of the tickbox that says "Enable Networking" was that unticking it would bring all the network interfaces down (except loopback), so ifconfig wouldn't show them without -a. Same as ifdown eth0; ... would if the interfaces were configured in /etc/network/interfaces. I've seen a comment that maybe N-M keeps the ifaces UP and RUNNING so it can check for link activity. It doesn't make sense to do that if all networking is supposed to be disabled anyway. I see this behaviour on the the i386 Hardy Beta livecd, and with up-to- date Hardy installed on a Toshiba A70 laptop (rtl8139, madwifi). I doubt it's hardware-specific, though. I'll provide more info if this isn't easily reproducible for everyone. network-manager version: 0.6.6-0ubuntu5. network-manager-gnome 0.6.6-0ubuntu2. ifconfig # networking disabled ath0 Link encap:Ethernet HWaddr 00:90:96:b4:99:aa inet6 addr: fe80::290:96ff:feb4:99aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:02:3f:d4:2c:44 inet6 addr: 3ffe:bc0:112:1:202:3fff:fed4:2c44/64 Scope:Global inet6 addr: fe80::202:3fff:fed4:2c44/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40383 errors:0 dropped:0 overruns:0 frame:0 TX packets:22416 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:60715796 (57.9 MB) TX bytes:1554946 (1.4 MB) Interrupt:18 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1582 errors:0 dropped:0 overruns:0 frame:0 TX packets:1582 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79260 (77.4 KB) TX bytes:79260 (77.4 KB) wifi0 Link encap:UNSPEC HWaddr 00-90-96-B4-99-AA-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6637 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 B) TX bytes:305302 (298.1 KB) Interrupt:19 ifconfig # networking enabled ath0 Link encap:Ethernet HWaddr 00:90:96:b4:99:aa inet6 addr: fe80::290:96ff:feb4:99aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:02:3f:d4:2c:44 inet addr:10.1.0.207 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: 3ffe:bc0:112:1:202:3fff:fed4:2c44/64 Scope:Global inet6 addr: fe80::202:3fff:fed4:2c44/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40393 errors:0 dropped:0 overruns:0 frame:0 TX packets:22462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:60717173 (57.9 MB) TX bytes:1561469 (1.4 MB) Interrupt:18 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1582 errors:0 dropped:0 overruns:0 frame:0 TX packets:1582 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79260 (77.4 KB) TX bytes:79260 (77.4 KB) wifi0 Link encap:UNSPEC HWaddr 00-90-96-B4-99-AA-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6649 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 B) TX bytes:305854 (298.6 KB) Interrupt:19 (the only diff is packet counts and the IPv4 line for eth0). The v6 routing table (route -6) still has a default route with "networking disabled", so it looks like v6 still has full connectivity. Or it would if my v6 router actually worked. :/ I gave up on v6 until my ISP supports it, but I still have radvd installed on my router. A cable was plugged in to eth0 the whole time the laptop was on. It seems kind of pointless for it to be transmitting packets on ath0, but it is. In any case, the laptop's wireless switch is off. It's not associated with an AP, though. I think I already saw a bug report about leaving the radio on, so I won't go on any further about this. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- "disable networking" leaves ipv6 enabled https://bugs.launchpad.net/bugs/215497 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs