Package Details: qnetctl-git 20140422-1

Package Base: qnetctl-git
Description: A Qt GUI for netctl
Upstream URL: https://github.com/luebking/qnetctl/
Category: network
Licenses: GPL2
Submitter: seth
Maintainer: seth
Last Packager: None
Votes: 5
First Submitted: 2013-10-24 20:38
Last Updated: 2014-04-22 19:25

Dependencies (1)

Required by (0)

Sources

Latest Comments

Comment by seth

2014-04-22 19:26

more robust scanning of down interfaces (that uplink slow), explicit disconnect profiles

Comment by seth

2014-04-19 21:23

After some stall, there's a major change in the backend that uses a dbus controlled UID0 process to trigger a limited set of actions (iw scan, netctl, systemctl calls), ie. one does only have to elevate this one process and that can also be done via a simple sudo pattern.

In addition some fixes reg. scanning networks (ensures the device to be up) and autostarting profile management.

Comment by seth

2013-10-26 09:28

Yupp, sorry.
Forgot that i cheated arch by placing a symlink higher into the PATH.

Should be fixed. Many thanks for the notice.

Comment by phillipe

2013-10-26 01:14

@seth
Very good work. Very simple and useful.
I had problems to compile because Arch now use qt5 as default. So qmake must be qmake-qt4 to work correctly.

Comment by seth

2013-10-24 20:39

QNetCtl is a Qt frontend for netctl, ip and iw

It shows you avaialable network profiles, devices, wireless access points and ad hoc networks and allows you to create a (basic!) netctl profile for new available connections and switch between the profiles.

The only build dependency is QtGui, runtime requirements are netctl, ip and -optionally- iw (for wireless connections)

Biggest issue:
--------------
Many network operations require root permissions, that does esp. include wireless scanning.

-> As resolution you'll either have to run qnetctl as root or provide a way to elevate permissions, eg. kdesu.

Just, you really don't want to enter the root password every ten seconds to check for available access points.
For now, it's up to you to decide whether you want to add NOPASSWD entries to the sudoers or polkit rules ... or enter the root password all the time ;-)