Page MenuHomeVyOS Platform

wireguard - Interface wg01 could not be brought up in time
Closed, ResolvedPublicBUG


[ interfaces wireguard wg01 ]
Interface wg01 could not be brought up in time ...

ip a l dev wg01
6: wg01: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    inet scope global wg01
       valid_lft forever preferred_lft forever
interface: wg01
  public key: ucYbVoJodRE6QtKjEJOppB6rcoMAfC6wanfgGdff1g8=
  private key: (hidden)
  listening port: 12345

peer: LrSToNEmCOP8kMsyZs3wzm7jyKJzQFtOIBLuyluynSo=
  allowed ips:
  latest handshake: 34 seconds ago
  transfer: 604 B received, 692 B sent

So, the tunnel is up and working. Vyos shows it as up as well.

set and del disable the interface takes quite some time and shows the same error messages, which is in reality no issue at all.


Difficulty level
Easy (less than an hour)
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

@cpo operstate will be unknown for wg interfaces, I think it's the only interface type having unknown. Anything else should be up or down, I think. I can re-implement with the wg class if that's better.
Let me know what you think, wg is working with no issues, so functionality isn't an issue here.

hagbard triaged this task as Normal priority.Oct 10 2019, 10:40 PM
hagbard changed Difficulty level from Unknown (require assessment) to Easy (less than an hour).

I‘d simply override the set_state() function in derived WireGuard Class without that check. If more interface have this (possibly VXLAN) it could be added to baseclass with a flag that the particular code is not executed.

I‘d add it as a flag in base class as we never know what thw other interfaces like l2tpv3 bring.

erkin set Issue type to Bug (incorrect behavior).Aug 31 2021, 6:38 PM