0

After my previous networking woes got fixed (No (easy) networking after upgrade to Xubuntu 20.04.1 LTS) I have swapped over to Ubuntu Studio. The 22.04.01 LTS release recommends a clean install, which I have done, and... you guessed it I now need to do sudo ip link set dev wlp7s0 down && dhclient wlp7s0 after every boot to get a fully working connection (without doing this some sites such as Google, are accessible, others, such as AskUbuntu(!) are not).

Results of wireless info script are linked below (split into two parts).

Part 1: https://paste.ubuntu.com/p/Ks7wdfjwbF/

Part 2: https://paste.ubuntu.com/p/TtvJ8q56wZ/

I've spotted that lsmod output points out that the driver that's been installed for me is related to the rtl8192ce, so I don't know if that is my issue, and I'm not sure how to 'force' the correct driver to be used. [In the past I've used the RTL8188CE drivers published by FreedomBen on GitHub but they are presently not compiling: https://github.com/FreedomBen/rtl8188ce-linux-driver/issues/157 ]

Edit: Additional Info results: https://paste.ubuntu.com/p/DjmnRDfjvN/

Edit 2:

$ sudo cat /var/lib/NetworkManager/NetworkManager.state
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
IainCunningham
  • 132
  • 1
  • 10
  • 2
    "so let me know how to share the rest and I will" Please give us the link to a second, and, if needed, third paste. Thanks. – chili555 Aug 24 '22 at 21:14
  • @Chili555 Done! – IainCunningham Aug 24 '22 at 21:33
  • [Seems as though it's actually a clipboard problem, and the string '' breaks the copy/paste somehow] – IainCunningham Aug 24 '22 at 21:34
  • 2
    that is the correct driver, so not the issue. – Esther Aug 24 '22 at 21:49
  • 1
    "without doing this some sites such as Google, are accessible, others, such as AskUbuntu(!) are not" This makes me wonder if you are not getting a proper (or any) DNS nameservers from the access point/router. Please set fixed DNS in Network Manager: https://www.ricmedia.com/images/117.webp and reboot. Any improvement? – chili555 Aug 24 '22 at 22:02
  • Fixed DNS gives no improvement, I still need to sudo ip link set dev wlp7s0 down && dhclient wlp7s0. I've run the script before doing this, and have linked the result from my post above. (I don't seem to have an IPv4 address allocated?) – IainCunningham Aug 25 '22 at 22:05
  • Indeed. No IPv4 address. May we see: sudo cat /var/lib/NetworkManager/NetworkManager.state Do all other devices; i.e. phones, tablets, etc. work properly on this network? – chili555 Aug 25 '22 at 23:08
  • @chili555 I've added the result to my OP. Everything else on the network seems to be fine (this PC was too, until I ran the clean install!) – IainCunningham Aug 29 '22 at 14:46
  • [In case it's relevant, the results are the same before and after sudo ip link...] – IainCunningham Aug 29 '22 at 14:53
  • While there quite obviously is something wrong, I regret that after studying your readings carefully, I see nothing fixable. Sorry. Perhaps another wireless specialist will come by and correct me. – chili555 Sep 02 '22 at 13:10
  • I've had a search around for Ubuntu IPv4 issues (for clues) and it seems I'm not alone. Unfortunately most of the threads end with someone saying, "well, if it was a real problem there would be hundreds of people complaining". :-( – IainCunningham Sep 02 '22 at 22:00
  • @chili555 it seems there may be some weirdness inside NetworkManager's DHCP client, after forcing it to use dhclient instead I have IPv4 on every boot. – IainCunningham Sep 05 '22 at 20:33

1 Answers1

1

After a lot of digging around, I noticed that there were some people questioning the built-in DHCP client of NetworkManager, and after reading the docs, I have added:

dhcp=dhclient

To the [main] section of /etc/NetworkManager/NetworkManager.conf.

Since doing this everything has been working just fine.

IainCunningham
  • 132
  • 1
  • 10