search

gravitl / netmaker

Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
https://netmaker.io
Other
9.4k stars 547 forks source link

[Bug]: junk routes left behind when 2nd network is removed from a client #2220

Open skandragon opened 1 year ago

skandragon commented 1 year ago

Contact Details

No response

What happened?

I added a host to a network called "flame" which uses IPv4 space 10.30.0.0/20, and the "netmaker" interface gets a 10.30.0.2 address. I later added it to one called "colo" with IPv4 space 10.31.0.0/20, and the "netmaker" interface changes to 10.31.0.2.

When I remove the "colo" network through the UI from this host, I am left with a junk route:

root@iot:~# ip route
10.30.0.0/20 dev netmaker proto kernel scope link src 10.30.0.2
10.31.0.1 dev netmaker
10.31.0.2 dev netmaker

Version

v0.18.5

What OS are you using?

Linux

Relevant log output

No response

Contributing guidelines

mattkasun commented 1 year ago

can you verify the versions of netmaker and netclient you are using. Cannot duplicate behaviour on v.0.18.5

bpmarine commented 1 year ago

I'm seeing the same on Linux and Windows while testing v18. I have loads of junk routes from various networks I have tried and later deleted still showing and causing a lot of connection issues. I didn't notice this until I added a second egress gateway to another site. All clients are 18.6