[BUG] Ping peers

[unknown1818]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi,

I cant ping peers from wireguard container
wg show its connected and handshake succesfull

ip route show table all
i got multiple default route but with different table how i can ping on that?

default dev wg-client table 51820 scope link 
default dev wg-server table 51821 scope link 
default via 172.18.0.1 dev eth0 
10.0.0.0/24 dev wg-server proto kernel scope link src 10.0.0.1 
11.0.0.0/24 dev wg-client proto kernel scope link src 11.0.0.2 
172.18.0.0/16 dev eth0 proto kernel scope link src 172.18.0.3 
local 10.0.0.1 dev wg-server table local proto kernel scope host src 10.0.0.1 
broadcast 10.0.0.255 dev wg-server table local proto kernel scope link src 10.0.0.1 
local 11.0.0.2 dev wg-client table local proto kernel scope host src 11.0.0.2 
broadcast 11.0.0.255 dev wg-client table local proto kernel scope link src 11.0.0.2 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
local 172.18.0.3 dev eth0 table local proto kernel scope host src 172.18.0.3 
broadcast 172.18.255.255 dev eth0 table local proto kernel scope link src 172.18.0.3 

Expected Behavior

No response

Steps To Reproduce

default config

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

default

Container logs

default

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.