Thanks @lurker888
I make the assertion that "no attempt is made" on all of the following:
- nothing in the system log (see log config and search examples below)
- in WinBox and at CLI /interface/wireguard/peer/print detail never show any last-handshake
- /tool/sniffer captures, looking at wg1, or looking at no filters at all except for filter-port=${MikroTik4 WireGuard listener port}, which never captures anything at all except my traceroutes or pings to generate traffic that should cause the tunnel to come up, and that shows only MikroTik3G's own ICMP packets being transmitted on wg1 (so, there are routes which will send data out via a WireGuard peer), but causes absolutely no other traffic.
Given all this, is it still worth trying to capture the WireGuard handshakes/initiation in mangle? Or, as I think, have these other ways of looking for the handshakes/initiation sufficietly demonstrated that It's Just Not Happening Like It Should?
thanks,
Jay
system logging config:
[admin@MikroTik3B] > /system/logging/print where topics~"wireguard" and disabled=no
Columns: TOPICS, ACTIONTOPICS ACTION
1 ppp memory
wireguard
debug
packet
info
warning
bridge
discover
interface
Nothing in the system log:
[admin@MikroTik3B] > /log print where topics~"wireguard" or topics~wireguard or message~"wg1" or message~"wireguard" or message~"WireGuard"
2026-08-20 04:05:53 interface,info wg1 link up
I'm actually surprised to see even this one "wg1 link up" entry but I'm fairly sure that's when I had tested completely deleting and re-creating the WireGuard interface and peers, so, it is not any indication of any peer connection attempt.