Search results

I have changed the txqueuelen of wg1 and eth2 to 8192 and changed the qdisc to fq_codel. It looks like after awhile the qdisc of eth2 is reverted back to the previous value which is mq: Will this flap wg1 interface? Those peers that are connected to this wireguard hub is running traffic, hence...

@CaffeineAddict over the night, I saw we are transmitting more on wg1 interface, and actually I still see TX dropped during that higher traffic. I didn't see packet drop when the traffic is below 50MiB. I am monitoring closely. Also I am not able to get output for ethtool wg1. However it is...

It is because the clients site wg are managed by me as well. TX packet drop is observed on wg interface: Basically we use BGP to exchange the prefixes between each site and hub The txqueuelen was 500 before on wg1 interface, and I just set it to 5000, this stopped the TX dropped in wg1...

@CaffeineAddict thanks for your comment. MTU is configured as default on wg hub and wg clients (1420). We don't configure jumbo MTU on the interfaces. As for default gw, I believe wg is point to point, hence there won't have any gw: Example pinging to 1 of wg client: Example pinging to 1...

@jpnilson it looks like I am getting packet loss pinging to any peer tunnels IP when the TX packet drop is huge on wg interface. I confirm there is no packet drop in eth port that is used to transmit traffic of wg interface. Also I do not see packet loss when pinging the peer public IP...

@GatorsFan thanks for your insight. Actually I am setting it as wireguard hub with just 1 wg interface to provide connectivity to more than 80 peers. Do you think it is causing issue? From my observation, it looks to be traffic/throughput related.

Hi guys, Have you guys encountered transmit packet drop on wireguard interface? I have been trying to look around for the reason online, but I don't see a concrete cause. I am running Linux 10/buster. I use default wireguard mtu which is 1420. I have about 80 wireguard peers. From my testing...