-
Notifications
You must be signed in to change notification settings - Fork 70
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
Packets block happens on writing to wireguard device by udp protocol exceeds 30 packets/sec #114
Comments
More tests has been done
|
Hi. I'm also using EdgeRouter X and faced a similar issue. From a client computer which connected to EdgeRouter's WireGuard server, I could browse web sites such as YouTube, but the video playback is very slow. When I inspect the packet flow with Wireshark, it seems that YouTube first sends me the video data over UDP. But EdgeRouter dropped these UDP packets. After I waited a while it seemed to fall back to TCP and and I was able to play the video. Note: the link above points to the hwnat issue. When I disabled my EdgeRouter's hwnat, the issue no longer occurred. However, the EdgeRouter's performance will drop significantly... |
@yukinobu Was it UDP over port 443(aka QUIC)? You might be able to just block QUIC outright so it never uses that and see if it improves the experience? |
@jbeez Yes, it seemed QUIC. Now, I blocking all egress UDP packets and it improves my experience definitely! Below is a snippet of my NAT rules. For packets from WireGuard tunnels, only TCP and ICMP are handled by NAT.
|
Package version
1.0.20211208-1
Firmware version
v2.0.9-hotfix.2
Device
EdgeRouter X (SFP) - e50
Issue description
My network connection looks like
'''
Server[192.168.100.18]------Wireguard-------ERX[192.168.100.19/192.168.0.1]-------LAN-------Mac[192.168.0.110]
'''
192.168.100.18/192.168.100.19 is wireguard devices
192.168.0.1/192.168.0.110 is Lan devices
if I run on Server
run on Mac
I got log on Server
Obviously, while udp packets writing to wireguard device exceeds 30p/s, the device blocked writing.
I think something might happens on packet queue located inside wireguard driver.
Other tests been done
Configuration and log output
No response
The text was updated successfully, but these errors were encountered: