Skip to content

Failed to configure: WireGuard error: Netlink error: Netlink payload error: No such device #354

Description

@dburianov

I have 2 similar instalation. All run in docker compose. 1 instance with all servers(gateway, core, proxy, nginx) and 2 instances with gateway only.

Maybe after 24 hours after start gateway, I see in gateway logs:

2026-07-24T06:08:01.813671Z  INFO defguard_gateway::gateway_server: message=Defguard Core gRPC client connected from 11.22.33.44:57446 log.target=defguard_gateway::gateway_server log.module_path=defguard_gateway::gateway_server log.file=src/gateway_server.rs log.line=162
2026-07-24T06:08:01.813705Z  INFO core_communication: defguard_gateway::version: message=Defguard Core version 2.0.2+f74086e is supported log.target=defguard_gateway::version log.module_path=defguard_gateway::version log.file=src/version.rs log.line=22 [2.0.2][C:2.0.2+f74086e]
2026-07-24T06:08:01.813730Z  INFO core_communication: defguard_gateway::gateway_server: message=Requesting network configuration from 11.22.33.44:57446 log.target=defguard_gateway::gateway_server log.module_path=defguard_gateway::gateway_server log.file=src/gateway_server.rs log.line=203 [2.0.2][C:2.0.2+f74086e]
2026-07-24T06:08:02.089021Z ERROR defguard_gateway::gateway_server: message=Failed to configure: WireGuard error: Netlink error: Netlink payload error: No such device (os error 19) log.target=defguard_gateway::gateway_server log.module_path=defguard_gateway::gateway_server log.file=src/gateway_server.rs log.line=227 [2.0.2 Debian 13.0.0 x86_64]
2026-07-24T06:08:21.399806Z ERROR defguard_gateway::gateway: message=Failed to retrieve WireGuard interface statistics: Netlink error: Netlink payload error: No such device (os error 19) log.target=defguard_gateway::gateway log.module_path=defguard_gateway::gateway log.file=src/gateway.rs log.line=618 [2.0.2 Debian 13.0.0 x86_64]

logs from core container:

core-1     | 2026-07-24T06:08:01.842025Z  INFO defguard_gateway_manager::handler: message=Connected to Defguard Gateway http://88.77.66.55:50066/
core-1     | 2026-07-24T06:08:01.842060Z  INFO defguard_gateway_manager::handler: message=Received message from Gateway.
core-1     | 2026-07-24T06:08:02.079936Z  INFO defguard_gateway_manager::handler: message=Configuration sent to Gateway(ID 9; URL 88.77.66.55:50066), network [ID 4] Infra
core-1     | 2026-07-24T06:08:02.080028Z  INFO defguard_gateway_manager::handler: message=Sent configuration to Gateway(ID 9; URL 88.77.66.55:50066)
core-1     | 2026-07-24T06:08:02.582266Z  INFO proxy_bidi: defguard_gateway_manager::handler: message=Starting update stream to gateway: Infra, network [ID 4] Infra [2.0.2][PX:2.0.2+322ac3f]
core-1     | 2026-07-24T06:08:04.357826Z  INFO defguard_gateway_manager::handler: message=Received message from Gateway.

after this system lost WG interface. For fix it I need stop and start container.

One feature, this problem only on remote gateways. Gateway, that run in one docker compose with other services, does not have this problem.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status
Ready to release

Relationships

None yet

Development

No branches or pull requests

Issue actions