Discussion:
What does "Restrict to Device" mean in the Kubuntu network manager?
(too old to reply)
Sean Weiner
2014-10-09 06:41:42 UTC
Permalink
What does "Restrict to Device" mean in the Kubuntu network manager?
Loading Image...
Mike Easter
2014-10-09 12:45:48 UTC
Permalink
Post by Sean Weiner
What does "Restrict to Device" mean in the Kubuntu network manager?
http://oi57.tinypic.com/tafwjd.jpg
I assume the following; my wireless configurator doesn't have that feature.

Normally that field would be blank/empty.

Populated, I believe it would restrict the device from accessing
anything other than the MAC address defined. It could be populated with
the MAC of your wireless router or gateway device.
--
Mike Easter
Sean Weiner
2014-10-09 14:02:10 UTC
Permalink
Post by Mike Easter
I assume the following; my wireless configurator doesn't have that feature.
I can't stand the default "wireless configurator" in Kubuntu 14.04.
It's horrific.

Whatever was used on Kubuntu 13.10 worked great.
Whatever is being used on Kubuntu 14.04 is horrid.

After a dozen or so attempts at doing the SAME THING, the Kubuntu 14.04
one finally connects (yes, I know that's the definition of insanity).

Can you tell me what your Kubuntu "wireless configurator" is so that I
may switch off the default Kubuntu one and use the one you use?

Anything would be better than this one.
Sean Weiner
2014-10-09 14:08:59 UTC
Permalink
Post by Sean Weiner
Can you tell me what your Kubuntu "wireless configurator" is so that I
may switch off the default Kubuntu one and use the one you use?
Anything would be better than this one.
This is the wireless configurator I'm apparently using on Kubuntu 14.04,
but, it's absolutely horrid compared to what was on Kubuntu 13.10.
Loading Image...

What can I replace it with that will work better?
Cybe R. Wizard
2014-10-09 14:26:47 UTC
Permalink
On Thu, 9 Oct 2014 14:08:59 +0000 (UTC)
Post by Sean Weiner
Post by Sean Weiner
Can you tell me what your Kubuntu "wireless configurator" is so
that I may switch off the default Kubuntu one and use the one you
use?
Anything would be better than this one.
This is the wireless configurator I'm apparently using on Kubuntu
14.04, but, it's absolutely horrid compared to what was on Kubuntu
13.10. http://oi59.tinypic.com/2daf8nm.jpg
What can I replace it with that will work better?
Wicd works well for me.

Cybe R. Wizard
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Sean Weiner
2014-10-09 14:39:52 UTC
Permalink
Post by Cybe R. Wizard
Wicd works well for me.
I am installing it as we speak!
$ sudo apt-get install wicd
..... stuff ....
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe python-wicd
all 1.7.2.4-4.1ubuntu1 [34.3 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty/universe wicd-daemon
all 1.7.2.4-4.1ubuntu1 [166 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty/universe wicd-gtk all
1.7.2.4-4.1ubuntu1 [85.9 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty/universe wicd all
1.7.2.4-4.1ubuntu1 [4,256 B]
..... stuff ....
Cybe R. Wizard
2014-10-09 15:14:07 UTC
Permalink
On Thu, 9 Oct 2014 14:39:52 +0000 (UTC)
Post by Sean Weiner
Post by Cybe R. Wizard
Wicd works well for me.
I am installing it as we speak!
$ sudo apt-get install wicd
..... stuff ....
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe
python-wicd all 1.7.2.4-4.1ubuntu1 [34.3 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty/universe
wicd-daemon all 1.7.2.4-4.1ubuntu1 [166 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty/universe wicd-gtk
all 1.7.2.4-4.1ubuntu1 [85.9 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty/universe wicd all
1.7.2.4-4.1ubuntu1 [4,256 B]
..... stuff ....
Good luck! Wicd will also take a small amount of time to connect.

Kiss your SO a few times while you wait!

Cybe R. Wizard -...Significant Other, in case you wonder...
--
Nice computers don't go down.
Larry Niven, Steven Barnes
"The Barsoom Project"
Sean Weiner
2014-10-09 17:48:51 UTC
Permalink
Post by Cybe R. Wizard
Wicd will also take a small amount of time to connect.
I wonder how Kubuntu knows WHICH wireless daemon to run, now that I have
two?

There must be some setup involved because I tried running wicd and it
failed immediately (probably because the default wireless configurator
was also running?).

$ which wicd
==> /usr/sbin/wicd

$ wicd --help
==> Root privileges are required for the daemon to run properly. Exiting.

$ man wicd
==> Wicd is designed to give the user as much control over behavior of
network connections as possible. (stuff deleted)
Wicd has two major parts:
a) the daemon, which runs with root privileges;
b) and the user interface, which runs with normal user privileges.
(stuff deleted)
The user interface (stored in wicd-gtk (stuff deleted)
The daemon is started by wicd's init script during system startup
(before any user logs in)
FILES:
/etc/wicd/manager-settings.conf
/etc/wicd/wireless-settings.conf
/var/lib/wicd/configurations/
etc.

It didn't work when I just tried it, but, maybe I need to reboot so I'll
send this and reboot.

I wonder how Kubuntu knows WHICH wireless daemon to run, now that I have
two?
Caver1
2014-10-09 18:05:30 UTC
Permalink
Post by Sean Weiner
Post by Cybe R. Wizard
Wicd will also take a small amount of time to connect.
I wonder how Kubuntu knows WHICH wireless daemon to run, now that I have
two?
There must be some setup involved because I tried running wicd and it
failed immediately (probably because the default wireless configurator
was also running?).
$ which wicd
==> /usr/sbin/wicd
$ wicd --help
==> Root privileges are required for the daemon to run properly. Exiting.
$ man wicd
==> Wicd is designed to give the user as much control over behavior of
network connections as possible. (stuff deleted)
a) the daemon, which runs with root privileges;
b) and the user interface, which runs with normal user privileges.
(stuff deleted)
The user interface (stored in wicd-gtk (stuff deleted)
The daemon is started by wicd's init script during system startup
(before any user logs in)
/etc/wicd/manager-settings.conf
/etc/wicd/wireless-settings.conf
/var/lib/wicd/configurations/
etc.
It didn't work when I just tried it, but, maybe I need to reboot so I'll
send this and reboot.
I wonder how Kubuntu knows WHICH wireless daemon to run, now that I have
two?
Can't you remove the one you won't use?
--
Caver1
Sean Weiner
2014-10-09 18:28:19 UTC
Permalink
Post by Caver1
Can't you remove the one you won't use?
I'd love to remove it.

If only I knew how.

When I right click on the whatever GUI comes with Kubuntu/KDE,
it's called "Network Management Settings".

So, googling for "how to remove KDE network management settings",
I find this comes up, which intimates the "thing" is called
"networkmanagement" https://userbase.kde.org/NetworkManagement

Searching specifically for how to *remove* it, this comes up:
How can I completely remove NetworkManager?
http://askubuntu.com/questions/249944/how-can-i-completely-remove-networkmanager

That is for Ubuntu, and it's confusing because it gives different
answers, such as:
sudo apt-get purge network-manager
And, then later,
sudo apt-get remove --purge knetworkmanager network-manager

So, now I have *three* names for the thing, all similarly different.
Loading...