[Solved] Wireless connection no longer working in Mageia 5

[Solved] Wireless connection no longer working in Mageia 5

Postby eldiener » Aug 26th, '15, 14:22

After upgrading from Mageia 4 to Mageia 5 my wireless connection to the Internet is no longer working.

I have a USB device which is a Rosewill RNX-EasyN1 as the wireless device on my computer. It uses internally an Ralink connection. In network manager I can see that Mageia 5 recognizes it as "Ralink 802.11n WLAN" and when I try to connect to my router's wireless network via Network Manager it says that the connection is established and that there is no problem. But all attempts at accessing the Internet fail. The weather applet shows a big X-like image rather than a weather image; when I open web pages in Firefox all pages return that the server is not connectied etc. etc. through any Internet access.

Any help trying to figure out what is happening would be appreciated. I have a sneaking suspicion that the problem is that Network Manager and some sort of network applet are conflicting with each other, both trying to manage the wireless network connection. But while I can easily see the Network Manager I do not see a network applet anywhere if it exists. Of course I could easily be wrong and it is some other problem.
Last edited by eldiener on Sep 6th, '15, 12:33, edited 1 time in total.
eldiener
 
Posts: 57
Joined: Oct 22nd, '12, 01:44

Re: Wireless connection no longer working in Mageia 5

Postby doktor5000 » Aug 26th, '15, 22:49

Which desktop environment are you using? Please provide the output of the following commands:

Code: Select all
lspcidrake -v | grep -i -e net -e wireless -e wifi
ps -ef | grep -v grep | grep -ie net -e wpa


and, as root:
Code: Select all
ifconfig -a
rfkill list all
systemctl status network.service -a
journalctl -ab | grep -iE "fw|firmware|iwl|wifi|wire|80211"
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17659
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Wireless connection no longer working in Mageia 5

Postby eldiener » Aug 27th, '15, 07:02

The desktop environment is KDE.

Code: Select all
    lspcidrake -v | grep -i -e net -e wireless -e wifi

r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1462 subd:376c) (rev: 01)


Code: Select all
    ps -ef | grep -v grep | grep -ie net -e wpa

root        24     2  0 23:34 ?        00:00:00 [netns]
root      1603     1  0 23:35 ?        00:00:00 /usr/sbin/wpa_supplicant -B -i wlp0s19f5u8 -c /etc/wpa_supplicant.conf -D wext 


Code: Select all
    ifconfig -a

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:1d:92:b0:b8:d4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 819  bytes 89203 (87.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 819  bytes 89203 (87.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s19f5u8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.84  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2602:306:37b3:6140:202:6fff:fe5b:66f9  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::202:6fff:fe5b:66f9  prefixlen 64  scopeid 0x20<link>
        ether 00:02:6f:5b:66:f9  txqueuelen 1000  (Ethernet)
        RX packets 875  bytes 50798 (49.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 2024 (1.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Code: Select all
    rfkill list all

0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no


Code: Select all
    systemctl status network.service -a

network.service - LSB: Bring up/down networking                                                                                       
   Loaded: loaded (/etc/rc.d/init.d/network)                                                                                           
   Active: failed (Result: exit-code) since Wed 2015-08-26 23:35:36 EDT; 16min ago                                                     
  Process: 1142 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)                                               
   CGroup: /system.slice/network.service                                                                                               
           â”œâ”€1410 /sbin/ifplugd -I -b -i eth0                                                                                           
           â”œâ”€1603 /usr/sbin/wpa_supplicant -B -i wlp0s19f5u8 -c /etc/wpa_supplicant.conf -D wext                                       
           â”œâ”€1605 /sbin/ifplugd -I -b -i wlp0s19f5u8
           â””─1968 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlp0s19f5u8.lease -pf /var/run/dhclient-wlp0s19f5u8.pid wlp0s19f5u8

Aug 26 23:35:36 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Aug 26 23:35:36 localhost.localdomain systemd[1]: Unit network.service entered failed state.
Aug 26 23:35:36 localhost.localdomain systemd[1]: network.service failed.
Aug 26 23:35:43 localhost.localdomain ifplugd(wlp0s19f5u8)[1605]: Link beat detected.
Aug 26 23:35:44 localhost.localdomain ifplugd(wlp0s19f5u8)[1605]: Executing '/etc/ifplugd/ifplugd.action wlp0s19f5u8 up'.
Aug 26 23:35:45 localhost.localdomain dhclient[1866]: DHCPREQUEST on wlp0s19f5u8 to 255.255.255.255 port 67
Aug 26 23:35:45 localhost.localdomain dhclient[1866]: DHCPACK from 192.168.1.254
Aug 26 23:35:45 localhost.localdomain dhclient[1866]: bound to 192.168.1.84 -- renewal in 33081 seconds.
Aug 26 23:35:45 localhost.localdomain ifplugd(wlp0s19f5u8)[1605]: client: Determining IP information for wlp0s19f5u8... done.
Aug 26 23:35:45 localhost.localdomain ifplugd(wlp0s19f5u8)[1605]: Program executed successfully.


Code: Select all
  journalctl -ab | grep -iE "fw|firmware|iwl|wifi|wire|80211"

Aug 26 23:35:07 localhost.localdomain kernel: pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
Aug 26 23:35:07 localhost.localdomain kernel: firewire_ohci 0000:04:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
Aug 26 23:35:07 localhost.localdomain kernel: firewire_core 0000:04:00.0: created device fw0: GUID 00dc1000015522aa, S400
Aug 26 23:35:07 localhost.localdomain kernel: usb 1-10.1: Product: Back-UPS RS 1500 FW:8.g9 .D USB FW:g9
Aug 26 23:35:07 localhost.localdomain kernel: hid-generic 0003:051D:0002.0007: hiddev0,hidraw3: USB HID v1.10 Device [American Power Conversion Back-UPS RS 1500 FW:8.g9 .D USB FW:g9 ] on usb-0000:00:13.5-10.1/input0
Aug 26 23:35:13 localhost.localdomain kernel: cfg80211: Calling CRDA to update world regulatory domain
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211: World regulatory domain updated:
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:  DFS Master region: unset
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0200 detected
Aug 26 23:35:16 localhost.localdomain kernel: ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
Aug 26 23:35:16 localhost.localdomain kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211: Calling CRDA for country: US
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211: Regulatory domain changed to country: US
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:  DFS Master region: FCC
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Aug 26 23:35:16 localhost.localdomain kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Aug 26 23:35:30 localhost.localdomain network[1142]: Configuring wireless regulatory domain  [  OK  ]
Aug 26 23:35:32 localhost.localdomain kernel: ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
Aug 26 23:35:33 localhost.localdomain kernel: ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
Aug 26 23:35:34 localhost.localdomain network[1142]: Bringing up interface wlp0s19f5u8:  Error for wireless request "Set Encode" (8B2A) :
Aug 26 23:35:42 localhost.localdomain kernel: IFWLOG: register target
Last edited by doktor5000 on Aug 27th, '15, 19:51, edited 1 time in total.
Reason: removed fullquote
eldiener
 
Posts: 57
Joined: Oct 22nd, '12, 01:44

Re: Wireless connection no longer working in Mageia 5

Postby doktor5000 » Aug 27th, '15, 20:08

Hmm, seems OK so far, you are connected via wireless and have even obtained an IP adress via DHCP. Please show the output of the following commands as root

Code: Select all
iwconfig
netstat -rn
cat /etc/resolv.conf
ping -c5 8.8.8.8
ping -c5 google.com
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17659
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Wireless connection no longer working in Mageia 5

Postby eldiener » Aug 28th, '15, 07:40

doktor5000 wrote:Hmm, seems OK so far, you are connected via wireless and have even obtained an IP adress via DHCP. Please show the output of the following commands as root

Code: Select all
iwconfig
netstat -rn
cat /etc/resolv.conf
ping -c5 8.8.8.8
ping -c5 google.com


Code: Select all
iwconfig

eth0      no wireless extensions.

wlp0s19f5u8  IEEE 802.11bgn  ESSID:"EdDienerNet" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: D0:39:B3:2B:7E:D0   
          Bit Rate=1 Mb/s   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=53/70  Signal level=-57 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:6   Missed beacon:0

lo        no wireless extensions.


Code: Select all
    netstat -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0 wlp0s19f5u8
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 wlp0s19f5u8
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 wlp0s19f5u8


Code: Select all
cat /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.254
search att.net


Code: Select all
ping -c5 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable

--- 8.8.8.8 ping statistics ---
0 packets transmitted, 0 received, +5 errors


Code: Select all
  ping -c5 google.com

ping: unknown host google.com
eldiener
 
Posts: 57
Joined: Oct 22nd, '12, 01:44

Re: Wireless connection no longer working in Mageia 5

Postby doktor5000 » Aug 29th, '15, 19:52

Hmmm, looks like a problem with your router. routing table and default route looks OK, you obtained DNS server and search suffix (are you with AT&T ?) from your router.
Maybe the router simply needs a reboot?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17659
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Wireless connection no longer working in Mageia 5

Postby wintpe » Sep 1st, '15, 11:09

Ive seen this symptom as well where the only thing thats not passed in the DHCP packet is a good dns resolver.

in that case I had to set the dns manually to 8.8.8.8 on there persons desktop.

that will work as a workaround, but ultimately, the router needs either a hard coded dns server set in its config, to pass in the dhcp part
or find out why the dns proxy is not working in the router.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: Wireless connection no longer working in Mageia 5

Postby doktor5000 » Sep 1st, '15, 20:36

Well, it should be easy to find out. If the name server is in the lease obtained from the router, then it's an issue on your box.
If it's not in the lease, then that's a broken router.

The .lease files should be located in either
/var/lib/dhclient or for networkmanager in /var/lib/NetworkManager/
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17659
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Wireless connection no longer working in Mageia 5

Postby jiml8 » Sep 1st, '15, 23:06

It all looks OK. Might try pinging the router directly. Problem pretty much has to be there.
jiml8
 
Posts: 1253
Joined: Jul 7th, '13, 18:09

Re: Wireless connection no longer working in Mageia 5

Postby eldiener » Sep 6th, '15, 12:32

doktor5000 wrote:Well, it should be easy to find out. If the name server is in the lease obtained from the router, then it's an issue on your box.
If it's not in the lease, then that's a broken router.

The .lease files should be located in either
/var/lib/dhclient or for networkmanager in /var/lib/NetworkManager/


I moved and in the process changed Internet providers. With my new Internet provider I have had no problems connecting to their wireless network via their router/modem setup using Mageia 5. Everything else, including my own computer and hardware, remained the same. Perhaps Mageia was able to figure something out internally which it could not with the old Internet provider's router/modem.

So the issue is resolved for me.

Thanks for your help !
eldiener
 
Posts: 57
Joined: Oct 22nd, '12, 01:44


Return to Networking

Who is online

Users browsing this forum: No registered users and 1 guest