FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
111 views 1 comments
by anonymous
Hello,

For a wireguard interface used as initiator only there is no requirement to set a fixed listen_port any value will do. The UI sets it to 51820 by default and a failure is assured if there is more than one such interface.

Simple solution: don't output a "option listen_port '51820'" if the field is not set by the user in the UI.

Regards,

1 Answer

0 votes
by anonymous

Hello,

Thank you for this suggestion. 

It has been forwarded to the developers. However, be aware that, unless they are critical, suggestions from this forum usually take a longer time to implement. For example, your previous suggestion is still open and has no definite time line, when it will be completed.

Suggestions are always welcome, just keep in mind that their consideration and development will most likely take some time.

Best regards,

by anonymous

Thank you, I have refined the script since:

  • no need to restart the full network stack, only the relevant wg interface,
  • works even if the interface has never been established,
  • works with psk.

Better than the default /usr/bin/wireguard_watchdog.