You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a wireguard setup on debian as a headend where about 4 nodes connect in. I'm using all IPv6 here. I setup two fping6 probes.
My Probes file has + FPing6 at the top with just the path to the binary defined, then underneath at the ++ level I have an FPing6Normal and an FPing6wg.
Problem: The FPing6Normal hosts in my Targets file are not generating a graph for remote hosts, but I can manually run the FPing6 binary with -S and the value I assigned to sourceaddress successfully.
It is generating a graph for the local machine itself, which isn't super useful to me but that is working for FPing6. I saw another issue in github here asking for a source interface instead, that would also be useful here as my public ipv6 address is subject to change.
In Targets, I even tried to define probe = FPing6Normal immediately before every host =, but no change in behavior.
The text was updated successfully, but these errors were encountered:
Did some debugging today, turns out the issue was related to packet sizes. I could send full 5000 byte packets inside WG tunnels, but I was limited outside of it
I have a wireguard setup on debian as a headend where about 4 nodes connect in. I'm using all IPv6 here. I setup two fping6 probes.
My Probes file has + FPing6 at the top with just the path to the binary defined, then underneath at the ++ level I have an FPing6Normal and an FPing6wg.
Problem: The FPing6Normal hosts in my Targets file are not generating a graph for remote hosts, but I can manually run the FPing6 binary with -S and the value I assigned to sourceaddress successfully.
It is generating a graph for the local machine itself, which isn't super useful to me but that is working for FPing6. I saw another issue in github here asking for a source interface instead, that would also be useful here as my public ipv6 address is subject to change.
In Targets, I even tried to define probe = FPing6Normal immediately before every host =, but no change in behavior.
The text was updated successfully, but these errors were encountered: