Skip to content

Keepalive signal to wireguards peer does not follow the setting #9636

@NeverBeenHere999

Description

@NeverBeenHere999

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

Setting any value in "keepalive interval" in the wireguard peer does not change the timing (according to the wireguard log).
I itred to use: empty box, maximum value 65535 and maximum value-1 = 65534

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)

To Reproduce

Try change this setting and double check the behaviour in the wireguard log.

Expected behavior

To follow the setting and to have no keepalive signals in case of empy setting (no number specified)

Describe alternatives you considered

none

Screenshots

If applicable, add screenshots to help explain your problem.

Relevant log files

If applicable, information from log files supporting your claim.

Additional context

Add any other context about the problem here.

Environment

Software version used and hardware type if relevant, e.g.:

Version | 25.7.11_2 |  
Architecture | amd64 |  
Commit | 9bcc481 |  
Mirror | https://pkg.opnsense.org/FreeBSD:14:amd64/25.7 |  
Repositories | OPNsense (Priority: 11), mimugmail (Priority: 5) |  

Metadata

Metadata

Assignees

No one assigned

    Labels

    supportCommunity support or awaiting triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions