Arch Linux User Repository

updated to latest version : 2024.6.497-1

it seems to keep revering? i think out of date, is there a reason for this? cloudflare-warp-bin: local (2024.6.497-1) is newer than AUR (2024.4.133-2) on yay -Syu

cannot connect to cloudflare, anyone know how to solve ?

❯ warp-cli connect
Success
❯ warp-cli status
Status update: Disconnected. Reason: Manual Disconnection
Success

@username13 if you have libpcap.so simply adding symlink would solve the issue $ ln -s libpcap.so libpcap.so.0.8

warp-dex: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory

not sure how to that @brianwo im not that bright, however i think i can help another method

I have this in my .zshrc

# export completion cli to fpath
fpath=($HOME/.completion_zsh $fpath)

that way if i do warp-cli generate-completions zsh > .completion_zsh/_warp-cli then i exec zsh i can have the completions

Can we add shell completion directly to the package? There are completions for bash, elvish, fish, powershell, and zsh built-in to the executable (warp-cli generate-completions). The completion code is rather long >6000 lines.

okay i've update the source to jammy @klosentag, thx for the input appreciate it

@Neomax7 @dhupee Hey guys can you change the ubuntu distro to jammy? It might be better because it's linked to a newer glibc

diff --git a/PKGBUILD b/PKGBUILD
index e72df36..19248b6 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -20,7 +20,7 @@ conflicts=('cloudflare-warp')

 # Function to get latest version from repository
 get_latest_version() {
-    curl -s https://pkg.cloudflareclient.com/dists/focal/main/binary-amd64/Packages \
+    curl -s https://pkg.cloudflareclient.com/dists/jammy/main/binary-amd64/Packages \
     | grep -E -o 'Version: [0-9]+\.[0-9]+\.[0-9]+' \
     | head -n1 \
     | grep -E -o '[0-9]+\.[0-9]+\.[0-9]+'
@@ -35,9 +35,9 @@ if [[ "$pkgver" != "$latest_version" ]]; then
 fi

 source=(
-    "${pkgname}-${pkgver}-x86_64.deb::https://pkg.cloudflareclient.com/pool/focal/main/c/cloudflare-warp/cloudflare-warp_${pkgver//-/_}-1_amd64.deb"
-    "${pkgname}-${pkgver}-${pkgrel}-Release::https://pkg.cloudflareclient.com/dists/focal/Release"
-    "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::https://pkg.cloudflareclient.com/dists/focal/main/binary-amd64/Packages"
+    "${pkgname}-${pkgver}-x86_64.deb::https://pkg.cloudflareclient.com/pool/jammy/main/c/cloudflare-warp/cloudflare-warp_${pkgver//-/_}-1_amd64.deb"
+    "${pkgname}-${pkgver}-${pkgrel}-Release::https://pkg.cloudflareclient.com/dists/jammy/Release"
+    "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::https://pkg.cloudflareclient.com/dists/jammy/main/binary-amd64/Packages"
 )

 md5sums=('SKIP'

Hi everyone,

I had some issues with CF warp not able to start due to various problems, including not being able to initialize firewall or access the local DNS resolver (it wanted to overwrite the existing /etc/resolv.conf which is obviously protected.

I have not found any solutions elsewhere so decided to share a solution myself (credits go to my colleague Atte :) ).

• Create a file override.conf in /etc/systemd/system/warp-svc.service.d with the following contents:

[Unit]
After=network.target

[Service]
TemporaryFileSystem=/etc /usr/bin
BindPaths=/etc/warp/resolv.conf:/etc/resolv.conf
BindReadOnlyPaths=/etc/warp/nsswitch.conf:/etc/nsswitch.conf /usr/bin/warp-svc /usr/bin/nft /usr/bin/resolvectl

User=warp-svc
Group=warp-svc
DynamicUser=yes

AmbientCapabilities=
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
CapabilityBoundingSet=
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
DeviceAllow=/dev/net/tun
DevicePolicy=closed
LockPersonality=yes
MemoryDenyWriteExecute=yes
ProcSubset=pid
ProtectClock=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectHostname=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectProc=invisible
Restart=no
RestrictAddressFamilies=AF_INET AF_INET6 AF_NETLINK AF_UNIX
RestrictNamespaces=yes
RestrictRealtime=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
SystemCallFilter=~@privileged @resources

[Install]
WantedBy=default.target

• Create a directory /etc/warp and put a copy of /etc/resolv.conf there with the owner set to the warp-svc user. Also, put there a nsswitch.conf file with the following contents (just copying for what it's worth):

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files systemd
gshadow: files systemd

publickey: files

hosts: hosts: dns [!UNAVAIL=return] files

networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

• These steps should help run warp-svc successfully!