Did I set up the service incorrectly?

[isaaclw]

I'm running:

$ uname -a
Linux ohm 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux
$ cat /etc/debian_version 
12.8

Currently the service is running:

● snap.friendly-neighbor.friendly-neighbor.service - Service for snap application friendly-neighbor.friendly-neighbor
     Loaded: loaded (/etc/systemd/system/snap.friendly-neighbor.friendly-neighbor.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-12-26 22:58:14 EST; 2 days ago
   Main PID: 54587 (friendly-neighb)
      Tasks: 2 (limit: 762)
        CPU: 3.079s
     CGroup: /system.slice/snap.friendly-neighbor.friendly-neighbor.service
             ├─54587 /bin/sh /snap/friendly-neighbor/14/bin/friendly-neighbor-wrapper
             └─54647 /snap/friendly-neighbor/14/bin/friendly-neighbor -i eth0 --mappings "74:D0:2B:9D:E9:E7,192.168.1.70 8C:89:A5:11:5B:05,192.168.1.31"

Dec 26 22:58:14 ohm systemd[1]: Started snap.friendly-neighbor.friendly-neighbor.service - Service for snap application friendly-neighbor.friendly-neighbor.
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Active IPv4/ARP mappings:
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO]   192.168.1.70 -> 74:d0:2b:9d:e9:e7
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO]   192.168.1.31 -> 8c:89:a5:11:5b:5
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Starting Friendly Neighbor v0.6.0...
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Listening on interface eth0...

I mean to map:

74:D0:2B:9D:E9:E7 <->  192.168.1.70
8C:89:A5:11:5B:05 <-> 192.168.1.31

'Wakeonlan's work. I used it periodically (and do now too) to autosuspend and wake up periodically.

I would like the system to be a bit more seemless, though.

I must have missed a step with install.

I have not seen the service, friendly neighbor, do anything. Is there something I'm supposed to install along side it? Do I need to install the 'arp_standin'

This post suggested arp_standin, but said it was outdated. I don't see anything I missed here.

[danielpgross]

Hi @isaaclw, everything here looks fine. You should now be able to wake up the server machines using regular unicast packets instead of WoL packets. Is that working?

[isaaclw]

The service doesn't seem to do anything. There's been no output since I started it up, so I'm not sure how to debug the issue

● snap.friendly-neighbor.friendly-neighbor.service - Service for snap application friendly-neighbor.friendly-neighbor
     Loaded: loaded (/etc/systemd/system/snap.friendly-neighbor.friendly-neighbor.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-12-26 22:58:14 EST; 1 month 13 days ago
   Main PID: 54587 (friendly-neighb)
      Tasks: 2 (limit: 762)
        CPU: 49.590s
     CGroup: /system.slice/snap.friendly-neighbor.friendly-neighbor.service
             ├─54587 /bin/sh /snap/friendly-neighbor/14/bin/friendly-neighbor-wrapper
             └─54647 /snap/friendly-neighbor/14/bin/friendly-neighbor -i eth0 --mappings "74:D0:2B:9D:E9:E7,192.168.1.70 8C:89:A5:11:5B:05,192.168.1.31"

Dec 26 22:58:14 ohm systemd[1]: Started snap.friendly-neighbor.friendly-neighbor.service - Service for snap application friendly-neighbor.friendly-neighbor.
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Active IPv4/ARP mappings:
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO]   192.168.1.70 -> 74:d0:2b:9d:e9:e7
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO]   192.168.1.31 -> 8c:89:a5:11:5b:5
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Starting Friendly Neighbor v0.6.0...
Dec 26 22:58:15 ohm friendly-neighbor.friendly-neighbor[54647]: [INFO] Listening on interface eth0...

[isaaclw]

Based on the limited configuration it seems like almost any network request on the target machines:

• 192.168.1.31
• 192.168.1.70
  should wake them up, but it seems like nothing does.

Perhaps I have something set up on my firewall (which is a separate host) that is preventing this?