Client bridge stops working after a few hours

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

foreverstorm
Posts: 20
Joined: Mon Aug 24, 2009 2:17 pm

Client bridge stops working after a few hours

Postby foreverstorm » Sat Mar 10, 2012 3:01 am

I have a TP link WR1043ND with Gargoyle 1.5.4 running in wireless bridge/repeater mode to a TP link W8960N modem running on stock firmware. The bridge is not broadcasting a separate wireless repeater SSID as that seems to make my problems worse.

I use the WR1043ND to connect to my computer and NAS wirelessly to the W8960N modem so that I can both access the internet from my computer and stream movies from the NAS to my PS3 which is connected by ethernet to the W8960N. This is to overcome the fact that the WR1043ND is too far to wirelessly stream media to the PS3 as the PS3 operates only in wireless G mode.

I find that particularly when I stream video from the NAS (ethernet->WR1032ND->wireless bridge->W8960N->ethernet->PS3) that it will work perfectly for a while but a third of the way through a movie length feature it will stop streaming and the NAS will become inaccessible for anyone connected to the W8960N, while I can continue to access it from my computer which is connected to the WR1032ND by ethernet.

The internet will sometimes continue to work from my computer even though my computer or NAS cannot be accessed through the LAN by devices connected to the modem.

The only way to solve the problem once it occurs is to restart the WR1032ND.

I have tried several clean installs and different versions of Gargoyle to no avail.

Any help would be appreciated!

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: Client bridge stops working after a few hours

Postby mix » Sat Mar 10, 2012 9:07 am

Sounds like the wireless is crashing. You can try to ssh into the 1043nd via a computer connected to it with ethernet and view the results of the commands "dmesg" and "logread" and view the cause of the failure.
WRT54GL v1.1
Gargoyle 1.4.7

foreverstorm
Posts: 20
Joined: Mon Aug 24, 2009 2:17 pm

Re: Client bridge stops working after a few hours

Postby foreverstorm » Sun Mar 11, 2012 12:23 am

Thanks for the advice, when I'm back to Gargoyle I'll try it, but I'm on DD-WRT now and ssh won't enable for some reason.

The problem is more pronounced with DD-WRT. The connection seems to be stable unless I watch a something like a TV show from the PS3. Then a DLNA error will occur as the stream cuts out half way through the show. Clients wirelessly connected to the modem will continue to operate correctly and access the internet, but can no longer access the NAS through the bridge and the bridge won't let ethernet connected computers access the internet for a while.

The problem remains even after bridge is restarted - the modem has to be restarted for it to be fixed immediately, otherwise it might resolve in time.

I'm thinking this could specifically be a problem with the TD-W8960N and wireless clients in general but I don't know how I can possibly fix it; should I just buy another WR1043ND?

pbix
Developer
Posts: 1366
Joined: Fri Aug 21, 2009 5:09 pm

Re: Client bridge stops working after a few hours

Postby pbix » Sun Mar 11, 2012 10:33 am

I would recommend that you buy a NAS than can run Gargoyle. Stock firmware is notorious for crashing which is why we have Gargoyle in the first place. Then you need a good stable modem. I am not sure if you put your TD-W8960N in "bridge mode" or not but if not get a modem that can be put in bridge mode.

I am assuming this is a DSL link but you did not really say.
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM

foreverstorm
Posts: 20
Joined: Mon Aug 24, 2009 2:17 pm

Re: Client bridge stops working after a few hours

Postby foreverstorm » Tue Mar 13, 2012 3:33 am

I think there is a bit of confusion so I'll write out the network topology, I think there is a fundamental problem somewhere either in the WR1043ND being in wifi client bridge mode or the W8960N in dealing with a wifi client bridge.

Lan 1: [NAS, PC1, PC2] --GigE-- { WR1043ND }
|
Wifi Client Bridge (20 MHz Wifi N, WPA2 AES)
|
Lan 2: [PS3] --FastEth-- { W8960N } -- Wifi -- [PC3, PC4, PC5...]
|
Internet

Now something or rather happens after a period of streaming from the NAS to the PS3, and clients on Lan 2 can't communicate with Lan 1, sometimes Lan 1 can still access the internet though the web interface of the W8960N won't be accessible. This problem can either then spontaneously resolve after half an hour or more, or a restart of the W8960N can solve it.

I think that WDS might be a better solution to have between Lan 1 and Lan 2 instead of a Wifi Client Bridge, but I can't get that to work.

I don't know if buying another WR1043ND and attaching it to the W8960N over FastEth and making it take over the client bridge between the it and the other WR1043ND will solve this, or what :?:

ekpyr
Posts: 9
Joined: Sat Mar 17, 2012 9:52 pm

Re: Client bridge stops working after a few hours

Postby ekpyr » Sat Mar 17, 2012 10:01 pm

I see a few of these threads on the forums.

I am also seeing dropouts. I have a similar setup. One main wr1043nd connected to the internet acting as an AP and a wr1043nd acting as a repeater/bridge. Both run 1.5.4.

The main wr1043nd AP works fine. Hasn't had any issues whatsoever. The repeater/bridge, however, has been going offline--the frequency depends on whether or not repeater mode is on. Leaving repeater off allowed the router to run for about a week before it crashed.

When it crashes, I'm unable to access the web management tool for the repeater/bridge. I am connected to it via ethernet. I did not try SSH, but will do that when it happens again.

ekpyr
Posts: 9
Joined: Sat Mar 17, 2012 9:52 pm

Re: Client bridge stops working after a few hours

Postby ekpyr » Sat Mar 17, 2012 10:54 pm

The wireless just cut out. I was in the middle of a SC2 game, so I switched the client router's WLAN mode to B and it came back up. Here's the log:

Around Mar 17 19:41:56 is when I think I switched wireless modes. Is this some sort of WPA issue?

Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-alauda
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-cypress
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-datafab
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-freecom
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-isd200
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-jumpshot
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-karma
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-sddr09
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-sddr55
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver ums-usbat
Dec 31 16:00:28 office user.info kernel: USB Serial support registered for GSM modem (1-port)
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver option
Dec 31 16:00:28 office user.info kernel: option: v0.7.2:USB Driver for GSM modems
Dec 31 16:00:28 office user.info kernel: USB Serial support registered for Sierra USB modem
Dec 31 16:00:28 office user.info kernel: usbcore: registered new interface driver sierra
Dec 31 16:00:28 office user.info kernel: sierra: v.1.3.8:USB Driver for Sierra Wireless USB modems
Dec 31 16:00:29 office user.info kernel: fuse init (API version 7.13)
Dec 31 16:00:30 office user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_2.6.32.27_ehci_hcd Product=Atheros_AR91xx_built-in_EHCI_controller Serial=ar71xx-ehci
Dec 31 16:00:32 office user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_2.6.32.27_ehci_hcd Product=Atheros_AR91xx_built-in_EHCI_controller Serial=ar71xx-ehci
Dec 31 16:00:33 office user.info kernel: device wlan0 entered promiscuous mode
Mar 17 16:00:01 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 16:00:01 office user.debug kernel: wlan0: authenticated
Mar 17 16:00:01 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 16:00:01 office user.debug kernel: wlan0: RX AssocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 16:00:01 office user.debug kernel: wlan0: associated
Mar 17 16:00:01 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 16:00:02 office user.info sysinit: Loading defaults
Mar 17 16:00:02 office user.info sysinit: Loading synflood protection
Mar 17 16:00:02 office user.info sysinit: Adding custom chains
Mar 17 16:00:03 office user.info sysinit: Loading zones
Mar 17 16:00:04 office user.info sysinit: Loading forwardings
Mar 17 16:00:04 office user.info sysinit: Loading redirects
Mar 17 16:00:04 office user.info sysinit: Loading rules
Mar 17 16:00:04 office user.info sysinit: Loading includes
Mar 17 16:00:05 office user.info sysinit: uci: Entry not found
Mar 17 16:00:05 office user.info sysinit: Optimizing conntrack
Mar 17 16:00:05 office user.info sysinit: Loading interfaces
Mar 17 16:00:05 office user.info firewall: adding lan (br-lan) to zone lan
Mar 17 16:00:06 office cron.err crond[1361]: crond (busybox 1.15.3) started, log level 9
Mar 17 16:00:06 office authpriv.info dropbear[1373]: Running in background
Mar 17 16:00:07 office daemon.warn httpd_gargoyle[1399]: started as root without requesting chroot(), warning only
Mar 17 16:00:07 office daemon.notice httpd_gargoyle[1399]: httpd_gargoyle/1.0 14mar2008 starting on office, port 80
Mar 17 16:00:09 office daemon.warn exportfs[1427]: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Mar 17 16:00:09 office user.info sysinit: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Mar 17 16:00:09 office daemon.err exportfs[1427]: can't lock /var/lib/nfs/etab for writing
Mar 17 16:00:09 office user.info sysinit: exportfs: can't lock /var/lib/nfs/etab for writing
Mar 17 16:00:10 office user.info sysinit: ERROR: No valid dynamic DNS service configurations defined
Mar 17 16:00:10 office user.info sysinit: (Did you specify correct configuration file path?)
Mar 17 16:00:10 office user.info sysinit: setting up led WLAN
Mar 17 16:00:10 office user.debug kernel: ar71xx-wdt: enabling watchdog timer
Mar 17 16:00:11 office user.notice root: starting ntpclient
Mar 17 18:43:42 office cron.err crond[1484]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:43:58 office user.warn kernel: ipt_bandwidth: timezone shift of 420 minutes detected, adjusting
Mar 17 18:43:58 office user.warn kernel: old minutes west=0, new minutes west=420
Mar 17 18:43:59 office cron.err crond[1822]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:47:59 office user.debug kernel: wlan0: deauthenticated from f8:d1:11:88:6c:f4 (Reason: 2)
Mar 17 18:47:59 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 18:48:09 office cron.err crond[2799]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:48:09 office cron.err crond[2850]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:48:09 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:48:09 office user.debug kernel: wlan0: authenticated
Mar 17 18:48:09 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:48:09 office user.debug kernel: wlan0: RX ReassocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 18:48:09 office user.debug kernel: wlan0: associated
Mar 17 18:48:09 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 18:48:11 office user.notice root: stopping ntpclient
Mar 17 18:48:12 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 18:48:12 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 18:48:12 office user.info kernel: device eth0 left promiscuous mode
Mar 17 18:48:12 office user.debug kernel: wlan0: deauthenticating from f8:d1:11:88:6c:f4 by local choice (reason=3)
Mar 17 18:48:12 office user.info kernel: device wlan0 left promiscuous mode
Mar 17 18:48:12 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 18:48:12 office user.info kernel: device eth0.1 left promiscuous mode
Mar 17 18:48:12 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 18:48:18 office user.notice ifup: Enabling Router Solicitations on loopback (lo)
Mar 17 18:48:19 office user.info kernel: device eth0.1 entered promiscuous mode
Mar 17 18:48:19 office user.info kernel: device eth0 entered promiscuous mode
Mar 17 18:48:19 office user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Mar 17 18:48:20 office user.info kernel: device wlan0 entered promiscuous mode
Mar 17 18:48:21 office user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Mar 17 18:48:21 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:48:21 office user.debug kernel: wlan0: authenticated
Mar 17 18:48:21 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:48:21 office user.debug kernel: wlan0: RX AssocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 18:48:21 office user.debug kernel: wlan0: associated
Mar 17 18:48:21 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 18:48:24 office user.notice root: starting ntpclient
Mar 17 18:48:24 office user.info firewall: adding lan (br-lan) to zone lan
Mar 17 18:48:41 office cron.err crond[4559]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:49:43 office cron.err crond[5048]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:49:44 office cron.err crond[5099]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:49:46 office user.notice root: stopping ntpclient
Mar 17 18:49:47 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 18:49:47 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 18:49:47 office user.info kernel: device eth0 left promiscuous mode
Mar 17 18:49:47 office user.info kernel: device wlan0 left promiscuous mode
Mar 17 18:49:47 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 18:49:47 office user.info kernel: device eth0.1 left promiscuous mode
Mar 17 18:49:47 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 18:49:48 office user.debug kernel: wlan0: deauthenticating from f8:d1:11:88:6c:f4 by local choice (reason=3)
Mar 17 18:49:53 office user.notice ifup: Enabling Router Solicitations on loopback (lo)
Mar 17 18:49:54 office user.info kernel: device eth0.1 entered promiscuous mode
Mar 17 18:49:54 office user.info kernel: device eth0 entered promiscuous mode
Mar 17 18:49:54 office user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Mar 17 18:49:55 office user.info kernel: device wlan0 entered promiscuous mode
Mar 17 18:49:56 office user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Mar 17 18:49:56 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:49:56 office user.debug kernel: wlan0: authenticated
Mar 17 18:49:56 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 18:49:56 office user.debug kernel: wlan0: RX AssocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 18:49:56 office user.debug kernel: wlan0: associated
Mar 17 18:49:56 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 18:49:56 office user.notice root: starting ntpclient
Mar 17 18:49:59 office user.info firewall: adding lan (br-lan) to zone lan
Mar 17 18:50:13 office cron.err crond[6971]: crond (busybox 1.15.3) started, log level 9
Mar 17 18:51:04 office authpriv.info dropbear[7353]: Child connection from 192.168.1.189:62459
Mar 17 18:51:08 office authpriv.warn dropbear[7353]: Login attempt for nonexistent user from 192.168.1.189:62459
Mar 17 18:51:12 office authpriv.info dropbear[7353]: Exit before auth: Error reading: Connection reset by peer
Mar 17 18:51:14 office authpriv.info dropbear[7354]: Child connection from 192.168.1.189:62461
Mar 17 18:51:19 office authpriv.notice dropbear[7354]: Password auth succeeded for 'root' from 192.168.1.189:62461
Mar 17 19:05:28 office cron.err crond[9353]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:05:28 office cron.err crond[9404]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:05:30 office user.notice root: stopping ntpclient
Mar 17 19:05:31 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:05:31 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:05:31 office user.info kernel: device eth0 left promiscuous mode
Mar 17 19:05:31 office user.info kernel: device wlan0 left promiscuous mode
Mar 17 19:05:31 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:05:31 office user.info kernel: device eth0.1 left promiscuous mode
Mar 17 19:05:31 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:05:33 office user.debug kernel: wlan0: deauthenticating from f8:d1:11:88:6c:f4 by local choice (reason=3)
Mar 17 19:05:37 office user.notice ifup: Enabling Router Solicitations on loopback (lo)
Mar 17 19:05:38 office user.info kernel: device eth0.1 entered promiscuous mode
Mar 17 19:05:38 office user.info kernel: device eth0 entered promiscuous mode
Mar 17 19:05:38 office user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Mar 17 19:05:39 office user.info kernel: device wlan0 entered promiscuous mode
Mar 17 19:05:40 office user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Mar 17 19:05:40 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:05:40 office user.debug kernel: wlan0: authenticated
Mar 17 19:05:40 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:05:40 office user.debug kernel: wlan0: RX AssocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 19:05:40 office user.debug kernel: wlan0: associated
Mar 17 19:05:40 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 19:05:43 office user.info firewall: adding lan (br-lan) to zone lan
Mar 17 19:05:51 office user.notice root: starting ntpclient
Mar 17 19:06:07 office cron.err crond[11095]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:09:10 office user.debug kernel: wlan0: deauthenticated from f8:d1:11:88:6c:f4 (Reason: 2)
Mar 17 19:09:10 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:09:20 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:09:20 office user.debug kernel: wlan0: authenticated
Mar 17 19:09:20 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:09:20 office user.debug kernel: wlan0: RX ReassocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 19:09:20 office user.debug kernel: wlan0: associated
Mar 17 19:09:20 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 19:41:56 office cron.err crond[13239]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:41:57 office cron.err crond[13290]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:41:58 office user.notice root: stopping ntpclient
Mar 17 19:41:59 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:41:59 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:41:59 office user.info kernel: device eth0 left promiscuous mode
Mar 17 19:41:59 office user.info kernel: device wlan0 left promiscuous mode
Mar 17 19:41:59 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:41:59 office user.info kernel: device eth0.1 left promiscuous mode
Mar 17 19:41:59 office user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:42:01 office user.debug kernel: wlan0: deauthenticating from f8:d1:11:88:6c:f4 by local choice (reason=3)
Mar 17 19:42:09 office user.notice ifup: Enabling Router Solicitations on loopback (lo)
Mar 17 19:42:11 office user.info kernel: device eth0.1 entered promiscuous mode
Mar 17 19:42:11 office user.info kernel: device eth0 entered promiscuous mode
Mar 17 19:42:11 office user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Mar 17 19:42:12 office user.info kernel: device wlan0 entered promiscuous mode
Mar 17 19:42:12 office user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Mar 17 19:42:12 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:42:12 office user.debug kernel: wlan0: authenticated
Mar 17 19:42:12 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:42:12 office user.debug kernel: wlan0: RX AssocResp from f8:d1:11:88:6c:f4 (capab=0x411 status=0 aid=1)
Mar 17 19:42:12 office user.debug kernel: wlan0: associated
Mar 17 19:42:12 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 19:42:15 office user.notice root: starting ntpclient
Mar 17 19:42:16 office user.info firewall: adding lan (br-lan) to zone lan
Mar 17 19:42:32 office cron.err crond[14982]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:47:57 office user.debug kernel: wlan0: deauthenticated from f8:d1:11:88:6c:f4 (Reason: 2)
Mar 17 19:47:57 office user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:48:07 office user.debug kernel: wlan0: authenticate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:48:07 office user.debug kernel: wlan0: authenticated
Mar 17 19:48:07 office user.debug kernel: wlan0: associate with f8:d1:11:88:6c:f4 (try 1)
Mar 17 19:48:07 office user.debug kernel: wlan0: RX ReassocResp from f8:d1:11:88:6c:f4 (capab=0x11 status=0 aid=1)
Mar 17 19:48:07 office user.debug kernel: wlan0: associated
Mar 17 19:48:07 office user.info kernel: br-lan: port 2(wlan0) entering forwarding state

ekpyr
Posts: 9
Joined: Sat Mar 17, 2012 9:52 pm

Re: Client bridge stops working after a few hours

Postby ekpyr » Sat Mar 17, 2012 11:03 pm

Interesting... logs for the gateway (main AP). It looks like it spontaneously restarted?


Mar 17 19:29:18 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b WPA: group key handshake completed (RSN)
Mar 17 19:29:18 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac WPA: group key handshake completed (RSN)
Mar 17 19:29:19 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa WPA: group key handshake completed (RSN)
Mar 17 19:39:18 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 WPA: group key handshake completed (RSN)
Mar 17 19:39:18 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa WPA: group key handshake completed (RSN)
Mar 17 19:39:18 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac WPA: group key handshake completed (RSN)
Mar 17 19:39:18 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b WPA: group key handshake completed (RSN)
Mar 17 19:42:12 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: authenticated
Mar 17 19:42:13 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: associated (aid 1)
Mar 17 19:42:13 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 WPA: pairwise key handshake completed (RSN)
Mar 17 19:47:51 gateway cron.err crond[10914]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:47:51 gateway cron.err crond[10965]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:47:52 gateway daemon.info dnsmasq[8271]: exiting on receipt of SIGTERM
Mar 17 19:47:53 gateway user.notice root: stopping ntpclient
Mar 17 19:47:54 gateway user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:47:54 gateway user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:47:54 gateway user.info kernel: device eth0 left promiscuous mode
Mar 17 19:47:54 gateway user.info kernel: device wlan0 left promiscuous mode
Mar 17 19:47:54 gateway user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:47:54 gateway user.info kernel: device eth0.1 left promiscuous mode
Mar 17 19:47:54 gateway user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Mar 17 19:48:01 gateway user.notice ifup: Enabling Router Solicitations on loopback (lo)
Mar 17 19:48:02 gateway user.info kernel: device eth0.1 entered promiscuous mode
Mar 17 19:48:02 gateway user.info kernel: device eth0 entered promiscuous mode
Mar 17 19:48:02 gateway user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Mar 17 19:48:04 gateway user.notice ifup: Enabling Router Solicitations on lan (br-lan)
Mar 17 19:48:05 gateway user.info kernel: device wlan0 entered promiscuous mode
Mar 17 19:48:05 gateway user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 19:48:07 gateway user.notice ifup: Allowing Router Advertisements on wan (eth0.2)
Mar 17 19:48:07 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: authenticated
Mar 17 19:48:07 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: associated (aid 1)
Mar 17 19:48:07 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:07 gateway user.notice root: starting ntpclient
Mar 17 19:48:08 gateway user.info kernel: device wlan0 left promiscuous mode
Mar 17 19:48:08 gateway user.info kernel: br-lan: port 2(wlan0) entering disabled state
Mar 17 19:48:08 gateway user.info kernel: device wlan0 entered promiscuous mode
Mar 17 19:48:08 gateway user.info kernel: br-lan: port 2(wlan0) entering forwarding state
Mar 17 19:48:11 gateway user.info firewall: adding lan (br-lan) to zone lan
Mar 17 19:48:11 gateway user.info firewall: adding wan (eth0.2) to zone wan
Mar 17 19:48:12 gateway user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Mar 17 19:48:12 gateway user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Mar 17 19:48:13 gateway cron.err crond[12865]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:48:15 gateway cron.err crond[13203]: crond (busybox 1.15.3) started, log level 9
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: started, version 2.55 cachesize 150
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
Mar 17 19:48:15 gateway daemon.info dnsmasq-dhcp[13219]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 78.47.86.43#53 for domain bit
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 178.32.31.41#53 for domain bit
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using local addresses only for domain lan
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: reading /tmp/resolv.conf.auto
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 209.18.47.62#53
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 209.18.47.61#53
Mar 17 19:48:15 gateway daemon.warn dnsmasq[13219]: ignoring nameserver 192.168.1.1 - local interface
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain micro
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain oss
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain null
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain ing
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain indy
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain gopher
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain geek
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain fur
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain free
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain bbs
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain dyn
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain parody
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.142.171.235#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 95.211.32.162#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 66.244.95.20#53 for domain glue
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 78.47.86.43#53 for domain bit
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using nameserver 178.32.31.41#53 for domain bit
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: using local addresses only for domain lan
Mar 17 19:48:15 gateway daemon.info dnsmasq[13219]: read /etc/hosts - 3 addresses
Mar 17 19:48:15 gateway daemon.info dnsmasq-dhcp[13219]: read /etc/ethers - 0 addresses
Mar 17 19:48:16 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac IEEE 802.11: authenticated
Mar 17 19:48:16 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac IEEE 802.11: authenticated
Mar 17 19:48:16 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac IEEE 802.11: associated (aid 2)
Mar 17 19:48:16 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:16 gateway daemon.info dnsmasq-dhcp[13219]: DHCPREQUEST(br-lan) 192.168.1.152 10:93:e9:07:09:ac
Mar 17 19:48:16 gateway daemon.info dnsmasq-dhcp[13219]: DHCPACK(br-lan) 192.168.1.152 10:93:e9:07:09:ac SMOLTM021
Mar 17 19:48:17 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa IEEE 802.11: authenticated
Mar 17 19:48:17 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa IEEE 802.11: associated (aid 3)
Mar 17 19:48:17 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:17 gateway daemon.info dnsmasq-dhcp[13219]: DHCPREQUEST(br-lan) 192.168.1.151 40:a6:d9:b0:66:aa
Mar 17 19:48:17 gateway daemon.info dnsmasq-dhcp[13219]: DHCPACK(br-lan) 192.168.1.151 40:a6:d9:b0:66:aa Eves-iPhone
Mar 17 19:48:30 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b IEEE 802.11: authenticated
Mar 17 19:48:30 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b IEEE 802.11: associated (aid 4)
Mar 17 19:48:30 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:30 gateway daemon.info dnsmasq-dhcp[13219]: DHCPREQUEST(br-lan) 192.168.1.148 40:a6:d9:5a:1c:0b
Mar 17 19:48:30 gateway daemon.info dnsmasq-dhcp[13219]: DHCPACK(br-lan) 192.168.1.148 40:a6:d9:5a:1c:0b Vibols-iPhone
Mar 17 19:58:06 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 WPA: group key handshake completed (RSN)
Mar 17 19:58:06 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:b0:66:aa WPA: group key handshake completed (RSN)
Mar 17 19:58:06 gateway daemon.info hostapd: wlan0: STA 10:93:e9:07:09:ac WPA: group key handshake completed (RSN)
Mar 17 19:58:06 gateway daemon.info hostapd: wlan0: STA 40:a6:d9:5a:1c:0b WPA: group key handshake completed (RSN)
Mar 17 19:59:35 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: authenticated
Mar 17 19:59:35 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 IEEE 802.11: associated (aid 1)
Mar 17 19:59:35 gateway daemon.info hostapd: wlan0: STA f8:d1:11:7f:6c:60 WPA: pairwise key handshake completed (RSN)
Mar 17 20:01:31 gateway authpriv.info dropbear[13702]: Child connection from 192.168.1.189:49613
Mar 17 20:01:37 gateway authpriv.notice dropbear[13702]: Password auth succeeded for 'root' from 192.168.1.189:49613

foreverstorm
Posts: 20
Joined: Mon Aug 24, 2009 2:17 pm

Re: Client bridge stops working after a few hours

Postby foreverstorm » Wed Mar 28, 2012 12:13 pm

Ok, I got 2x Asus RT-N56U so that I could have a 5ghz bridge RT-N56U from my room to the lounge, where everyone connects to the second RT-N56U on the 2.4ghz channel, and it is wired over ethernet to my WR1043ND with gargoyle on it.

A few problems with connectivity I was having I solved by simply placing both routers in the lounge away from the PS3, which was causing wireless interference. But I still have remaining issues.

In particular, I have a wireless client bridge from the WR143ND to the W8960N ADSL modem. For some reason, every so often the connection becomes very slow (when I run a ping test on pingtest.net the latency jumps from 49 to 400 and with about as much jitter). I can barely get access to the W8960N configuration page.

All I do is reboot Gargoyle and problem solved. So why is it slowing down so randomly and so much? Is there any test I can do to narrow it down? I've disabled UPNP and the only special features I'm running are client bridge and QoS.

User avatar
DoesItMatter
Moderator
Posts: 1373
Joined: Thu May 21, 2009 3:56 pm

Re: Client bridge stops working after a few hours

Postby DoesItMatter » Thu Mar 29, 2012 12:58 am

Simple test is to disable QoS and only use the client bridge portion

That will determine whether or not its wireless stability and/or
the router crashing due to cpu overload
:twisted: Soylent Green Is People! :twisted:
2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400


Return to “Network / Wireless Issues”

Who is online

Users browsing this forum: No registered users and 8 guests