On Ubuntu 16.04.2, it starts from :666 as specified in /etc/darkstat/init.cfg
after a reboot. After this, changes to the config file port value seem to be
observed following service darkstat restart.
A little confusing but solved, thanks.
** Summary changed:
- connection refused due to pcap
Sorry about the documentation. I can't change what's in that magazine.
:)
The cfg file is specific to the distro and applies to systemd(?)
starting darkstat at boot time, it's not a standard part of darkstat /
not something it reads at startup.
i.e. Either "service start darkstat" or whatever
Thank you, it's working on :667
https://unix4lyfe.org/darkstat/linuxformat.jpg
says :666 though
There are rather deep references in man darkstat to 667 but I hadn't
looked because
/etc/darkstat/init.cfg says
PORT="-p 666"
...which seems to be ignored.
Oh well, thanks again.
Gareth
On Wed,
The default webserver port should be 667. Try: "netstat -lntp" while
darkstat is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699374
Title:
connection refused due to pcap error?
To
** Bug watch added: github.com/Ettercap/ettercap/issues #408
https://github.com/Ettercap/ettercap/issues/408
** Description changed:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699374
Title:
eth0, wlan0 on Ubuntu are now named according to
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[1]
user@tommy:~$ sudo darkstat -i wlp3s0 --debug
error: illegal argument: "--debug"
darkstat 3.0.719 (using libpcap version 1.7.4)
user@tommy:~$ sudo darkstat -i
Try: sudo darkstat -i eth0 --debug
The error message could be better, but it's saying there's no interface
called "--debug", which was the argument to -i.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
