Arch Linux

newbiehere

Member

Registered: 2020-01-29

Posts: 5

Running ungoogled-chromium causes network lagging & disrupting VPN

Whenever I start ungoogled chromium (installed from AUR) my network goes from

ping gnu.org

64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=48 ttl=53 time=177 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=49 ttl=53 time=126 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=50 ttl=53 time=145 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=51 ttl=53 time=127 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=52 ttl=53 time=144 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=53 ttl=53 time=124 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=54 ttl=53 time=125 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=55 ttl=53 time=156 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=56 ttl=53 time=157 ms

to

ping gnu.org

64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=55 ttl=53 time=156 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=56 ttl=53 time=157 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=57 ttl=53 time=3272 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=58 ttl=53 time=5111 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=59 ttl=53 time=5191 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=60 ttl=53 time=4978 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=61 ttl=53 time=4275 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=62 ttl=53 time=3781 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=63 ttl=53 time=3926 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=64 ttl=53 time=3447 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=65 ttl=53 time=2979 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=66 ttl=53 time=2830 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=67 ttl=53 time=1850 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=68 ttl=53 time=1096 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=69 ttl=53 time=868 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=70 ttl=53 time=2373 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=71 ttl=53 time=3244 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=72 ttl=53 time=3667 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=73 ttl=53 time=3204 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=74 ttl=53 time=2441 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=75 ttl=53 time=2506 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=76 ttl=53 time=2039 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=77 ttl=53 time=1586 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=78 ttl=53 time=1680 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=79 ttl=53 time=2316 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=80 ttl=53 time=2382 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=81 ttl=53 time=2456 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=82 ttl=53 time=2242 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=83 ttl=53 time=3458 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=84 ttl=53 time=5604 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=85 ttl=53 time=5133 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=86 ttl=53 time=4684 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=87 ttl=53 time=3950 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=88 ttl=53 time=2945 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=89 ttl=53 time=3144 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=90 ttl=53 time=5043 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=91 ttl=53 time=4337 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=92 ttl=53 time=5117 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=93 ttl=53 time=6142 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=94 ttl=53 time=6101 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=95 ttl=53 time=7333 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=96 ttl=53 time=8439 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=97 ttl=53 time=9401 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=98 ttl=53 time=10988 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=99 ttl=53 time=12604 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=100 ttl=53 time=12642 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=101 ttl=53 time=12189 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=102 ttl=53 time=11431 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=103 ttl=53 time=11683 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=104 ttl=53 time=12944 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=105 ttl=53 time=12845 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=106 ttl=53 time=11820 ms
64 bytes from wildebeest.gnu.org (209.51.188.148): icmp_seq=107 ttl=53 time=11390 ms

Even after chromium is killed, using the exit button and checking with ps -A | grep chromium, the lag continues!

The lag is not there whenever I do "pkill openvpn" and I get on my regular network, AKA usign a VPN. I can use Firefix without any issues or network lagging / slowing.

I am using PIA VPN, their udp strong config and update-resolv-conf script. No firewall, no crypt-dns, no pi-hole, etc.

Any ideas?

Last edited by newbiehere (2020-01-30 11:27:45)

newbiehere

Member

Registered: 2020-01-29

Posts: 5

Re: Running ungoogled-chromium causes network lagging & disrupting VPN

I solved it by switching to PIA VPN's tcp strong config and changing the DNS to cloudflare, instead of PIA dns!