Discussion:
Unable to get arpwatch to work in my brand new Debian bullseye v11.3 install...
(too old to reply)
Ant
2022-05-14 01:30:04 UTC
Permalink
Hello.

I finally installed a brand new Debian bullseye v11.3 into my 13 yrs.
old PC since my Jessie v8 was just too old and needed to start clean.
I'm having problems getting arpwatch to start:

# /etc/init.d/arpwatch start
Starting arpwatch (via systemctl): arpwatch.service.
# /etc/init.d/arpwatch status
??? arpwatch.service - arpwatch service
Loaded: loaded (/lib/systemd/system/arpwatch.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2022-05-13 18:00:38 PDT; 4min 8s ago
Docs: man:arpwatch(8)
Process: 1749270 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1749270 (code=exited, status=0/SUCCESS)
CPU: 2ms

May 13 18:00:38 Debian2022 systemd[1]: Starting arpwatch service...
May 13 18:00:38 Debian2022 systemd[1]: Finished arpwatch service.

It seems like arpwatch changed stuff since then. I don't even see an arp.dat file. Am I missing something?

Thank you for reading and hopefully answering soon. :)
--
Friday the 13th! :O Will it be quiet too? So far, it is even though getting hot. Still aching like the left foot with its ankle.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )
Joe Beanfish
2022-05-17 15:16:07 UTC
Permalink
Post by Ant
Hello.
I finally installed a brand new Debian bullseye v11.3 into my 13 yrs.
old PC since my Jessie v8 was just too old and needed to start clean.
# /etc/init.d/arpwatch start
Starting arpwatch (via systemctl): arpwatch.service.
# /etc/init.d/arpwatch status
??? arpwatch.service - arpwatch service
Loaded: loaded (/lib/systemd/system/arpwatch.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2022-05-13 18:00:38 PDT; 4min 8s ago
Docs: man:arpwatch(8)
Process: 1749270 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1749270 (code=exited, status=0/SUCCESS)
CPU: 2ms
May 13 18:00:38 Debian2022 systemd[1]: Starting arpwatch service...
May 13 18:00:38 Debian2022 systemd[1]: Finished arpwatch service.
It seems like arpwatch changed stuff since then. I don't even see an arp.dat file. Am I missing something?
Thank you for reading and hopefully answering soon. :)
Looks like you have to do some setup for your interface(s). See
https://www.mybluelinux.com/arpwatch-monitor-mac-addresses-change/
Ant
2022-05-17 22:46:32 UTC
Permalink
Post by Joe Beanfish
Post by Ant
Hello.
I finally installed a brand new Debian bullseye v11.3 into my 13 yrs.
old PC since my Jessie v8 was just too old and needed to start clean.
# /etc/init.d/arpwatch start
Starting arpwatch (via systemctl): arpwatch.service.
# /etc/init.d/arpwatch status
??? arpwatch.service - arpwatch service
Loaded: loaded (/lib/systemd/system/arpwatch.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2022-05-13 18:00:38 PDT; 4min 8s ago
Docs: man:arpwatch(8)
Process: 1749270 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1749270 (code=exited, status=0/SUCCESS)
CPU: 2ms
May 13 18:00:38 Debian2022 systemd[1]: Starting arpwatch service...
May 13 18:00:38 Debian2022 systemd[1]: Finished arpwatch service.
It seems like arpwatch changed stuff since then. I don't even see an arp.dat file. Am I missing something?
Thank you for reading and hopefully answering soon. :)
Looks like you have to do some setup for your interface(s). See
https://www.mybluelinux.com/arpwatch-monitor-mac-addresses-change/
Thanks. It's sure different from older versions. :O
--
Nice cooler weather now on a quiet Tuesday? Celtics have better get burned by Miami Heat!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )
Loading...