Image 01
profile-image

Inphos

Oliver G.
Network
System Software
test
NUT - Network UTility

Network 38 comments

Score 77.8%
Nov 18 2009
Does it work? The gentoo ebuild may be of some help to install nut properly. - Nov 29 2009
Hi, we think, we've fixed the problem. Please try to build the latest head. You also need to install openresolv. - Nov 25 2009
Hi,
we're sorry, but we couldn't find a solution to your problem so far.
According to your compiler-output linking should work if you installed the correct library (libiw). The order of the linker flags are the same on our machines.

Which version of qt are using (though this shouldn't cause the problems)?

Wirelesstools, libwireless and libwireles-devel aren't corrupted? - Nov 24 2009
Hi,
could you post the complete buildlog somewhere? (i.e. pastebin) - Nov 17 2009
Hi,
I put it in the bug tracker (https://redmine.stbuehler.de/issues/20) and we'll try to solve this soon.

We may need you're assistance though as it compiles on debian and gentoo. - Nov 12 2009
Nice. Thank you very much for your work. I will add a link to your page in the app description :) - Aug 05 2009
I can't reply to your last comment so I'll this here.
I've tried it myself to find out which files are realy necessary. Here's what I did:
daniel@daniel ~/nut $ git clone git://stbuehler.de/nut.git
remote: Counting objects: 6472, done.
remote: Compressing objects: 100% (1913/1913), done.
remote: Total 6472 (delta 4791), reused 6104 (delta 4527)
Receiving objects: 100% (6472/6472), 5.11 MiB | 686 KiB/s, done.
Resolving deltas: 100% (4791/4791), done.
daniel@daniel ~/nut $ cd nut
daniel@daniel ~/nut/nut $ ls
cnut debian docs gentoo libnutclient libnutcommon libnutwireless nut.pro nuts presentation qnut resources
daniel@daniel ~/nut/nut $ qmake -r
Reading /home/daniel/nut/nut/libnutcommon/libnutcommon.pro
Reading /home/daniel/nut/nut/libnutwireless/libnutwireless.pro
Reading /home/daniel/nut/nut/libnutclient/libnutclient.pro
Reading /home/daniel/nut/nut/nuts/nuts.pro
Reading /home/daniel/nut/nut/qnut/qnut.pro
Reading /home/daniel/nut/nut/cnut/cnut.pro
daniel@daniel ~/nut/nut $ make
<a lot of compiler output>
daniel@daniel ~/nut/nut $ cd qnut/
daniel@daniel ~/nut/nut/qnut $ ./qnut
Try setting watch dir to "/var/run"
Pid file name is "dbus.pid"
Enabling DBusMonitor
Filedescriptor for inotify is 9
Connected SocketNotifier for inotify
Set dbus pid to: 3486
(Inotify) Setting up watches
Setup Pid file dir watch with 1
Enabled DBusMonitor
Cannot open file '/usr/share/qnut/icons/qnut_small.svg', because: No such file or directory
Cannot open file '/usr/share/qnut/icons/qnut_small.svg', because: No such file or directory
<after nut start>
setInformation()
Placing getDeviceList Call
essid feteched
Properties feteched
config feteched
essid feteched
Properties feteched
"Environmentname: "
activeenv fetched
activeenv fetched
InterfaceInit completed
Feteched all Interfaces
EnvironmentInit completed: ""
Device init completed: "eth0"

As root:
daniel nut # mkdir /etc/nuts
daniel nut # echo 'device "eth0";' > /etc/nuts/nuts.config
daniel nut # cp resources/nuts-dbus.conf /etc/dbus-1/system.d/
daniel nut # cd nuts/
daniel nuts # ./nuts
Try setting watch dir to "/var/run"
Pid file name is "dbus.pid"
Filedescriptor for inotify is 23
Connected SocketNotifier for inotify
Set dbus pid to: 3486
(Inotify) Setting up watches
Setup Pid file dir watch with 1
Device(eth0) gotCarrier
Set next environment 0
Interface_IPv4::start

The netdev goup has been created before.

qnut doesn't have any symbol, but that doesn't matter, it works anyway. - May 16 2009
I can't reply to your last comment so I'll this here.
I've tried it myself to find out which files are realy necessary. Here's what I did:
daniel@daniel ~/nut $ git clone git://stbuehler.de/nut.git
remote: Counting objects: 6472, done.
remote: Compressing objects: 100% (1913/1913), done.
remote: Total 6472 (delta 4791), reused 6104 (delta 4527)
Receiving objects: 100% (6472/6472), 5.11 MiB | 686 KiB/s, done.
Resolving deltas: 100% (4791/4791), done.
daniel@daniel ~/nut $ cd nut
daniel@daniel ~/nut/nut $ ls
cnut debian docs gentoo libnutclient libnutcommon libnutwireless nut.pro nuts presentation qnut resources
daniel@daniel ~/nut/nut $ qmake -r
Reading /home/daniel/nut/nut/libnutcommon/libnutcommon.pro
Reading /home/daniel/nut/nut/libnutwireless/libnutwireless.pro
Reading /home/daniel/nut/nut/libnutclient/libnutclient.pro
Reading /home/daniel/nut/nut/nuts/nuts.pro
Reading /home/daniel/nut/nut/qnut/qnut.pro
Reading /home/daniel/nut/nut/cnut/cnut.pro
daniel@daniel ~/nut/nut $ make
<a lot of compiler output>
daniel@daniel ~/nut/nut $ cd qnut/
daniel@daniel ~/nut/nut/qnut $ ./qnut
Try setting watch dir to "/var/run"
Pid file name is "dbus.pid"
Enabling DBusMonitor
Filedescriptor for inotify is 9
Connected SocketNotifier for inotify
Set dbus pid to: 3486
(Inotify) Setting up watches
Setup Pid file dir watch with 1
Enabled DBusMonitor
Cannot open file '/usr/share/qnut/icons/qnut_small.svg', because: No such file or directory
Cannot open file '/usr/share/qnut/icons/qnut_small.svg', because: No such file or directory
<after nut start>
setInformation()
Placing getDeviceList Call
essid feteched
Properties feteched
config feteched
essid feteched
Properties feteched
"Environmentname: "
activeenv fetched
activeenv fetched
InterfaceInit completed
Feteched all Interfaces
EnvironmentInit completed: ""
Device init completed: "eth0"

As root:
daniel nut # mkdir /etc/nuts
daniel nut # echo 'device "eth0";' > /etc/nuts/nuts.config
daniel nut # cp resources/nuts-dbus.conf /etc/dbus-1/system.d/
daniel nut # cd nuts/
daniel nuts # ./nuts
Try setting watch dir to "/var/run"
Pid file name is "dbus.pid"
Filedescriptor for inotify is 23
Connected SocketNotifier for inotify
Set dbus pid to: 3486
(Inotify) Setting up watches
Setup Pid file dir watch with 1
Device(eth0) gotCarrier
Set next environment 0
Interface_IPv4::start

The netdev goup has been created before.

qnut doesn't have any symbol, but that doesn't matter, it works anyway. - May 16 2009
Thanks for the grammar correction. I've fixed this. As for your dbus problem:
Did you put the nuts-dbus.conf into the right place (I guess it should be in /etc/dbus-1/system.d/)? If you have, I will add some debug output to nuts. - May 14 2009
Hi,
thanks for trying to create a pkgbuild.
Unfortunatelly we never encountered the problems you have. It compiles fine on 3 different debian pcs (amd64+i686) and on 2 different gentoo pcs (amd64+i686).
We can confirm that it works on at least 5 debian and 2 gentoo machines.
Have you tried running nuts in a console as well as qnut? nuts config files and dbus config files are put in the right place? qnut has sufficient rights (though it looks like as if nuts can't connect to dbus)? - May 11 2009
Unfortunatelly we don't know archlinux.
According to the archlinux-wiki (http://wiki.archlinux.org/index.php/Arch_vs_Others#Arch_vs_Gentoo) you have to write a PKGBUILD script. You might use the gentoo ebuild as reference. Maybe there is some way to use the debian package. - Apr 27 2009
Alright,
unfortunately I don't realy understand how you added qnut/nut to netdev group.

Anyway, from your output I can see that your user named "dyve" is not in the netdev group. Under debian you have to execute the follwing command as root to add "dyve" to the netdev group (always read the man page before executing commands from the internet):
adduser dyve netdev

adduser <username> <groupname>

After that you have to login again. Check with "id" if you are in the netdev group afterwards.

If qnut does not show any devices it's most likely that you did not configure nuts. Please have a look at /etc/nuts/nuts.conf. You can get the name of a device with "ifconfig". You can find an example config file in the download section. - Jun 03 2008
Hi,
did you chown/chmod nuts/qnut or did you add all users using qnut/cnut to netdev?

Could you provide us with the ouput of:
# id
# ls -l /usr/bin/qnut /usr/bin/cnut /usr/sbin/nuts
# cat /etc/dbus-1/system.d/nuts-dbus.conf

The file /etc/dbus-1/system.d/nuts-dbus.conf is the access permission configuration file for nuts' dbus interface. You could try to run qnut as root (once, not forever, just to check if it works) and see if it works. If it does, then you do not have sufficient rights.

Atm I'm downloading an ubuntu vmware image to check if it works with ubuntu 8.04.
- Jun 03 2008
Rereading your comment, I realized that the "-p" flag is not listed in your yacc's "help" message. Are you using yacc or bison? If it's yacc, then try bison. - May 31 2008
Hi,
for the compiler errors I have to contact the dev of the server.

There are new packages available (version 0.4.9) that don't have this InvalidSignature message anymore. Unfortunately this is still a bug in qt. Actually you don't have sufficient rights to access the interface on dbus. Qt returns InvalidSignature instead of AccessDenied.

In order to get it working, just add all users using qnut/cnut to the netdev group.

You can get new packages from
http://gobby.efreetsystems.de/debian/pool/main/binary/

I hope that helps. - May 31 2008