Ask Your Question
0

Fedora 26 lost wifi connection to *only one* network

asked 2017-10-27 18:34:29 -0500

technog1 gravatar image

OS: Fedora 26

03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

Very odd behavior. ISP had an issue and lost full access to the internet.

Once ISP connection was restored, my fedora 26 laptop still cannot connect to the wireless network it could connect to prior to the isp outage.

Note that other clients have been able to re-connect to the wifi without any problems. However, none of these connected clients are linux. They are windows, android and ios clients. So i know my router is working fine.

I tried to renew my lease via dhclient -r virbir0. Still does not connect.

If I take my laptop to a different wifi network it had connected to prior, it automatically reconnects just fine. So i know my wifi on the laptop is working.

I checked the passwd on the wifi and its good.

Its just my home network!!! Cannot connect to wifi anymore!!! Not sure what to do

Not sure if I should do anything with modprobe ?

tia,

Sunil

edit retag flag offensive close merge delete

Comments

Without knowing your network settings in more detail we can hardly assist you further. But from the provided info it would seems like you have some network configuration issue on that laptop. Where does this virbr0 interface comes from? Do you have some virtual machine bridge configured on the laptop?

I would recommend going into network settings for this machine and undo any custom things you might have configured on it in order to bring back the defaults.

To help us understand this further you can provide ip addr show output as well or screenshot of your network settings.

masteroman gravatar imagemasteroman ( 2017-10-28 07:53:42 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2017-10-29 13:47:30 -0500

technog1 gravatar image

Sure. Will provide what ever info is needed. I was surprised to see "virbr0" ifce as well. But dont remember what the wireless ifce was named before this. I have not installed any os virtualization. PS. syslog below shows trying to authenticate. I havent changed my ssid passwd. My other non linux devices re- connected just fine.

If i missed any settings info, pls let me know and I will provide.

This is the output from ifconfig: I am currently connected via a ethernet cable.

enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.124  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::5604:a6ff:fe44:a479  prefixlen 64  scopeid 0x20<link>
        ether 54:04:a6:44:a4:79  txqueuelen 1000  (Ethernet)
        RX packets 587547  bytes 516022358 (492.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 490834  bytes 126045126 (120.2 MiB)
        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 1000  (Local Loopback)
        RX packets 24  bytes 1816 (1.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 1816 (1.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.124.1  netmask 255.255.255.0  broadcast 192.168.124.255
        ether 52:54:00:ff:2d:c2  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

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:ff:2d:c2  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

wlp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether a6:a7:e7:fd:af:f4  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

ip addr output:

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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 54:04:a6:44:a4:79 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.124/24 ...
(more)
edit flag offensive delete link more

Comments

masteroman: Sorry, i had installed vpn software a long time ago. Not sure if that was what you were alluding to? It had been working fine all this time. I will have to figure out how to un-install that software and check if its any better afterwards.

technog1 gravatar imagetechnog1 ( 2017-10-29 14:06:38 -0500 )edit

I were alluding to the virbr itnerface being created by the some virtualization software. virbr is usually created by virt-manager, virtualbox and similar programs. Your wireless interface is still wlp3s0 , but seems like it could be a part of virbr interface when you connect to the wifi.

You're currently connected to the network via cable, right? Because I can see enp5s0 is active and has IP assigned to it.

Can you re-create issue and while the issue is active provide that output since that may give better info..

masteroman gravatar imagemasteroman ( 2017-11-02 07:18:50 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2017-10-27 18:34:29 -0500

Seen: 389 times

Last updated: Oct 29 '17