intermittent wireless

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Wed Jan 21, 2015 5:40    Post subject: intermittent wireless Reply with quote
Hi,

My set up is a zoom cable modem/router 5352 as the AP. I have three Cisco routers running wireless as repeater bridges. I configured these following religiously the dd-wrt wiki. They are a couple of WRT54G and a WRT54G2, all of them running with build 25697 mini except the last one running micro, all of them connected to the zoom router with virtual interface (different SSIDs from each other and from the AP).

The problem that is driving me crazy is that all of them will work fine for a few seconds, freeze for another few and so on. The Status/Wireless show different number of transmit errors for each device and no Receive errors. I collected advice from older postings and these are the things I tried:

1. Keep the transmit power at or below 84mW,
2. Clone the MAC addresses,
3. Make the sensitivity range (ACK Timing) equal to zero,
4. Change the security settings (now running WPA2/AES),
5. Change the channel number & bandwidth in the main router,
6. Tried different builds.

None of these worked for me. Any ideas?

Thanks
Sponsor
Murrkf
DD-WRT Guru


Joined: 22 Sep 2008
Posts: 11763

PostPosted: Wed Jan 21, 2015 19:09    Post subject: Reply with quote
Try following all advice in the peacock announcement, including build advice for those older router. You might find that those routers lack the power to do what you need them to do.
_________________
SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor. So See this:
http://i31.tinypic.com/24mz3ms.png

LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Wed Jan 21, 2015 23:09    Post subject: Reply with quote
I read the posting and followed the recommendation on the builds. So I installed 14929 and so far it seems to be running OK. The transmit errors are very few and I haven't seen any intermittance to now.

Thank you very much for your help.

Daniel
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Thu Jan 22, 2015 4:39    Post subject: Reply with quote
Unfortunately, the intermittance is still there. One more piece of information: if I ping from any of the wireless connected machines (that are wired-connected to the repeater bridges) to the AP main router, I don't miss any packet. On the other hand if I ping from the same machine to an external site, e.g. google.com then I miss lots of packets. Does this mean anything?
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Fri Jan 23, 2015 19:04    Post subject: Reply with quote
bump
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Sat Jan 24, 2015 20:49    Post subject: Reply with quote
I made some progress. As I said in a previous posting, I had three repeater bridges all connected wirelessly to the main AP router. I noticed that one of them was "freezing" more often than the others. This one had three machines connected with ethernet wires to the LAN ports. So I thought that perhaps is not that the wireless link was freezing but that the router/switch could not handle these three machines, being one of them a lightly loaded mail server (SMTP port 25). I unplugged this and another machine and ping'ed back to google.com with the only one connected. Voila! This time it was zero packet loss. So the issue seems to be how the router operates regarding the switching. I wonder if there would be a way to make it "smoother" rather than completely stopping one or more of the ports.
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Tue Jan 27, 2015 19:09    Post subject: Reply with quote
By using the program "nethog" I could see that the actual internet traffic was minimal, so why is that accessing the internet is so choppy? Is there any thing inherent to dd-wrt or the wrt54g that makes this problem to arise?
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Sat Jan 31, 2015 23:34    Post subject: Reply with quote
As I wrote in my previous posting, I thought that perhaps the WRT54G was not capable of handling three machines hooked up to the ethernet ports (albeit very light traffic) I replaced the WRT54G with the RT-AC66U that is considered one of the fastest routers today. I successfully installed build 25974 (26081 has wireless issues) and set it up as repeater bridge. But when I tried pinging google.com the problem is still there, about 20% of packets lost. As I said before, there are no packets lost when pinging to the main router that seems to indicate that the wireless connection is fine, so can some expert suggest what could be the problem?
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Mon Feb 02, 2015 19:00    Post subject: Reply with quote
anybody?
danielsender
DD-WRT Novice


Joined: 12 Aug 2010
Posts: 40

PostPosted: Tue Feb 03, 2015 0:06    Post subject: Reply with quote
In case somebody can figure this out, I'm attaching the /var/log/messages of the router:
Quote:
Feb 1 20:33:35 DD-WRT syslog.info syslogd started: BusyBox v1.23.0
Feb 1 20:33:35 DD-WRT user.info syslog: syslogd : syslog daemon successfully started
Feb 1 20:33:35 DD-WRT user.info syslog: klogd : klog daemon successfully started
Feb 1 20:33:35 DD-WRT kern.notice kernel: klogd started: BusyBox v1.23.0 (2015-01-20 07:38:37 CET)
Feb 1 20:33:35 DD-WRT kern.notice kernel: Linux version 3.10.65 (root@dd-wrt.buildserver) (gcc version 4.7.3 20121106 (prerelease) (Linaro GCC 4.7-2012.11) ) #5871 Tue Jan 20 07:40:17 CET 2015
Feb 1 20:33:35 DD-WRT kern.info kernel: CPU revision is: 00019749 (MIPS 74Kc)
Feb 1 20:33:35 DD-WRT kern.warn kernel: Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Feb 1 20:33:35 DD-WRT kern.notice kernel: found nvram at 1F0000
Feb 1 20:33:35 DD-WRT kern.info kernel: something wrong here. do not remap
Feb 1 20:33:35 DD-WRT kern.info kernel: Determined physical RAM map:
Feb 1 20:33:35 DD-WRT kern.info kernel: memory: 07fff000 @ 00000000 (usable)
Feb 1 20:33:35 DD-WRT kern.info kernel: memory: 07fff000 @ 87fff000 (usable)
Feb 1 20:33:35 DD-WRT kern.warn kernel: Zone ranges:
Feb 1 20:33:35 DD-WRT kern.warn kernel: Normal [mem 0x00000000-0x1fffffff]
Feb 1 20:33:35 DD-WRT kern.warn kernel: HighMem [mem 0x20000000-0x8fffdfff]
Feb 1 20:33:35 DD-WRT kern.warn kernel: Movable zone start for each node
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:00:09.0: reg 10: [mem 0x18008000-0x18008fff]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:00:09.0: reg 30: [mem 0x00000000-0x000007ff pref]
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bus 0
Feb 1 20:33:35 DD-WRT kern.info kernel: pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Feb 1 20:33:35 DD-WRT kern.info kernel: pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI/PCIe coreunit 0 is set to bus 1.
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.0: [14e4:5300] type 00 class 0x060000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.0: reg 10: [mem 0x00000000-0x00003fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.0: reg 18: [mem 0x00000000-0x07ffffff 64bit]
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bridge
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 6 new_cmd 6
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.0: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.1: [14e4:0000] type 00 class 0x060000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.1: reg 10: [mem 0x00000000-0x00003fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.1: reg 18: [mem 0x00000000-0x07ffffff 64bit]
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bridge
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 6 new_cmd 4
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:00.1: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:01.0: [14e4:4331] type 00 class 0x028000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:01.0: reg 10: [mem 0x00000000-0x00003fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:01:01.0: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bus 1
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI/PCIe coreunit 1 is set to bus 2.
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.0: [14e4:5300] type 00 class 0x060000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.0: reg 10: [mem 0x00000000-0x00003fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.0: reg 18: [mem 0x00000000-0x07ffffff 64bit]
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bridge
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 6 new_cmd 6
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.0: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.1: [14e4:0000] type 00 class 0x060000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.1: reg 10: [mem 0x00000000-0x00003fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.1: reg 18: [mem 0x00000000-0x07ffffff 64bit]
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bridge
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 6 new_cmd 4
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:00.1: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:01.0: [14e4:4360] type 00 class 0x028000
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:01.0: reg 10: [mem 0x00000000-0x00007fff 64bit]
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci 0000:02:01.0: supports D1 D2
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Fixing up bus 2
Feb 1 20:33:35 DD-WRT kern.debug kernel: pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
Feb 1 20:33:35 DD-WRT kern.info kernel: Switching to clocksource MIPS
Feb 1 20:33:35 DD-WRT kern.info kernel: NET: Registered protocol family 2
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: Hash tables configured (established 1024 bind 1024)
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: reno registered
Feb 1 20:33:35 DD-WRT kern.info kernel: UDP hash table entries: 256 (order: 0, 4096 bytes)
Feb 1 20:33:35 DD-WRT kern.info kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Feb 1 20:33:35 DD-WRT kern.info kernel: NET: Registered protocol family 1
Feb 1 20:33:35 DD-WRT kern.debug kernel: PCI: CLS 0 bytes, default 32
Feb 1 20:33:35 DD-WRT kern.emerg kernel: Asus-RT-AC66U init
Feb 1 20:33:35 DD-WRT kern.warn kernel: bounce pool size: 64 pages
Feb 1 20:33:35 DD-WRT kern.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
Feb 1 20:33:35 DD-WRT kern.info kernel: msgmni has been set to 210
Feb 1 20:33:35 DD-WRT kern.info kernel: io scheduler noop registered (default)
Feb 1 20:33:35 DD-WRT kern.info kernel: HDLC line discipline maxframe=4096
Feb 1 20:33:35 DD-WRT kern.info kernel: N_HDLC line discipline registered.
Feb 1 20:33:35 DD-WRT kern.info kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: scalable registered
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: lp registered
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: yeah registered
Feb 1 20:33:35 DD-WRT kern.info kernel: TCP: illinois registered
Feb 1 20:33:35 DD-WRT kern.info kernel: NET: Registered protocol family 17
Feb 1 20:33:35 DD-WRT kern.notice kernel: Bridge firewalling registered
Feb 1 20:33:35 DD-WRT kern.info kernel: 8021q: 802.1Q VLAN Support v1.8
Feb 1 20:33:35 DD-WRT kern.info kernel: startup nvram driver
Feb 1 20:33:35 DD-WRT kern.emerg kernel: found nvram
Feb 1 20:33:35 DD-WRT kern.info kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
Feb 1 20:33:35 DD-WRT kern.info kernel: Freeing unused kernel memory: 316K (80361000 - 803b0000)
Feb 1 20:33:35 DD-WRT kern.warn kernel: et: module license 'Proprietary' taints kernel.
Feb 1 20:33:35 DD-WRT kern.warn kernel: Disabling lock debugging due to kernel taint
Feb 1 20:33:35 DD-WRT kern.warn kernel: et_module_init: passivemode set to 0x0
Feb 1 20:33:35 DD-WRT kern.warn kernel: et_module_init: txworkq set to 0x0
Feb 1 20:33:35 DD-WRT kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Feb 1 20:33:35 DD-WRT kern.debug kernel: et 0000:00:01.0: setting latency timer to 64
Feb 1 20:33:35 DD-WRT kern.warn kernel: bcm_robo_enable_switch: EEE is disabled
Feb 1 20:33:35 DD-WRT kern.info kernel: et0: online cpus 1
Feb 1 20:33:35 DD-WRT kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.86 (r456083)
Feb 1 20:33:35 DD-WRT kern.info kernel: roboswitch: Probing device 'eth0'
Feb 1 20:33:35 DD-WRT kern.info kernel: roboswitch: trying a 53125! at eth0
Feb 1 20:33:35 DD-WRT kern.info kernel: roboswitch: found a 53125! at eth0
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 2 new_cmd 0
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Feb 1 20:33:35 DD-WRT kern.emerg kernel: cmd 2 new_cmd 0
Feb 1 20:33:35 DD-WRT kern.warn kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device wl0.1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device wl0.1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan2 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device wl0.1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device wl0.1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered disabled state
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.warn kernel: Hooks already unregistered
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device wl0.1 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device vlan2 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 3(wl0.1) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 4(eth2) entered forwarding state
Feb 1 20:33:35 DD-WRT kern.info kernel: br0: port 5(vlan2) entered forwarding state
Feb 1 20:33:37 DD-WRT user.info syslog: telnetd : telnet daemon successfully stopped
Feb 1 20:33:37 DD-WRT user.info syslog: pptpd : pptp daemon successfully stoped
Feb 1 20:33:37 DD-WRT user.info syslog: pptpd : pptp daemon successfully stoped
Feb 1 20:33:37 DD-WRT user.info syslog: telnetd : telnet daemon successfully started
Feb 1 20:33:38 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Feb 1 20:33:38 DD-WRT kern.notice kernel: klogd: exiting
Feb 1 20:33:38 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Feb 1 20:33:38 DD-WRT syslog.info syslogd exiting
Feb 1 20:33:38 DD-WRT syslog.info syslogd started: BusyBox v1.23.0
Feb 1 20:33:38 DD-WRT user.info syslog: klogd : klog daemon successfully started
Feb 1 20:33:38 DD-WRT kern.notice kernel: klogd started: BusyBox v1.23.0 (2015-01-20 07:38:37 CET)
Feb 1 20:44:58 DD-WRT user.info syslog: cron : cron daemon successfully stopped
Feb 1 20:44:59 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Feb 1 20:44:59 DD-WRT user.info syslog: wland : WLAN daemon successfully stopped
Feb 1 20:44:59 DD-WRT kern.notice kernel: klogd: exiting
Feb 1 20:44:59 DD-WRT user.info syslog: wland : WLAN daemon successfully started
Feb 1 20:44:59 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Feb 1 20:45:00 DD-WRT syslog.info syslogd exiting
Feb 1 20:45:00 DD-WRT syslog.info syslogd started: BusyBox v1.23.0
Feb 1 20:45:00 DD-WRT user.info syslog: klogd : klog daemon successfully started
Feb 1 20:45:00 DD-WRT kern.notice kernel: klogd started: BusyBox v1.23.0 (2015-01-20 07:38:37 CET)
Feb 1 20:45:00 DD-WRT cron.info cron[17977]: (CRON) STARTUP (fork ok)
Feb 1 20:45:00 DD-WRT cron.info cron[17977]: (crontabs) ORPHAN (no passwd entry)
Feb 1 20:51:55 DD-WRT user.info syslog: cron : cron daemon successfully stopped
Feb 1 20:51:56 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Feb 1 20:51:56 DD-WRT user.info syslog: wland : WLAN daemon successfully stopped
Feb 1 20:51:56 DD-WRT kern.notice kernel: klogd: exiting
Feb 1 20:51:56 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Feb 1 20:51:56 DD-WRT syslog.info syslogd exiting
Feb 1 20:51:57 DD-WRT syslog.info syslogd started: BusyBox v1.23.0
Feb 1 20:51:57 DD-WRT user.info syslog: klogd : klog daemon successfully started
Feb 1 20:51:57 DD-WRT kern.notice kernel: klogd started: BusyBox v1.23.0 (2015-01-20 07:38:37 CET)
Feb 1 20:55:05 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Feb 1 20:55:05 DD-WRT kern.notice kernel: klogd: exiting
Feb 1 20:55:05 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Feb 1 20:55:05 DD-WRT syslog.info syslogd exiting[code]

Thanks.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum