Network speeds differ according to boot source

Hardware - Support > Network

<< < (2/3) > >>

stevef:
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 ?

Earthenware:
I'll work my way through that stuff, but it will take a while.

Regarding VMs, I'm running the exact same VirtualBox setup that I have on all my previous Linux Lite computers, including the exact same VMs and the exact same VirtualBox internal network configuration.

I very much hope that LL hasn't developed an allergy to VMs, as they are essential to my business.

stevef:

--- Quote from: Earthenware on November 20, 2023, 08:25:29 AM ---Booting from PC:
Network:
Device-1: Intel Ethernet I219-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 88:05:69:24:35:f8
IP v4: 192.168.8.110/24 type: dynamic noprefixroute scope: global
IP v6: fd14:de39:dda1:6900:7013:abfe:de3a:692/64 type: temporary dynamic
scope: global
IP v6: fd14:de39:dda1:6900:d427:370b:22d8:ef80/64
type: dynamic mngtmpaddr noprefixroute scope: global
IP v6: fe80::3824:f2d0:1746:2269/64 type: noprefixroute scope: link
Device-2: Intel Wireless 7265 driver: iwlwifi
IF: wlp1s0 state: down mac: a0:a4:c5:b4:46:41
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
IP v4: 10.10.0.8/16 scope: global
IP v6: fe80::b291:da71:92ad:22b2/64 virtual: stable-privacy scope: link
IF-ID-2: vboxnet0 state: up speed: 10 Mbps duplex: full
mac: 0a:00:27:00:00:00
IP v4: 192.168.56.1/24 scope: global
IP v6: fe80::800:27ff:fe00:0/64 scope: link
WAN IP: ;; communications error to 208.67.222.222#53: connection refused

--- End quote ---

Ethernet driver is clearly the same in both case, but there are some 'extras' in your installed version.
It appears to have a tunnel network and a virtual machine.
I don't use virtual machines and don't know yet if it is significant to your problem.

Secondly, the WAN address reporting is showing an odd situation, possibly related to DNS. This may be significant.

Have you set up a virtual machine in the installed version or done anything at all related to networking - maybe a VPN?

If possible can you run these commands in both scenarios. Apologies for the scattergun approach, but something in one or more of these outputs might show why the network is performing differently in the installed version.

--- Code: ---ifconfig -a
--- End code ---

--- Code: ---ip r
--- End code ---

--- Code: ---route
--- End code ---

--- Code: ---ip n
--- End code ---

--- Code: ---arp -a
--- End code ---

--- Code: ---ping _gateway
--- End code ---
Allow to run for 5 seconds, then terminate command with 'ctrl c'

--- Code: ---ping 8.8.8.8
--- End code ---
Allow to run for 5 seconds, then terminate command with 'ctrl c'

--- Code: ---ping google.com
--- End code ---
Allow to run for 5 seconds, then terminate command with 'ctrl c'

--- Code: ---nmcli dev show
--- End code ---
If the screen pause showing 'lines x-y' press space until you see (END), then press 'Q'

--- Code: ---resolvectl status
--- End code ---
If the screen pause showing 'lines x-y' press space until you see (END), then press 'Q'

--- Code: ---resolvectl query bbc.co.uk
--- End code ---

--- Code: ---tracepath -l 500 -n -b 184.95.56.34
--- End code ---

Earthenware:

--- Quote from: stevef on November 20, 2023, 08:03:31 AM ---To check your driver theory post back with the outputs of this command run in both boot scenarios.

--- Code: ---inxi -ni
--- End code ---
You may want to mask the WAN IP address.

--- End quote ---

Running that command gives the following:

Booting from USB
Network:
Device-1: Intel Ethernet I219-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 88:05:69:24:35:f8
IP v4: 192.168.8.110/24 type: dynamic noprefixroute scope: global
IP v6: fd14:de39:dda1:6900:f99f:e573:8a89:1638/64 type: temporary dynamic
scope: global
IP v6: fd14:de39:dda1:6900:d427:370b:22d8:ef80/64
type: dynamic mngtmpaddr noprefixroute scope: global
IP v6: fe80::3824:f2d0:1746:2269/64 type: noprefixroute scope: link
Device-2: Intel Wireless 7265 driver: iwlwifi
IF: wlp1s0 state: down mac: a0:a4:c5:b4:46:41
WAN IP: 31.94.71.180

Booting from PC:
Network:
Device-1: Intel Ethernet I219-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 88:05:69:24:35:f8
IP v4: 192.168.8.110/24 type: dynamic noprefixroute scope: global
IP v6: fd14:de39:dda1:6900:7013:abfe:de3a:692/64 type: temporary dynamic
scope: global
IP v6: fd14:de39:dda1:6900:d427:370b:22d8:ef80/64
type: dynamic mngtmpaddr noprefixroute scope: global
IP v6: fe80::3824:f2d0:1746:2269/64 type: noprefixroute scope: link
Device-2: Intel Wireless 7265 driver: iwlwifi
IF: wlp1s0 state: down mac: a0:a4:c5:b4:46:41
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
IP v4: 10.10.0.8/16 scope: global
IP v6: fe80::b291:da71:92ad:22b2/64 virtual: stable-privacy scope: link
IF-ID-2: vboxnet0 state: up speed: 10 Mbps duplex: full
mac: 0a:00:27:00:00:00
IP v4: 192.168.56.1/24 scope: global
IP v6: fe80::800:27ff:fe00:0/64 scope: link
WAN IP: ;; communications error to 208.67.222.222#53: connection refused

stevef:
To check your driver theory post back with the outputs of this command run in both boot scenarios.

--- Code: ---inxi -ni
--- End code ---

You may want to mask the WAN IP address.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version