I have an issue with my wireless connection failing after a random amount of time.
It connects to the router fine without problems but after a few minutes - 20 minutes, everything network related stops working (ping, name resolution).
I've trawled through lots of searches and forums but found no solution.
I've tried 2 different wireless cards:
- Asus PCE-N53 PCI-E card (https://wikidevi.com/wiki/ASUS_PCE-N53) which has the RT5592 chipset.
- Edimax EW-7811UN USB adapter (https://wikidevi.com/wiki/Edimax_EW-7811Un) which has the RTL8188CUS chipset.
I found out that the chipset in the asus card was not very good on linux so I bought the usb one thinking that was the problem, but it's still the same.
Here is the output from mintwifi:
Code: Select all
mintwifi
-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"SKY73794"
Mode:Managed Frequency:2.412 GHz Access Point: 7C:4C:A5:01:78:25
Bit Rate=7.2 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
Link Quality=46/70 Signal level=-64 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:151 Missed beacon:0
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr d8:50:e6:bd:9b:60
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:226 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20278 (20.2 KB) TX bytes:20278 (20.2 KB)
wlan0 Link encap:Ethernet HWaddr 80:1f:02:fd:8a:c5
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7715 errors:0 dropped:0 overruns:0 frame:0
TX packets:7985 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6845993 (6.8 MB) TX bytes:1604919 (1.6 MB)
-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: google.com
Address: 74.125.230.105
Name: google.com
Address: 74.125.230.103
Name: google.com
Address: 74.125.230.100
Name: google.com
Address: 74.125.230.99
Name: google.com
Address: 74.125.230.101
Name: google.com
Address: 74.125.230.98
Name: google.com
Address: 74.125.230.97
Name: google.com
Address: 74.125.230.104
Name: google.com
Address: 74.125.230.96
Name: google.com
Address: 74.125.230.110
Name: google.com
Address: 74.125.230.102
Code: Select all
inxi -N
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] driver: rtl8192cu
Normally it's like this:
Code: Select all
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default SkyRouter.Home 0.0.0.0 UG 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 9 0 0 wlan0
ip route
default via 192.168.0.1 dev wlan0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3 metric 9
Code: Select all
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 9 0 0 wlan0
ip route
default via 192.168.0.1 dev wlan0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.3 metric 9
ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13104ms
Occasionally ping shows 192.168.0.3 (my computer) as host unreachable (???)
Turning wifi off then back on again in network manager temporarily fixes it.
Many thanks for any help!
Michael