Package Details: perimeter81 10.0.5.962-1

Git Clone URL: https://aur.archlinux.org/perimeter81.git (read-only, click to copy)
Package Base: perimeter81
Description: Perimeter81 agent application
Upstream URL: https://support.perimeter81.com/docs/downloading-the-agent
Licenses: custom:LICENSE
Submitter: mikeroll
Maintainer: ttrmw (sgrue)
Last Packager: sgrue
Votes: 5
Popularity: 0.012354
First Submitted: 2021-10-01 15:02 (UTC)
Last Updated: 2026-02-26 08:38 (UTC)

Latest Comments

1 2 3 4 Next › Last »

Margual56 commented on 2026-03-02 15:10 (UTC)

First of all: Thanks for maintaining this package!

Latest version dumps a core. I use up-to-date plain ol' Arch with everything "normal" (systemd, kde, etc).

Previous version had been working fine for months, and continues to work (I downgraded this AUR package, and it still works).

Am I the only one?

ttrmw commented on 2025-07-30 12:33 (UTC) (edited on 2025-07-30 12:33 (UTC) by ttrmw)

Heya sgrue, yes that would be great - I have been forced off arch at work so no longer use p81 on our glorious distro :(

I have added you as co-maintainer, feel free to remove me or not

sgrue commented on 2025-07-29 09:18 (UTC)

Hi ttrmw, I'm interested in helping maintain this package. If you're open to adding a co-maintainer or no longer wish to maintain it, please let me know. Thanks!

ufo_driver commented on 2025-07-21 10:28 (UTC)

As for the network configuration I double checked what else DEB and RPM packages are installing. We are missing couple of scripts in current package (I've edited paths accordingly).

/etc/NetworkManager/dispatcher.d/50-perimeter81

#!/bin/bash -e
if [[ $1 == "tun0" ]]; then 
  exit 0
fi
if [[ $1 == "ipsec0" ]]; then 
  exit 0
fi
if [[ $1 == "p81" ]]; then 
  exit 0
fi

logger -s "P81 INTERFACE $1 $2"

case "$2" in
  up)
    /opt/Perimeter81/artifacts/daemon-creator network-interface-up
    ;;
  down)
    /opt/Perimeter81/artifacts/daemon-creator network-interface-down
    ;;
esac

/usr/lib/systemd/system-sleep/perimeter81

#!/bin/sh
case $1/$2 in
  post/*)
    /usr/bin/p81-helper-daemon-creator system-resume
    ;;
  pre/*)
    /usr/bin/p81-helper-daemon-creator system-sleep
    ;;
esac

/etc/sudoers.d/perimeter81 (really not sure about this one)

# Perimeter81 Start
ALL ALL=NOPASSWD: /opt/Perimeter81/artifacts/daemon
ALL ALL=NOPASSWD: /opt/Perimeter81/artifacts/daemon-creator
# Perimeter81 End

ShaiAvr commented on 2025-04-11 14:02 (UTC)

I am also having issues with this package. For starters, the network configuration gets messed up after killing the service, so the network service must be restarted. But more importantly, if I try to reboot my system while the service is running, it gets stuck on a black screen saying "The system will reboot now!", which forces me to physically power off the computer and power it back on. I added @ufo_driver's code to perimeter81helper.service, but the problems persist.

sgrue commented on 2025-04-03 07:07 (UTC)

Another remark: Once started I cannot stop the perimeter81helper service anymore, I need to kill it. Afterwards the network (DNS) configuration seems to be messed up, as no network connections work anymore until the network service is restarted.

sgrue commented on 2025-03-20 08:13 (UTC) (edited on 2025-03-20 08:14 (UTC) by sgrue)

Nice, this time it works for me (using Manjaro)! I just installed the package and had to start the perimeter81helper service:

systemctl start perimeter81helper

thx!

ufo_driver commented on 2025-03-18 22:45 (UTC) (edited on 2025-03-18 22:46 (UTC) by ufo_driver)

Added the following into perimeter81helper.service under [Service] section and was able to use it without problems.

ProtectHome=true
ProtectSystem=true
InaccessiblePaths=-/media -/mnt

What it does: hides user home folders from services; mounts /usr as read only; hides any other mounted disks

ufo_driver commented on 2025-03-18 21:14 (UTC)

Got the same problem as other user had with 100% CPU of process named p81daemonhelper after starting service on this version. Started strace on it and looks like this piece of code tries to lstat my whole filesystem. I have a BTRFS with snapshots so I have a lot of files and since service is launched as root - it tries to enumerate all of that, eats CPU and doesn't allow to make connections. We need to somehow restrict perimeter services permissions - maybe launch under a restricted user?

sergeykish commented on 2025-01-28 20:24 (UTC)

GUI displayed after

# systemctl start perimeter81helper

I have not executed /opt/Perimeter81/after-install.sh, briefly checked content.

It copies binaries

cp /opt/Perimeter81/artifacts/daemon-creator /usr/bin/p81-helper-daemon-creator

that monitors sleep /usr/lib/systemd/system-sleep/perimeter81

#!/bin/sh
case $1/$2 in
  post/*)
    /usr/bin/p81-helper-daemon-creator system-resume
    ;;
  pre/*)
    /usr/bin/p81-helper-daemon-creator system-sleep
    ;;
esac

and network /etc/NetworkManager/dispatcher.d/50-perimeter81:

#!/bin/bash -e
if [[ $1 == "tun0" ]] || [[ $1 == "ipsec0" ]] || [[ $1 == "p81" ]]; then 
  exit 0
fi

logger -s "P81 INTERFACE $1 $2"

case "$2" in
  up)
    /usr/bin/p81-helper-daemon-creator network-interface-up
    ;;
  down)
    /usr/bin/p81-helper-daemon-creator network-interface-down
    ;;
esac

And it adds wireguard kernel modules for some old kernels (3.10, 4.18). These modules definitely not needed for Arch:

$ find /lib/modules -iname wireguard
/lib/modules/6.12.10-arch1-1/kernel/drivers/net/wireguard