Network speeds differ according to boot source

Hardware - Support > Network

(1/3) > >>

stevef:

--- Quote ---How do I mark it as solved?
--- End quote ---

Instructions with pictures at the bottom of this post

https://www.linuxliteos.com/forums/introductions/forum-posting-guidelines/

Earthenware:
After a long and tedious day installing, de-installing and re-installing OSs, I've found the problem (I think).
The short version is that the culprit is the Mullvad VPN client.
The long version is as follows:
I've used four OSs as part of testing: LL 6.6, LL 5.4, Mint and MX.
All OSs work fine when booted from Live USB.
All installed OSs work fine until the Mullvad client is installed.
The Mullvad client screws up every OS.

In all cases except MX, the problem remains even after the Mullvad client is de-installed.
I even regressed to LL 5.4 and an older version of the Mullvad client (which I know to work ok) and found the same problem: LL works fine, Mullvad install screws it up, remove Mulllvad, still screwed.
I know for a fact that some of these combos work on my old computers (e.g. LL 5.4 and old Mullvad client), so I can only assume that the NIC in the new PC is the other factor.
I like Mullvad, so I'm going to take this up with them. Hopefully there's a fix available. If there is, I'll report back here in case anyone else has the same problem.
Until then, I'll mark this thread as SOLVED, although all I've really done is identify the culprit rather than solved the problem.
PS: How do I mark it as solved?

Earthenware:
Sorry, I missed the MX question.

TBH I don't remember whether it happened when booting from USB. I only noticed that it was a problem once installed. I've since re-used the Live USB.

I think next I'm going to try installing the "edge" version of Mint, as it claims to have support for newer hardware (which I still think is the underlying problem here).

stevef:
Can't see anything there. It's possible tracepath might have shown something but I guess you have other network devices working fine which rules out your WAN and ISP leaving us with what's different between the live booted and installed versions.

As you say, this is weird so I'd be really tempted to go back to the freshly installed set up (without firewall, VPN or virtual machine or even updates) and thoroughly check network performance at that point.

I've seen a VPN set up leave hooks in the IP stack which affected network operation even after the VPN had been uninstalled, so don't trust disabling.

--- Quote ---I very much hope that LL hasn't developed an allergy to VMs
--- End quote ---
Not heard any other reports of this nature.

--- Quote ---The Linux Lite updates run at about 20-30kbps, which I would also consider slow (unless LL usually does this now).
--- End quote ---
Yes - if you are getting 20-30kb(it)ps, that would be dial-up slow and isn't 'normal'.

On a 40Mbit/s nominal download connection with a local mirror a recent upgrade to Firefox gave me.

--- Quote ---Fetched 62.8 MB in 14s (4,458 kB/s)
--- End quote ---

4458 kB(ytes) per second is 35Mb(its) per second. so near enough maximum expected.

Can you clear up the point about MX please ?

Earthenware:

--- Quote from: stevef on November 20, 2023, 10:31:49 AM ---Would be interesting to know if youtube videos played as expected before VirtualBox was introduced to the installed system.

Any idea what the tunnel is for ? I guessed at VPN, but is it related to virtual machine ?

Edit to request clarification.
In your original post

--- Quote ---I tried another Llinux version to test this (MX) and the results are the same.
--- End quote ---
I initially read this to mean that MX had the same symptoms - i.e. ok on live, not ok after installation, but it could be read as no difference between installed and live versions of MX. Can you confirm which you meant please ?

--- End quote ---

Network performance was poor before installing any software. I noticed this when downloads of VirtualBox, VPN software were slow. The Linux Lite updates run at about 20-30kbps, which I would also consider slow (unless LL usually does this now).

I think I may have misled when I said "New PC". I should have said "New PC which will run exactly the same software setup as before, with the exception of LL 6.6 (I was on LL 5.x previously). Everything is the same VPN, VirtualBox, Browsers etc etc.

OUTPUTS (VPN disabled and I don't allow pings through my firewall):
ifconfig -a
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.110 netmask 255.255.255.0 broadcast 192.168.8.255
inet6 fd14:de39:dda1:6900:d427:370b:22d8:ef80 prefixlen 64 scopeid 0x0<global>
inet6 fe80::3824:f2d0:1746:2269 prefixlen 64 scopeid 0x20<link>
inet6 fd14:de39:dda1:6900:508a:2581:5bbe:454 prefixlen 64 scopeid 0x0<global>
ether 88:05:69:24:35:f8 txqueuelen 1000 (Ethernet)
RX packets 552508 bytes 747416111 (747.4 MB)
RX errors 50886 dropped 0 overruns 0 frame 50253
TX packets 345427 bytes 58511199 (58.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xb1200000-b1220000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 863 bytes 83528 (83.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 863 bytes 83528 (83.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vboxnet0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.56.1 netmask 255.255.255.0 broadcast 192.168.56.255
inet6 fe80::800:27ff:fe00:0 prefixlen 64 scopeid 0x20<link>
ether 0a:00:27:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 73 bytes 9231 (9.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp1s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether a0:a4:c5:b4:46:41 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ip r
default via 192.168.8.1 dev eno1 proto dhcp metric 100
192.168.8.0/24 dev eno1 proto kernel scope link src 192.168.8.110 metric 100
192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.1 linkdown

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default homerouter.cpe 0.0.0.0 UG 100 0 0 eno1
192.168.8.0 0.0.0.0 255.255.255.0 U 100 0 0 eno1
192.168.56.0 0.0.0.0 255.255.255.0 U 0 0 0 vboxnet0

ip n
192.168.8.1 dev eno1 lladdr 14:de:39:dd:a1:69 REACHABLE
fe80::16de:39ff:fedd:a169 dev eno1 lladdr 14:de:39:dd:a1:69 router STALE

arp -a
homerouter.cpe (192.168.8.1) at 14:de:39:dd:a1:69 [ether] on eno1

nmcli dev show
GENERAL.DEVICE: eno1
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 88:05:69:24:35:F8
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Wired connection 1
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveC>
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.8.110/24
IP4.GATEWAY: 192.168.8.1
IP4.ROUTE[1]: dst = 192.168.8.0/24, nh = 0.0.0.0, mt >
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.8.1, mt =>
IP4.DNS[1]: 192.168.8.1
IP6.ADDRESS[1]: fd14:de39:dda1:6900:508a:2581:5bbe:454/>
IP6.ADDRESS[2]: fd14:de39:dda1:6900:d427:370b:22d8:ef80>
IP6.ADDRESS[3]: fe80::3824:f2d0:1746:2269/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024
IP6.ROUTE[2]: dst = fd14:de39:dda1:6900::/64, nh = ::>
IP6.DNS[1]: fe80::16de:39ff:fedd:a169
GENERAL.DEVICE: wlp1s0
GENERAL.TYPE: wifi
GENERAL.HWADDR: A0:A4:C5:B4:46:41
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.GATEWAY: --
IP6.GATEWAY: --
GENERAL.DEVICE: vboxnet0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 0A:00:27:00:00:00
GENERAL.MTU: 1500
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: off
IP4.ADDRESS[1]: 192.168.56.1/24
IP4.GATEWAY: --
IP4.ROUTE[1]: dst = 192.168.56.0/24, nh = 0.0.0.0, mt>
IP6.ADDRESS[1]: fe80::800:27ff:fe00:0/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: --
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ::1/128, nh = ::, mt = 256

resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign

Link 2 (eno1)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.8.1
DNS Servers: 192.168.8.1

Link 3 (wlp1s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 8 (vboxnet0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
simon  ~  resolvectl query bbc.co.uk
bbc.co.uk: 151.101.64.81 -- link: eno1
151.101.192.81 -- link: eno1
151.101.0.81 -- link: eno1
151.101.128.81 -- link: eno1
2a04:4e42::81 -- link: eno1
2a04:4e42:400::81 -- link: eno1
2a04:4e42:600::81 -- link: eno1
2a04:4e42:200::81 -- link: eno1

-- Information acquired via protocol DNS in 24.4ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: network

Navigation

[0] Message Index

[#] Next page

Go to full version