Skip to content

/dev/ppp not openable in 2.2.x (regressed from 2.1.3) — breaks pppd/openfortivpn #2528

Closed as not planned

Description

@jannes-m

Since 2.2.0, opening /dev/ppp (char major 108) fails with EPERM inside machines — even as root, even in a --privileged container. /dev/net/tun is unaffected. This breaks pppd/openfortivpn; worked on 2.1.3.

Repro (no VPN needed):

docker run --rm --privileged alpine sh -c \
  'mknod /dev/ppp c 108 0 2>/dev/null; (exec 3<>/dev/ppp) && echo OK || echo EPERM'
  • 2.1.3 (20115, kernel 7.0.5) → OK
  • 2.2.1 (20628, kernel 7.0.11) → EPERM

mknod succeeds but the open is denied — looks like the cgroup v2 device allowlist dropped major 108. Plausibly the 2.2.0 "Security improvements to the kernel" change.

Confirms the VPN break: standalone pppd on 2.2.1 prints Couldn't open the /dev/ppp device: Operation not permitted / Sorry - this system lacks PPP kernel support, exit 4 — matching openfortivpn's log exactly. Fine on 2.1.3.

Env: macOS 26.5.1, Apple Silicon.

Ask: re-allow /dev/ppp (or make it opt-in, like tun)? Workaround: downgrade to 2.1.3, or use a tun-based client (FortiClient / openconnect --protocol=fortinet).

Activity

  1. jannes-m commented on Jun 10, 2026

    @jannes-m
    Author

    Duplicate of #2524 (same /dev/ppp EPERM regression in 2.2.x). Closing in favor of that one; added the Docker repro + privileged-container finding there.

  2. added this to the v2.2.2 milestone on Aug 3, 2026
  3. kdrag0n commented on Aug 3, 2026

    @kdrag0n
    Member

    Fixed in v2.2.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions