What's new

Wgclient-start or stop not being called

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Weblee2407

Regular Contributor
WireGuard is noticeably faster than OVPN but I can’t seems to get any of the notifications of a client connecting using the wgclient
scripts. Wgservice works but not even a ripple in the logs when a client connects. Are these scripts for site to site connects and disconnects? Is there anyway to detect when a phone or pc WG client connects?
 
WireGuard is noticeably faster than OVPN but I can’t seems to get any of the notifications of a client connecting using the wgclient
scripts.
I think that the wgclient-start/stop is called when the firmware client start/stops. not used for firmware server clients.
 
Why doesn’t WG think someone would want to know when a connection is made or terminated
 
Why doesn’t WG think someone would want to know when a connection is made or terminated
Because WG in its design is a connection-less technology. There is no concept of connecting or disconnecting. Either the two ends can communicate with one another, or they can't.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top