search

wiktorbgu / amneziawg-mikrotik

AmneziaWG client and server on Mikrotik container
https://hub.docker.com/r/wiktorbgu/amneziawg-mikrotik
10 stars 0 forks source link

(discuss) Some issues in logs #3

Open zarv1k opened 4 days ago

zarv1k commented 4 days ago

Hi!

First of all thank you for the working solution and for your docs about how to set it up.

Although I have had a working configuration in client mode there are some of log entries that I'm worried about (winbox logs screenshot attached) like the following:

Error: Unknown device type.

What is that? Should that be fixed?

[!] Missing WireGuard (Amnezia VPN) kernel module. Falling back to slow userspace implementation.

Is that ok? Why it logs that anyway even when everything works well? I suppose that is not normal and according to the log message there could be some performance issues.

Running amneziawg-go is not required because this ...

There is notice box in logs that amneziawg-go is not required. What about that? Should that be fixed?

Service hwdrivers' needs non existent servicedev' Service machine-id' needs non existent servicedev'

Are that logs not really critical and we should just not pay attention on them?

Спасибо

Screenshot 2024-11-13 at 10 07 07
wiktorbgu commented 10 hours ago

All the errors with AmneziaWG are related to the fact that this protocol is not implemented on Mikrotik devices, so the solution is used through a container. Errors with dev are most likely related to the implementation of containerization on Mikrotik. All these errors do not prevent this solution from working and there is nothing to worry about.

Пожалуйста)