-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wg Tunnelblockade #100
Comments
Debug output from today: The Situation
UFU-FWH-E106-Woermannstr-Technik1wg show on UFU-FWH-E106-Woermannstr-Technik1
Outbound on UFU-FWH-E106-Woermannstr-Technik1 wireguard interface
Inbound on UFU-FWH-E106-Woermannstr-Technik1 wireguard interface
sn10wg show on sn10
Inbound on wireguard interface of sn10(No packets appear here.)
Outbound on wireguard interface on sn10
|
Currently, it seems that only handshakes are sent out at UFU-FWH-E106-Woermannstr-Technik1:
And all of them seem to appear on sn10:
|
It also doesn't seem to be related to the vxlan traffic that we are sending into the wg interface. If we do a normal ping, we can also just see the handshakes on br-wan:
wg show still shows a valid handshake:
|
Here is the config dump from UFU-FWH-E106-Woermannstr-Technik1:
|
Also, the TX counter of wireguard shows that packets are not sent out (second last column):
Only 92 bytes are seen in 15 seconds only. This is excactly the size of one handshake packet. |
Also an inbound trace on UFU-WFH-E106-Technik1 on br-wan:
|
I just found this in dmesg:
Not sure if this is related, since this happened 15 days ago. |
Listening on any interface, also just shows the handshakes:
I suppose every handshake is shown three times, since I have a linux bridge (or so):
Unfortunately, the tcpdump doesn't show the interfaces where it saw the packets. |
Todays debugging session showed, that the direction of "its not working vs. its working" may be interchanged, too. Today it was not possible to ping fe80::1%wg_mesh. tcpdump showed that the reply packet is withdrawn somewhere on the way back from the supernode. |
From today's debug session: https://pad.leinelab.org/mKN6BNbHRIi5J7GPChw2FQ Especially interesting thereby:
^ RX Packet increases every 30 seconds by 1 packet.
=> Firewall sees approx 29.5 packets/s |
If this is seen the next time on a supernode (where the supernode get's deaf), please execute:
And capture logs using journalctl... I just checked on sn10, that this should work. On the gluon nodes, this doen't work, because we do not have debug within wireguard there. |
Symptoms:
Resulting symptoms:
See from:
Actions taken so far:
(Edit by @lemoer: translated using deepl to english)
The text was updated successfully, but these errors were encountered: