[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Network Applet
From: Kåre_Särs <kare.sars () iki ! fi>
Date: 2013-10-20 21:25:38
Message-ID: 2176999.4pL9EMJAGA () sars-ux32vd
[Download RAW message or body]
Hi,
On Sunday 20 October 2013 14:10:21 Jan Grulich wrote:
> Dne 20.10.2013 12:18, Reindl Harald napsal(a):
> > Am 20.10.2013 11:59, schrieb Jan Grulich:
> >>> * allow more than one connection to be expanded at a time
> >>
> >> I don't think is necessary to allow more than one connection to be
> >> expanded, because mostly you are connected only via one connection (or
> >> only one is default route)
> >
> > says who?
> >
> > yes, the machine below is a Fedora KDE-Workstation and even with a simple
> > setup when VPN is a topic you have no longer one default route for all
>
> I said mostly and even if you are using VPN connections, 99% of users
> would have expanded only one connection to see the traffic monitor. And
> I expect when you want to use some technical stuff, you won't use KDE NM
> applet for that.
Why limit the number of expanded items? What is the gain? I do not have as
extreme situation as the example below, but I have two networks at the same
time at work. One for internal testing and the other for the company wide
network. I definitely see a use-case for expanding more than one connection.
KDE NM has been more than enough for that so far ;)
Thanks for porting to QML!
/Kåre
>
> > my understanding of KDE is "for powerusers" and not for the
> > simple "that is my network cable" alone
> > ______________________________________
> >
> > [root@srv-rhsoft:~]$ route -n | wc -l
> > 12
> >
> > br0 = WLAN/LAN Brdige
> > br1 = Gust-WLAN/Virtual Device
> > eth0 = LAN
> > eth1 = WAN
> > eth2 = Virtual Devbice for Gust-WLAN-Bridge
> > tap0 = OpenVPN
> > vmnet8 = VMware NAT
> > wlan0 = Personal WLAN
> > waln1 = Guest WLAN
> >
> > br0: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500
> >
> > inet 192.168.7.2 netmask 255.255.255.0 broadcast 192.168.7.255
> > ether 24:be:05:1a:c0:27 txqueuelen 0 (Ethernet)
> > RX packets 16455 bytes 3459475 (3.2 MiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 13284 bytes 6685829 (6.3 MiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >
> > inet 192.168.10.1 netmask 255.255.255.0 broadcast
> > 192.168.10.255
> > ether 28:10:7b:ca:be:52 txqueuelen 0 (Ethernet)
> > RX packets 0 bytes 0 (0.0 B)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 0 bytes 0 (0.0 B)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
> >
> > ether 24:be:05:1a:c0:27 txqueuelen 1000 (Ethernet)
> > RX packets 13183 bytes 3289640 (3.1 MiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 10200 bytes 3934711 (3.7 MiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> > device interrupt 20 memory 0xf7e00000-f7e20000
> >
> > eth1: flags=67<UP,BROADCAST,RUNNING> mtu 1500
> >
> > inet **.**.**.** netmask 255.255.255.0 broadcast
> > 255.255.255.255
> > ether 00:50:8d:b5:cc:de txqueuelen 1000 (Ethernet)
> > RX packets 9056524 bytes 10416431487 (9.7 GiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 6900996 bytes 1563347260 (1.4 GiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> > device interrupt 16 memory 0xf7cc0000-f7ce0000
> >
> > eth2: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500
> >
> > ether da:a5:3f:9c:d0:19 txqueuelen 500 (Ethernet)
> > RX packets 0 bytes 0 (0.0 B)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 0 bytes 0 (0.0 B)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1444
> >
> > inet 192.168.8.241 netmask 255.255.255.0 broadcast
> > 192.168.8.255
> > ether 5a:27:d8:c7:7e:cc txqueuelen 500 (Ethernet)
> > RX packets 897500 bytes 376796062 (359.3 MiB)
> > RX errors 0 dropped 16308 overruns 0 frame 0
> > TX packets 983016 bytes 491210698 (468.4 MiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >
> > inet 192.168.196.1 netmask 255.255.255.0 broadcast
> > 192.168.196.255
> > ether 00:50:56:c0:00:08 txqueuelen 1000 (Ethernet)
> > RX packets 164721 bytes 0 (0.0 B)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 565701 bytes 0 (0.0 B)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >
> > ether 28:10:7b:ca:be:51 txqueuelen 1000 (Ethernet)
> > RX packets 3269 bytes 452877 (442.2 KiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 8406 bytes 3612636 (3.4 MiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >
> > ether 28:10:7b:ca:be:52 txqueuelen 1000 (Ethernet)
> > RX packets 0 bytes 0 (0.0 B)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 0 bytes 0 (0.0 B)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> Jan
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
> >> <<
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic