Closed Marctraider closed 2 years ago
I dont think i had any messages from the particular interface at all in the logs, just reflecting what I did on the engarde web interface
My bad, I'll open a new issue once it happens again to confirm, maybe it's my aging SBC.
Hello @Marctraider , thanks for the issue, it looks quite strange since the inclusion logic is the same for the UI visualization and for the transmission logic, but I will have a look at it. The (slower than I'd want) refactor will totally replace the way it works, by the way: it will be event-based and so it will for sure work in a more reliable way.
Thanks
Maybe it was an edge case or maybe it was something on my Debian, but I didn't touch anything OS/network level other than re-exclude/include and it magically started receiving packets again :)
Either way, all works great in general ^^
Maybe it was an edge case or maybe it was something on my Debian, but I didn't touch anything OS/network level other than re-exclude/include and it magically started receiving packets again :)
Either way, all works great in general ^^
Are you using keepalive on the wireguard interface? If so how many seconds?
Hi! Just noticed (maybe) a small bug, not exactly sure.
I excluded an interface yesterday and an hour later re-included it.
Now i look today it was included but says xxxxx seconds not received any data (basically 12 ish hours or so), so i excluded and reincluded it just now and it just works fine again instantly.
Maybe there is some small bug that not always properly saves the new state though the API?