XUbuntu 20.04 won't connect to wired router/internet using my computer, the live CD, or live CD for 18.x or 16.x. These had worked before without problem. Other computers running 18.x still work and my desktop still connects using Windows 10 but not when I boot into XUbuntu. I've tried a couple of solutions posted and one worked temporarily but failed to connect on next boot up. Please let me know what you need from me to trouble shoot this problem. Thanks.
@heynnema Thanks for you help.
Wired network is mix of purchased and home-made cables down to Cat-5 but properly assembled. DSL modem-router (with WiFi) with switch between. All 10/100. Router may go up to 1000. Network wrks fine with other XUbuntu 18.04 (32 bit) computers and the HP-elite 800 64 bit desktop under Windows 10. Used to work with all versions of XUbuntu until a month or two ago (including the live cds).
01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
ethernets:
eno1:
dhcp4: yes
dhcp6: no
I edited that file according to other solutions I had found and it worked briefly.
sudo lshw -C network
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eno1
version: 04
serial: 8c:dc:d4:25:f2:71
size: 100Mbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
resources: irq:27 memory:f7c00000-f7c1ffff memory:f7c3d000-f7c3dfff ioport:f080(size=32)
I'm really curious why the live cds would stop connecting to the network/internet when they worked on the same set-up not long ago.
@heynnema
I edited the netplan *.yaml file back to it's original state and rebooted. That plus "setting" the cable connectors yet again seems to work and explains the problem. Also:
$ tracepath www.google.com
tracepath: www.google.com: No address associated with hostname
$ tracepath 8.8.8.8
1?: [LOCALHOST] pmtu 1500
1: Broadcom.Home 1.406ms
1: Broadcom.Home 1.224ms
2: Broadcom.Home 1.170ms pmtu 1492
2: 172.16.2.1 26.823ms
3: vl-3611.tor01ad-aro22.ne.fibernetics.ca 43.601ms
4: no reply
5: ip-49.50.99.216.dsl-cust.ca.inter.net 26.673ms
6: google-b.ip4.torontointernetxchange.net 26.514ms asymm 9
7: no reply
I suppose that the mtu you asked for is in there.