So my father and i were just trying out Tumbleweed openSUSE 42.3, which to our surprise was very pleasant to use, as casual multimedia users.
We try different kinds of OS as a hobbie of ours. The fascinating world of the free software is astonishing to us and we are very grateful.
Now on more technical issues, when we first installed Tumbleweed, we could not set the right network configuration, thus having no internet connection.
I tried different solutions by different users and helpers and somehow by setting, global options by wicked and DHCP option, it worked. Then when upgrading Kernel Vanilla we lost connection to internet.
We tried reinstalling several times but we just don’t know how to properly set the network configuration.
We don’t have any real technical knowledge, just by trial and error.
Tell us how to give you more information and i will do as requested.
Thanks in advance and pardon my english if mistaken.
This is one of the problems that show up now;
More than one interface asks to control the hostname via DHCP. If you keep the current settings, the behavior is non deterministic.
By the reason that we are trying to find out, the wireless connection failed. However, we moved the desktop pc from one room to another, so we could try via ethernet cable and Internet connection was succesful.
I’m guessing the problem is unsuccesful wireless connection configuration, we are still trying to figure this out because the PC does not belong in the other room and wireless is needed.
Being connected via ethernet may help the wireless situation i suppose, so i’ll keep tuned in.
In YaST - System - Networksettings - Overview, you should see 2 items. One if the wirde network card, that you succesfully configured. The other one is the wireless card. Click it, click Edit to configure it, with ( easiest ) DHCP, search you wireless router, select the proper protocol ( most likely WPA2/PSK, and enter the key/passphrase. Finish everything and check the connection.
The Wireless Network Adpater seems to be configured as suggested (DHCP,WPA2/PSK and key) it recognises my wifi connection but it doesn’t connect to internet.
How else can i show you more information, it seems to be working fine but it is indeed not working.
-- Logs begin at Sun 2018-04-01 00:39:39 -03, end at Sun 2018-04-01 00:46:27 -03
abr 01 00:40:09 linux-viy6 systemd[1]: Starting wicked managed network interface
abr 01 00:40:16 linux-viy6 wicked[1135]: lo up
abr 01 00:40:16 linux-viy6 wicked[1135]: wlp2s0 device-not-running
abr 01 00:40:16 linux-viy6 systemd[1]: Started wicked managed network interfaces
abr 01 00:43:54 linux-viy6 systemd[1]: Reloading wicked managed network interfac
abr 01 00:43:54 linux-viy6 wicked[3430]: wlp2s0 device-ready
abr 01 00:43:54 linux-viy6 wicked[3430]: wlp2s0 device-not-running
abr 01 00:43:54 linux-viy6 systemd[1]: Reloaded wicked managed network interface
lines 1-9/9 (END)
You can use copy/paste and Code-Tags, only if the result is to long use the susepaste.
And please show also the complete line with the command, it helps if there are some mistakes inside.
I would suggest you try switching to Network Manager instead of Wicked.
I would also like to know the brand and model of the router you are trying to connect to.
… and a suggestion: Are the wireless settings in the router set properly? For example, do you have anything like MAC address filtering enabled? If so, do you have your wireless MAC entered in there and allowed?
In addition, you might temporarily give the wireless a simple encryption password to see if the problem is there.
And, I have found on some routers that having them set to Automatic instead of WPA or WPA2 exclusively can cause authorization failures on some devices, so try changing that setting.
And, check the IP ranges set in your router for the Wireless connections, make sure they are in the range accepted by the main IP settings you have in the router.
Also, make certain that you do not have that range already filled by other devices around the home.
If you have set Static Assignments for your devices in the router, make certain that this PC is not connecting on an address that is in use by another machine. I have also seen that happen with the same results you are experiencing, scratching your head.
Best we try to get this fixed while you still have some hair left.
Ok, so no MAC filters enabled, wifi ranges are ok , i reseted the router settings and changed the password to a simpler one, tried no password at all. No Static Assignments set for devices in router aswell. Further help is very well aprecciated.
Command requested:
abr 01 09:09:26 linux-5o3e kernel: ath9k 0000:02:00.0 wlp2s0: renamed from wlan0abr 01 09:09:44 linux-5o3e kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: authenticate with 98:97:d1:cc:af:38
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: send auth to 98:97:d1:cc:af:38 (try 1/3)
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: authenticated
abr 01 09:09:45 linux-5o3e kernel: ath9k 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: associate with 98:97:d1:cc:af:38 (try 1/3)
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: RX AssocResp from 98:97:d1:cc:af:38 (capab=0x431 status=0 aid=2)
abr 01 09:09:45 linux-5o3e kernel: wlp2s0: associated
abr 01 09:09:45 linux-5o3e kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
abr 01 09:12:26 linux-5o3e kernel: wlp2s0: deauthenticating from 98:97:d1:cc:af:38 by local choice (Reason: 3=DEAUTH_LEAVING)
abr 01 09:12:27 linux-5o3e kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: authenticate with 98:97:d1:cc:af:38
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: send auth to 98:97:d1:cc:af:38 (try 1/3)
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: authenticated
abr 01 09:12:28 linux-5o3e kernel: ath9k 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: associate with 98:97:d1:cc:af:38 (try 1/3)
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: RX AssocResp from 98:97:d1:cc:af:38 (capab=0x431 status=0 aid=2)
abr 01 09:12:28 linux-5o3e kernel: wlp2s0: associated
abr 01 09:12:29 linux-5o3e kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
So ip a, was the only command showing information, the others didn’t throw anything at all.
ip a;
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether f0:bf:97:e8:dd:e1 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 32:7a:68:ea:13:d1 brd ff:ff:ff:ff:ff:ff
linux-5o3e:/home/german # ip route
linux-5o3e:/home/german # grep name /etc/resolv.conf
linux-5o3e:/home/german #
Also trying NetworkManager it shows that 2 miniapplications are required to be running(KDE plasma and nm-applet for GNOME), ‘‘make sure they are running otherwise execute manually’’.
I’ve read accounts of others with wifi hardware supported by the ath9k driver where frequent disconnections are reported, as appears to be the case from the journal logging snippet you posted. Some users report disabling hardware encryption helps. For example…
Good to read of your progress with this. Not sure why configuring with static IP then dynamically DHCP should help here. It’s probably a good idea to monitor the connection via the following in a terminal window…
sudo journalctl -fu wicked
*Assuming wicked is in use.
For NetworkManager, use
sudo journalctl -fu NetworkManager
When you next believe that the connection has dropped for some reason, check the log output. That might help determine if there are further issues to be sorted.
I’ve seen this before, an empty resolv.conf after multiple tries to get networking working. Of course a static IP + DNS’s will overwrite resolv.conf. The first was mostly recovered by a reboot of the machine.
