Skip to main content
Vraag

Ubuntu will not connect to Internet

  • 30 november 2023
  • 11 reacties
  • 311 keer bekeken

Hi 

I have just switched today from Ziggo to KPN, all my devices are connecting to the internet including my windows PC, but my Linux Ubuntu will not connect. Works perfectly on my old Ziggo connection, and the network cable is lighting up, but no internet.

 

Can some please help advise?

 

Many thanks

Dit topic is gesloten. Staat je antwoord hier niet bij, gebruik dan de zoekfunctie van de Community of stel je vraag in een nieuw topic.

11 reacties

GeSp
Slimmerik
Forum|alt.badge.img+19
  • 6651 reacties
  • 30 november 2023

Hello @Stabi 

 

Does the Ubuntu PC get an IP address through DHCP or is it static and set to an IP address in the Ziggo local IP range (192.168.178.x) which differs from the KPN local IP range (192.168.2.x)?

It's best to set it to DHCP and use a DHCP Binding in the modem if it needs to stay the same.


  • Auteur
  • Nieuwkomer
  • 1 reactie
  • 30 november 2023

Hi @GeSp it is DHCP, i have all the cables in but will not connect to the internet. 

 


  • 5928 reacties
  • 30 november 2023

What if you ping anything ?
Or traceroute

( send from ubuntu )


  • Deelnemer
  • 5 reacties
  • 2 december 2023

Experiencing a similar issue. Moved houses/provider but kept same wifi ssid/pass. Everything connects fine except for my ThinkPad running Opensuse Tumbleweed. It seems to authenticate fine, but then doesn't get an ip. I removed the connection completely and nothing seems to work/help. 


GeSp
Slimmerik
Forum|alt.badge.img+19
  • 6651 reacties
  • 2 december 2023

@Stabi Have you got it working in the meantime?

 

@tbrasser

Did you configure the network connection to get an IP address via DHCP?

Does the ThinkPad get an IP address when you connect it with a network cable to the modem?
What KPN modem do you have?


  • Deelnemer
  • 5 reacties
  • 2 december 2023

Yes, dhcp, will check with ethernet, It's the box 14. 


  • Deelnemer
  • 5 reacties
  • 2 december 2023

Also tested on ethernet, same behavior unfortunately. I already turned off wifi and tried my own AP's so it's looking like something incompatible in the dhcp server? 


  • Deelnemer
  • 5 reacties
  • 2 december 2023

Captured some log output, seems indeed dhcp issues. I suspected ipv6 may be causing this, so I disabled that (both in box 14 and on laptop) but that didn´t improve things.

 

Dec 02 23:59:02 spacebar NetworkManager[1300]: <info>  [1701557942.5052] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
Dec 02 23:59:02 spacebar NetworkManager[1300]: <info>  [1701557942.5052] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "fiwi"
Dec 02 23:59:02 spacebar NetworkManager[1300]: <info>  [1701557942.5052] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
Dec 02 23:59:02 spacebar NetworkManager[1300]: <info>  [1701557942.5245] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 02 23:59:02 spacebar NetworkManager[1300]: <info>  [1701557942.5250] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Dec 02 23:59:14 spacebar systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.8178] device (wlp0s20f3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.8180] manager: NetworkManager state is now DISCONNECTED
Dec 02 23:59:47 spacebar kernel: wlp0s20f3: deauthenticating from f6:92:bf:98:b0:0a by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.8701] device (wlp0s20f3): set-hw-addr: set MAC address to DE:E6:91:6B:20:04 (scanning)
Dec 02 23:59:47 spacebar NetworkManager[1300]: <warn>  [1701557987.8734] device (wlp0s20f3): Activation: failed for connection 'fiwi'
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.8739] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.9044] dhcp4 (wlp0s20f3): canceled DHCP transaction
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.9045] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.9045] dhcp4 (wlp0s20f3): state changed no lease
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.9055] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Dec 02 23:59:47 spacebar NetworkManager[1300]: <info>  [1701557987.9056] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected

 


  • Deelnemer
  • 5 reacties
  • 3 december 2023

Try to give your ubuntu a fixed ip and then retry


  • Deelnemer
  • 5 reacties
  • 3 december 2023

Disabled DHCP, running my own now and also passing around a public dns server now, finally that got my laptop online (and every other device) without issues. 

Time to get a R86s Mini PC instead of the box 14 that now only acts as a gateway.

 

 


  • Deelnemer
  • 5 reacties
  • 3 december 2023

Good that it’s working now.

Still very strange.

I’ve got several Lxc cointainer runnning with ubuntu 22.04.3 and dhcp is working there.

also a thin client with ubuntu 22.04.3 using wlan and dhcp no problem.