Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-84185

Cannot make WireGuard connection as a client

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Undefined Undefined
    • None
    • CentOS Stream 10
    • wireguard-tools
    • None
    • Yes
    • None
    • rhel-net-core
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      I attempted to establish a WireGuard connection as a client.

      What is the impact of this issue to you?

      This issue prevents me from establishing a WireGuard connection as a client, which disrupts my network connectivity.

      Please provide the package NVR for which the bug is seen:

      This issue started occurring with kernel version 6.12.0-54.el10 and persists in the following versions:

      • 6.12.0-54.el10
      • 6.12.0-56.el10
      • 6.12.0-58.el10
      • 6.12.0-59.el10
      • 6.12.0-63.el10

      How reproducible is this bug?: Steps to reproduce

      1. Set up a WireGuard server on a CentOS Stream 9 system.
      2. Configure a WireGuard client on a CentOS Stream 10 system.
      3. Boot the CentOS Stream 10 client with a kernel version of 6.12.0-54.el10 or later.

      Expected results

      A successful WireGuard connection should be established.

      Actual results

      The WireGuard connection fails. The wg show command indicates that no packets are being received.

              haliu@redhat.com Hangbin Liu
              routis0617 인상 류 (Inactive)
              Hangbin Liu Hangbin Liu
              Jian Liu Jian Liu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: