Intermittent Wifi

oktorok · 2014-08-21 02:03:09

[edit] using BCM4331 and b43-firmware from the AUR

Hi,

My wireless connection is timing out after anywhere from a few seconds to a few minutes. It started happening about 2 weeks ago, seemingly out of nowhere, as everything was fine up until some random moment in time, but I'm assuming there was an update involved. On a wired connection the problem does not exist. I don't believe it is a problem with my router, as I'm able to maintain stable connections to it on all my other devices (Android, MacOS, Arch).

My system is currently up to date. I've seen problems similar to this here on the forums but haven't been able to resolve it based on them.

With Netctl, I would start my profile, everything would run smoothly, then all of a sudden I'd lose data transfer, while the output of iwconfig said I was still connected to my router, no errors logged in journalctl, no errors in netctl status.

I tried using dhclient with netctl, thinking the timeouts were related to my DHCP lease, but that didn't help.

Today I switched over to connman to see if that might work as a workaround, but to no avail.

Here is output from journalctl from the moment I switched my wireless device UP to when the stoppage of data transfer occured:

% journalctl | grep -A 200 'Aug 20 18:31:20' | grep connman                                                                                                  ~
Aug 20 18:31:20 arch connman-vpnd[294]: wlp3s0 {update} flags 4099 <UP>
Aug 20 18:31:20 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:20 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 2 <DOWN>
Aug 20 18:31:20 arch connmand[276]: wlp3s0 {RX} 2949 packets 3086916 bytes
Aug 20 18:31:20 arch connmand[276]: wlp3s0 {TX} 2303 packets 408710 bytes
Aug 20 18:31:20 arch connmand[276]: wlp3s0 {update} flags 4099 <UP>
Aug 20 18:31:20 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:20 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 2 <DOWN>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 69635 <UP,LOWER_UP>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 6 <UP>
Aug 20 18:31:21 arch connmand[276]: Skipping disconnect of 4c43415253_managed_psk, network is connecting.
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {RX} 2949 packets 3086916 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {TX} 2303 packets 408710 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {update} flags 69635 <UP,LOWER_UP>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {RX} 2951 packets 3087244 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {TX} 2305 packets 408998 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 6 <UP>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 4163 <UP,RUNNING>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 4099 <UP>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {RX} 2951 packets 3087244 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {TX} 2307 packets 409738 bytes
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {update} flags 4099 <UP>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 69635 <UP,LOWER_UP>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Aug 20 18:31:21 arch connman-vpnd[294]: wlp3s0 {update} flags 4099 <UP>
Aug 20 18:31:21 arch connmand[276]: wlp3s0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Aug 20 18:31:22 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:22 arch connmand[276]: wlp3s0 {RX} 2951 packets 3087244 bytes
Aug 20 18:31:22 arch connmand[276]: wlp3s0 {TX} 2307 packets 409738 bytes
Aug 20 18:31:22 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 2 <DOWN>
Aug 20 18:31:22 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:31:22 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 2 <DOWN>
Aug 20 18:32:24 arch connmand[276]: Skipping disconnect of 4c43415253_managed_psk, network is connecting.
Aug 20 18:32:24 arch connmand[276]: wlp3s0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {update} flags 69635 <UP,LOWER_UP>
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {RX} 2951 packets 3087244 bytes
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {TX} 2307 packets 409738 bytes
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {update} flags 69635 <UP,LOWER_UP>
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 5 <DORMANT>
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {RX} 2953 packets 3087572 bytes
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {TX} 2309 packets 410026 bytes
Aug 20 18:32:25 arch connman-vpnd[294]: wlp3s0 {newlink} index 3 operstate 6 <UP>
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {newlink} index 3 address 28:CF:DA:D5:6A:A6 mtu 1500
Aug 20 18:32:25 arch connmand[276]: wlp3s0 {newlink} index 3 operstate 6 <UP>
Aug 20 18:32:30 arch connmand[276]: Setting domainname to home.network
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} address 10.0.0.3/24 label wlp3s0 family 2
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} route 10.0.0.0 gw 0.0.0.0 scope 253 <LINK>
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} route 10.0.0.1 gw 0.0.0.0 scope 253 <LINK>
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} route 75.75.75.75 gw 10.0.0.1 scope 0 <UNIVERSE>
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} route 75.75.76.76 gw 10.0.0.1 scope 0 <UNIVERSE>
Aug 20 18:32:30 arch connmand[276]: wlp3s0 {add} route 0.0.0.0 gw 10.0.0.1 scope 0 <UNIVERSE>
Aug 20 18:32:31 arch connmand[276]: wlp3s0 {add} route 87.106.208.187 gw 10.0.0.1 scope 0 <UNIVERSE>
Aug 20 18:32:31 arch connmand[276]: wlp3s0 {del} route 87.106.208.187 gw 10.0.0.1 scope 0 <UNIVERSE>

Any help, time, or effort is appreciated.

Last edited by oktorok (2014-08-21 23:58:34)

dice · 2014-08-21 08:27:05

Did you try switching power save off for your wifi?

iw wlp3s0 set power_save off

This quite often solves a lot of wifi problems.

Also did you try these tips?

oktorok · 2014-08-21 20:58:32

I've set power_save off, giving that a shot, it didn't work on first attempt, but I ran it while the interface was UP and active, so I disabled wifi, set the interface DOWN and set power_save off, running off that now. I also set the channel selection to auto, but it just jumped on the same channel. I'm unable to change the channel manually with iw, when I try I get "device or resource busy" even while the interface is down. I've also noticed that now my Wireless LAN is getting soft-blocked, I'm assuming this is related to my problems, but there doesn't seem to be a connection yet. If I set the interface DOWN, when I want to bring it up, I have to do an rfkill unblock.

[edit 1] power_save off didn't fix it, just lost and regained connectivity after about 3 minutes.

[edit 2] rfkill is unrelated, that is happening through connmanctl enable/disable toggle. nbd.

[edit 3] Reinstalled b43-firmware, didn't fix it, tried downgrading to previous version, that didn't work. Tried broadcom-wl from the AUR,that didn't fix it either, so it's not the driver ****scratching my head*****.

Last edited by oktorok (2014-08-22 00:24:03)

dice · 2014-08-22 11:01:35

Just to clarify: Your is problem is that after some random period of time your wifi connection stops working although it is shown as connected?
Maybe your connection is working but it's some strange DNS issue or something(just a wild guess). To sort that out:
How do you notice that it stopped? Try ping to different hosts.
Is this limited to internet connections or is your local network connection blocked too?

oktorok · 2014-08-22 17:13:30

Thats about right. A short time (minutes) after connecting, data transfer stops, the usual indicator is a webpage gets stuck on 10% loaded and hangs there, then I ping google, and I'll have 100% packet loss. iwconfig reveals that I am still conect to the AP, but that the signal level has dropped to 0. Sometimes, after some seemingly random amount of time, data transfer will pick up again, signal level goes back to a normal number, and then the cycle continues. I'm taking a 24 hr break from the problem, but I'll try the DNS troubleshooting then. I'm also going to work on the clue that signal level is dropping to zero. Why would that happen?

ewaller · 2014-08-22 17:38:00

What network related services are you starting from systemd? There should only be one. If you are using netctl, do not also start dhcpcd, dhclient, etc... netctl will start them when needed.

What is the output of systemctl status--no-pager
?

oktorok · 2014-08-22 20:02:57

If you are using netctl, do not also start dhcpcd, dhclient, etc... netctl will start them when needed.

That part I'm aware of. When I first switched to connman I had to work through that a little bit, disabling all my profiles, but found the connection issues therein were more severe, as opposed to the random signal-level-dropping-to-zero data timeouts. Just to be sure that I am not mismanaging my network services, here is the output of systemctl status --no-pager:

% systemctl status --no-pager                                                                                                                                ~
* arch
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Fri 2014-08-22 12:39:10 PDT; 3min 24s ago
   CGroup: /
           |-1 /sbin/init \boot\vmlinuz-linux
           |-system.slice
           | |-dbus.service
           | | `-279 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
           | |-connman-vpn.service
           | | `-312 /usr/bin/connman-vpnd -n
           | |-wpa_supplicant.service
           | | `-311 /usr/bin/wpa_supplicant -u
           | |-mbpfan.service
           | | `-282 /usr/sbin/mbpfan -fv
           | |-systemd-journald.service
           | | `-150 /usr/lib/systemd/systemd-journald
           | |-connman.service
           | | `-277 /usr/bin/connmand -n
           | |-systemd-logind.service
           | | `-278 /usr/lib/systemd/systemd-logind
           | `-systemd-udevd.service
           |   `-172 /usr/lib/systemd/systemd-udevd
           `-user.slice
             `-user-1000.slice
               |-user@1000.service
               | |-318 /usr/lib/systemd/systemd --user
               | `-320 (sd-pam)
               `-session-c1.scope
                 |- 295 login -- username
                 |- 327 -zsh
                 |-2204 /bin/sh /usr/bin/startx
                 |-2221 xinit /home/username/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.b8L2nSBC4F
                 |-2222 /usr/bin/Xorg.bin -nolisten tcp :0 -auth /tmp/serverauth.b8L2nSBC4F vt1
                 |-2224 xf86-video-intel-backlight-helper acpi_video0
                 |-2227 awesome
                 |-2232 dbus-launch --sh-syntax --exit-with-session
                 |-2233 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                 |-2245 urxvt
                 |-2247 unclutter
                 |-2250 redshift
                 |-2258 zsh
                 `-2304 systemctl status --no-pager

Thank you for double checking this for me. Right now I'm looking into the resolution presented in this thread. It seems like the pertinent information is contained in a dead link, but there is some stuff to go on. I haven't tinkered with module loading at all, but I'm in a "try anything" problem solving mindset. The really challenging part of this problem is that I can't find any log data. The signal level quietly drops to zero, but systemctl, connman, and journalctl don't log any issues.

[quick update] I've now had an hour and a half of stable connectivity after about 2 weeks of not being able to maintain a connection for more than 10 minutes. I didn't change anything since my troubleshooting from yesterday except boot into my MacOS install last night, then back into Arch today. I'm not optimistic that my problem has solved itself, but this is at least new information.

[quick update #2] Got a bunch of hours of connectivity, from about 1 pm to about 8 pm, then the old problem returned The wifi signal went to 0. I rebooted into MacOS, perfect connectivity, also on the same channel as in Arch.

Last edited by oktorok (2014-08-23 03:39:45)

Silex89 · 2014-08-23 14:02:31

I have the exact same issue with my laptop, a Sony VAIO SVF with a BCM43142. It seems to be a problem related to the module in this kernel in particular (linux 3.16.1). I found this by trying the linux-lts package in the repos (currently on the 3.14 cycle) and it works quite better than the latest version available.

Just a shot in the dark that seems to work for my chipset, at least. I'll be alert anyway because I want (and need) to use the latest kernel.

Best of Luck!

EDIT: Since my wireless network has never been supported on linux, I'm using the broadcom-wl(-dkms) package of the AUR. Not the b43 firmware that the OP uses.

Last edited by Silex89 (2014-08-23 14:13:05)

oktorok · 2014-08-23 19:28:23

Thanks for the tip Silex89, I will give that a shot later today then update this post after a trial. I didn't know about linux-lts, seems like a very handy thing to be aware of. Also, thanks for leading me to this great wiki.

oktorok · 2014-08-24 01:00:17

So is linux-lts a simple pacman install? I ran pacman -S linux-lts, but I'm still running arch 3.16. I see that it's installed, but apparently it's in conflict kernel26-lts, but I don't know if I'm reading this right:

% pacman -Qi linux-lts                                                       ~
Name           : linux-lts
Version        : 3.14.17-1
Description    : The Linux-lts kernel and modules
Architecture   : x86_64
URL            : http://www.kernel.org/
Licenses       : GPL2
Groups         : None
Provides       : kernel26-lts=3.14.17
Depends On     : coreutils  linux-firmware  kmod  mkinitcpio>=0.7
Optional Deps  : crda: to set the correct wireless channels of your country
                 [installed]
Required By    : None
Optional For   : None
Conflicts With : kernel26-lts
Replaces       : kernel26-lts
Installed Size : 71731.00 KiB
Packager       : Bart
Build Date     : Wed Aug 13 22:37:08 2014
Install Date   : Sat Aug 23 17:42:31 2014
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature

but

% uname -a                                                                    ~
Linux arch 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux

Last edited by oktorok (2014-08-24 01:02:01)

Silex89 · 2014-08-24 14:28:43

The linux-lts package is not a drop in placement of the default kernel. You have to manually generate a bootable image with mkinitcpio -p linux-lts and add the an entry for that kernel in your bootloader. That's why it doesn't conflict with any other kernel.

Silex89 · 2014-08-25 13:36:09

I've double checked with the latest kernel. I reinstalled the broadcom propietary driver and the problem persists for the most part. The signal stops dropping if I get close to the source of the WiFi signal. But if I move away a couple of meters, the connection gets sloppy and then fades.

Anyone else tried something different or found something?

mkraemer · 2014-09-01 16:51:58

I've got similar problems using my Macbook Air 11" and the Broadcom 4360 which I've described at
https://bbs.archlinux.org/viewtopic.php … 5#p1450435

I've had the chance to try various different combinations of kernels, driver versions (broadcom-ml) and settings regarding power saving, all resulting in the same, seemingly random intervalls of packet loss.
For the time being, I tried switching to using a wifi stick (Realtek RTL8192cu, using the 8192cu-dkms package in the aur) which started showing the exactly same behaviour.

Did you have any success using other wifi sticks in your systems?

Silex89 · 2014-09-01 18:18:22

I don't own a wifi stick unfortunately. But if you tried with different chipsets and you get the same results, the problem is not related to the driver.

I'm currently getting a good, stable internet connection by using USB tethering with my Galaxy S3... I don't know if that counts as a "wifi stick" (I guess it doesn't since my desktop detects it as a wired connection).

Let's wait for the next release of linux to see if it gets fixed. I've seen other distros' forums where they have a similar problem. So we will hopefully see this go away in the next point release of the kernel.

oktorok · 2014-09-01 19:22:12

I've had the chance to try various different combinations of kernels

Which kernels did you try?

mkraemer · 2014-09-01 20:28:57

Silex89 wrote:

I'm currently getting a good, stable internet connection by using USB tethering with my Galaxy S3... I don't know if that counts as a "wifi stick" (I guess it doesn't since my desktop detects it as a wired connection).

Yeah, same for me.. USB tethering works flawlessly.

oktorok wrote:

Which kernels did you try?

3.16.1-1-ARCH, 3.15.7-1-Arch and 3.14.17-1-LTS

Silex89 · 2014-09-02 13:23:51

Ok guys. A nice update here

I came across this thread https://bbs.archlinux.org/viewtopic.php … 5#p1452785 and I issued the commands of the first post and voilà!!!. My wireless connection is flawless. Stable and fast.

So it wasn't related to the driver, just a couple of systemd services competing each other. Though I don't know if this will work for you, since this bug manifests itself on fresh installations only (my case) and I'm using Network Manager with KDE...

Sheer happiness yay!!

Best of luck for you, guys.

ewaller · 2014-09-02 15:21:13

Silex89 wrote:

Ok guys. A nice update here ... just a couple of systemd services competing each other. ...

That is what I had been driving at back in post #6. The OP posted his systemctl status and did not have this problem.
Same symptom, different root cause. Anyway, glad yours is working.

oktorok · 2014-09-03 01:27:42

mkraemer,

I have another thread going (related to this one in that it will be a workaround for me if it actually works) related to problems with running off a second kernel. I'm dual booting with MacOs, and I'm assuming you are as well (maybe I'm wrong about that), but could you let me know on that thread if you have to do anything outside of the standard procedure:

# pacman -S linux-lts
# grub-mkconfig -o /boot/grub/grub.cfg 
# mkinitcpio -p linux-lts

mkraemer · 2014-09-05 09:19:43

Silex89 wrote:

Ok guys. A nice update here
I came across this thread https://bbs.archlinux.org/viewtopic.php … 5#p1452785 and I issued the commands of the first post and voilà!!!. My wireless connection is flawless. Stable and fast.
So it wasn't related to the driver, just a couple of systemd services competing each other. Though I don't know if this will work for you, since this bug manifests itself on fresh installations only (my case) and I'm using Network Manager with KDE...
Sheer happiness yay!!
Best of luck for you, guys.

Thank you for posting this
I'm on a fresh installation too but not using network manager.. Unfortunately, none of the services mentioned in this thread where enabled for me.

The only network related systemd service running was and is netctl-auto for me.

Strangely enough, I didn't experience the problems since two days anyway.. Not sure what changed, but I hope it lasts

oktorok wrote:

mkraemer,
I have another thread going (related to this one in that it will be a workaround for me if it actually works) related to problems with running off a second kernel. I'm dual booting with MacOs, and I'm assuming you are as well (maybe I'm wrong about that), but could you let me know on that thread if you have to do anything outside of the standard procedure:

Yes, I am dual booting, but not not using rEFInd... I'm using OSXs native EFI boot loader with a boot.efi created by GRUB.
Booting the lts kernel just worked for me, although I never bothered to create a GRUB entry for it - I just replaced linux by linux-lts in my normal GRUB entry temporarily when booting.
Sorry :\

oktorok · 2014-09-05 22:36:41

No prob! Thanks for resonding. I'm just going to stick with usb tethering for the time being and come back to troubleshooting some other time down the line. Hopefully it will fix itself.

Arch Linux

#1 2014-08-21 02:03:09

Intermittent Wifi

#2 2014-08-21 08:27:05

Re: Intermittent Wifi

#3 2014-08-21 20:58:32

Re: Intermittent Wifi

#4 2014-08-22 11:01:35

Re: Intermittent Wifi

#5 2014-08-22 17:13:30

Re: Intermittent Wifi

#6 2014-08-22 17:38:00

Re: Intermittent Wifi

#7 2014-08-22 20:02:57

Re: Intermittent Wifi

#8 2014-08-23 14:02:31

Re: Intermittent Wifi

#9 2014-08-23 19:28:23

Re: Intermittent Wifi

#10 2014-08-24 01:00:17

Re: Intermittent Wifi

#11 2014-08-24 14:28:43

Re: Intermittent Wifi

#12 2014-08-25 13:36:09

Re: Intermittent Wifi

#13 2014-09-01 16:51:58

Re: Intermittent Wifi

#14 2014-09-01 18:18:22

Re: Intermittent Wifi

#15 2014-09-01 19:22:12

Re: Intermittent Wifi

#16 2014-09-01 20:28:57

Re: Intermittent Wifi

#17 2014-09-02 13:23:51

Re: Intermittent Wifi

#18 2014-09-02 15:21:13

Re: Intermittent Wifi

#19 2014-09-03 01:27:42

Re: Intermittent Wifi

#20 2014-09-05 09:19:43

Re: Intermittent Wifi

#21 2014-09-05 22:36:41

Re: Intermittent Wifi

Board footer