Yea it keeps his GB+ downloads somewhat under control.
Anything linked to my server will likely be down for another couple hours at least......Never fails when you try to get away something happens. I just found out of major power outage at my place. My backup power for router and server only good for about 45 minutes.......dangit and I just now got my client bridge / AP setup at this RV Park
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Jul 03, 2015 20:37 Post subject:
mrjcd wrote:
tatsuya46 wrote:
why g-only for the boy? bandwidth limiting?
Yea it keeps his GB+ downloads somewhat under control.
Anything linked to my server will likely be down for another couple hours at least......Never fails when you try to get away something happens. I just found out of major power outage at my place. My backup power for router and server only good for about 45 minutes.......dangit and I just now got my client bridge / AP setup at this RV Park
u should use n, & use qos to limit down/uploads. when wifi link saturates it creates ugly latency thats ungamable, voip-able or anything. ie: saturated 802.11g at 21mbps = hundreds/thousands of ms, qos to achieve same limits (especially ddwrt qos) = 3-35ms increase & stable _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Fri Jul 03, 2015 21:33 Post subject: TP-Link TL-WR842ND
Router: TP-Link TL-WR842ND REV v2.1 <--not a mistake v2.1
Firmware: 06-27-2015-r27456/tplink_tl-wr842ndv2 (current)
Kernel: Linux 3.10.81 #5214 Sat Jun 27 02:54:51 CEST 2015 mips
CPU: Atheros AR9341 ver 1 rev 1.3 (0x0123) 1 core @ 535 MHz
Reset: 30/30/30 reset before and after
Status: Client Bridge (Routed) mode
Site Survey quality works very well. It can detect 30+ wireless devices.
Errors:
I can connect to my AP using client bridge mode but the wireless connection is unusable. I had the same the same problem with firmware:04-09-2015-r26653/tplink_tl-wr842ndv2/.
WR842ND v2.1 is a newly purchased router that I was hoping to replace my old WRT54G v8 (broadcom). But as you can see below the WR842ND connection is unstable trying to ping my AP's gateway. Webpages won't open, my AP's management page opens sometimes.
However, my WRT54G (client bridge mode - 06-27-2015-r27456/broadcom micro generic) in the same location does not drop any packets and usually has 1 or 2 ms response. My AP/router is Netgear WNDR3400v2 (stock firmware).
Reply from 192.168.1.1: bytes=32 time=3ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=16ms TTL=63
Reply from 192.168.1.1: bytes=32 time=17ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=34ms TTL=63
Reply from 192.168.1.1: bytes=32 time=58ms TTL=63
Reply from 192.168.1.1: bytes=32 time=18ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=51ms TTL=63
Reply from 192.168.1.1: bytes=32 time=6ms TTL=63
Reply from 192.168.1.1: bytes=32 time=19ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=2003ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=4ms TTL=63
Reply from 192.168.1.1: bytes=32 time=18ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=7ms TTL=63
Reply from 192.168.1.1: bytes=32 time=6ms TTL=63
Reply from 192.168.1.1: bytes=32 time=55ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=12ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=43ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Last edited by jewshawn2 on Sun Jul 05, 2015 14:11; edited 1 time in total
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Fri Jul 03, 2015 22:34 Post subject:
scrawnyb wrote:
@ KrypteX
I also have the "problematic" Buffalo WZR-HP-G300NH and suffer the same problem about NVRAM backups. I understand your stance regarding the nvram settings being restored from an older firmware, etc. Often this router will fail to upgrade properly, and it requires to TFTP recovery... blame it on the lack of a reset or whatever - that's fine.
But I think if you are saying that the nvram backup button cannot be trusted (to restore), then can we find an alternative to get a textual dump of those settings - so we have something to compare to after an upgrade/wipe? To quote you, I don't think that asking for (or implementing) a textual backup of NVRAM settings takes "rocket science". Or is this step 1 of the scripts the other users are discussing (with step 2 being the restore) ?
Also on a related note, is there any real information on here about the Unbound implementation or how to set it up?
The WZR-HP-G300NH used to upgrade via the GUI just fine until upgrade problems started at some version below 20000, if I remember right.
That's what made me go back to Buffalo's version of DD-WRT firmware 19484. Upgrading via TFTP was just too much fuss to be doing very often.
I was still working for a living back then ...
Back then there were no problems writing out nvram content into a text file. The test file was formatted as a valid script to be used for setting each nvram variable one by one and committing them in the last lines. It was dubbed Frater's script after the maker and can be found in the Wiki under Useful scripts. The idea was to only restore vaiables that were 'not dangerous'.
Selecting which variables were 'essential' was done using a list in an auxiliairy file.
It stands to reason that any lists of variable names were not typed up by the maker of the script, but conjured from NVRAM.
Just study the script and the description in the WIKI.
There's some stuff there concerning transfer of files using FTP, which I threw out of my private version regarding it clutter. Besides the FTP needed some module that I would have had to install. Not knowing how to pull that off, I decided I can copy the output files to a local disk manually using WinSCP just as well.
Running the script in the WIKI or the core part of it (without the FTP clutter) only reads the NVRAM content. That can do no harm. One of the output files contains all variables (names only perhaps).
The BIG problem with restoring from such a list/script is that NVRAM variables have names that you won't easily recognize and usually won't be able to locate in the GUI without much guess work.
Also, they won't be in any 'logical' order.
So, for manual restoring the output scripts are of very little help.
The output scripts of Frater's script really only have practical use when run on the router to restore 'essential' NVRAM content, the 'non-dangerous' variables one by one.
The script(s) really used to work a charm at the time. The procedure could still be useful, if only Frater's script doing the 'dumping' would run.
Unfortunately, there is a serious problem with the NVRAM backup command of the GUI in the latest versions. I assume it to be essentially the very same problem that stops Frater's script from running.
I think that what running the output from Frater's script does is comparable to setting variables in the GUI, and only saving them screen by screen until (you think) you're done. Then 'Apply settings'.
Current versions will no doubt have variables that didn't exist at the time Frater (and others) worked on the script. Some of those might be deemed 'essential' and 'not dangerous', so could be added to the list of essential variables that goes with the script.
Current versions may lack variables that were dropped in the course of firmware development. They might therefore be on the script/output file that one uses to restore settings. I don't know what exactly might happen to those in DD-WRT installations, but usually when a computer program sets variables that it never uses later on, no harm is done other than taking up a little extra memory.
It would be worth looking into. We do not all have enough time at hand to manually type and set all variables week after week.
(Naturally I have never tried to restore settings from script output made on firmware that wouldn't run the script. Only from older versions that ran Frater's script. Those restore scripts would have commands to set named variables to valid values in text form.)
If there are serious objections to this way of copying settings from one version to another, I would want to see them pointed out on this forum in an analytical way one by one.
Yea it keeps his GB+ downloads somewhat under control.
Anything linked to my server will likely be down for another couple hours at least......Never fails when you try to get away something happens. I just found out of major power outage at my place. My backup power for router and server only good for about 45 minutes.......dangit and I just now got my client bridge / AP setup at this RV Park
u should use n, & use qos to limit down/uploads. when wifi link saturates it creates ugly latency thats ungamable, voip-able or anything. ie: saturated 802.11g at 21mbps = hundreds/thousands of ms, qos to achieve same limits (especially ddwrt qos) = 3-35ms increase & stable
I don't have the internet speed to worry about anything over 15...
.... and the boy has no problems -- he spends hours on end talking/yelling/screaming at who ever is on the other end of his headset.
OK, so I was able to kinda reproduce the "Out of Memory" error (outside of running the nvram command) by trying to do some dd's on my Buffalo WZR-HP-G300NH router.
I have a USB device mounted for writing out and testing (then downloading the files from lighttpd to check contents).
Router: TL-WR841N v9.3
Firmware: DD-WRT v3.0-r27456 (06/27/15) std
Status: Working as Gateway
Reset: No
Errors:
1) WAN LED not working
2) Wifi LED not working
3) Status page is visible without password (it has mac addresses)
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Sat Jul 04, 2015 12:14 Post subject:
scrawnyb wrote:
OK, so I was able to kinda reproduce the "Out of Memory" error (outside of running the nvram command) by trying to do some dd's on my Buffalo WZR-HP-G300NH router.
I have a USB device mounted for writing out and testing (then downloading the files from lighttpd to check contents).
See the attached screenshot below.
Same result here (same router, same fw).
I ran the commands using WinSCP using a JFFS directory.
Using bs=131071 nvram.dd is 128 kB and it contains (a lot of) nvram content. Using bs=131072 the file length is zero.
Posted: Sat Jul 04, 2015 15:42 Post subject: Re: TP-Link TL-WR842ND
jewshawn2 wrote:
Router: TP-Link TL-WR842ND REV v2.1 <--not a mistake v2.1
Firmware: 06-27-2015-r27456/tplink_tl-wr842ndv2 (current)
Kernel: Linux 3.10.81 #5214 Sat Jun 27 02:54:51 CEST 2015 mips
CPU: Atheros AR9341 ver 1 rev 1.3 (0x0123) 1 core @ 535 MHz
Reset: 30/30/30 reset before and after
Status: Client Bridge (Routed) mode
Site Survey quality works very well. It can detect 30+ wireless devices.
Errors:
I can connect to my AP using client bridge mode but the wireless connection is unusable. I had the same the same problem with firmware:04-09-2015-r26653/tplink_tl-wr842ndv2/.
WR842ND v2.1 is a newly purchased router that I was hoping to replace my old WRT54G v8 (broadcom). But as you can see below the WR842ND connection is unstable trying to ping my AP's gateway. Webpages won't open, my AP's management page opens sometimes.
However, my WRT54G (client bridge mode - 06-27-2015-r27456/broadcom micro generic) in the same location does not drop any packets and usually has 1 or 2 ms response. My AP/router is Netgear WNDR3400v2 (stock firmware).
This is a very good value router/bridge which I bought x2 8dbi antennas with. I'd like to see the bridge function work on the Atheros chips.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=16ms TTL=63
Reply from 192.168.1.1: bytes=32 time=17ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=34ms TTL=63
Reply from 192.168.1.1: bytes=32 time=58ms TTL=63
Reply from 192.168.1.1: bytes=32 time=18ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=51ms TTL=63
Reply from 192.168.1.1: bytes=32 time=6ms TTL=63
Reply from 192.168.1.1: bytes=32 time=19ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.251: Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=2003ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=4ms TTL=63
Reply from 192.168.1.1: bytes=32 time=18ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=7ms TTL=63
Reply from 192.168.1.1: bytes=32 time=6ms TTL=63
Reply from 192.168.1.1: bytes=32 time=55ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=12ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=43ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
same problem with TL-WR740N v4.27 , any fix , or working firmware?
Router: TL-WDR4300 v1.6 as Router and V1.7 as WDS repeater
Firmware: DD-WRT v3.0-r27456
Kernel Version: Linux 3.10.81
Status: Running Stable and good
Reset: yes
Errors: 5ghz is dropping out
Dmesg
<6>[ 0.000000] CPU revision is: 0001974c (MIPS 74Kc)
<4>[ 0.000000] cpu srif ddr srif cpu 560 ddr 450 ahb 225
<6>[ 0.000000] sys id = 2122 Atheros AR9344 ver 1 rev 1.2 (0x2122)
<6>[ 0.000000] Determined physical RAM map:
<6>[ 0.000000] memory: 08000000 @ 00000000 (usable)
<4>[ 0.000000] Zone ranges:
<4>[ 0.000000] Normal [mem 0x00000000-0x07ffffff]
<4>[ 0.000000] Movable zone start for each node
<4>[ 0.000000] Early memory node ranges
<4>[ 0.000000] node 0: [mem 0x00000000-0x07ffffff]
<7>[ 0.000000] On node 0 totalpages: 32768
<7>[ 0.000000] free_area_init_node: node 0, pgdat 802d50a0, node_mem_map 81000000
<7>[ 0.000000] Normal zone: 256 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 32768 pages, LIFO batch:7
<4>[ 0.000000] Primary instruction cache 64kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
<4>[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
<7>[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>[ 0.000000] pcpu-alloc: [0] 0
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
<5>[ 0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
<6>[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>[ 0.000000] Writing ErrCtl register=00000000
<6>[ 0.000000] Readback ErrCtl register=00000000
<6>[ 0.000000] Memory: 126464k/131072k available (2215k kernel code, 4608k reserved, 391k data, 208k init, 0k highmem)
<6>[ 0.000000] NR_IRQS:83
<6>[ 0.060000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
<6>[ 0.060000] pid_max: default: 32768 minimum: 301
<6>[ 0.070000] Mount-cache hash table entries: 512
<6>[ 0.070000] NET: Registered protocol family 16
<4>[ 0.280000] registering PCI controller with io_map_base unset
<6>[ 0.290000] bio: create slab at 0
<6>[ 0.290000] PCI host bridge to bus 0000:00
<6>[ 0.290000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
<6>[ 0.290000] pci_bus 0000:00: root bus resource [io 0x0000]
<6>[ 0.290000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
<7>[ 0.290000] pci 0000:00:00.0: [168c:0033] type 00 class 0x028000
<6>[ 0.290000] pci 0000:00:00.0: fixup device configuration
<7>[ 0.290000] pci 0000:00:00.0: reg 10: [mem 0x00000000-0x0001ffff 64bit]
<7>[ 0.290000] pci 0000:00:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
<7>[ 0.290000] pci 0000:00:00.0: supports D1
<7>[ 0.290000] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
<7>[ 0.290000] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
<6>[ 0.290000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
<6>[ 0.290000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
<6>[ 0.290000] pci 0000:00:00.0: using irq 72 for pin 1
<6>[ 0.290000] Switching to clocksource MIPS
<6>[ 0.290000] NET: Registered protocol family 2
<6>[ 0.300000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
<6>[ 0.300000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
<6>[ 0.300000] TCP: Hash tables configured (established 1024 bind 1024)
<6>[ 0.300000] TCP: reno registered
<6>[ 0.300000] UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 0.300000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 0.300000] NET: Registered protocol family 1
<7>[ 0.300000] PCI: CLS 0 bytes, default 32
<5>[ 0.300000] gpio_proc: module loaded and /proc/gpio/ created
<5>[ 0.300000] wl0gpio_proc: module loaded and /proc/wl0gpio/ created
<6>[ 0.300000] squashfs: version 3.0 (2006/03/15) Phillip Lougher
<6>[ 0.300000] msgmni has been set to 247
<6>[ 0.300000] io scheduler noop registered
<6>[ 0.300000] io scheduler deadline registered (default)
<6>[ 0.300000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
<6>[ 0.310000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
<6>[ 0.620000] console [ttyS0] enabled
<0>[ 0.630000] guessed flashsize = 8M
<0>[ 0.630000] scanning for root partition
<0>[ 0.630000] tplink uboot detected
<0>[ 0.640000] guessed bootloader size = 20000
<0>[ 0.650000]
<0>[ 0.650000] found squashfs at 120000
<6>[ 0.650000] adjusted length 7D0000, original length 7C38B9
<5>[ 0.660000] Creating 9 MTD partitions on nal lear7240-nor0
<5>[ 0.670000] 0x000000000000-0x000000020000 : lear7RedBoot0
<5>[ 0.670000] 0x000000020000-0x0000007e0000 : lear7linux;t0
<5>[ 0.680000] 0x000000120000-0x0000007d0000 : lear7rootfst0
<5>[ 0.680000] mtd: partition 0x0000rootfs00 : set to be root filesystem
<5>[ 0.690000] 0x0000007d0000-0x0000007e0000 : set ddwrt;root
<5>[ 0.700000] 0x0000007e0000-0x0000007f0000 : set nvram;root
<5>[ 0.700000] 0x0000007f0000-0x000000800000 : set board_config
<5>[ 0.710000] 0x000000000000-0x000000800000 : set fullflashfig
<5>[ 0.720000] 0x000000000000-0x000000020000 : set fullboothfig
<5>[ 0.720000] 0x000000010000-0x000000020000 : set uboot-envfig
<6>[ 0.730000] libphy: Fixed MDIO Bus: probed
<6>[ 0.730000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 0.740000] tun: (C) 1999-2004 Max Krasnyansky
<6>[ 0.750000] PPP generic driver version 2.4.2
<6>[ 0.750000] PPP BSD Compression module registered
<6>[ 0.760000] PPP Deflate Compression module registered
<6>[ 0.760000] PPP MPPE Compression module registered
<6>[ 0.770000] NET: Registered protocol family 24
<6>[ 0.790000] u32 classifier
<6>[ 0.790000] Performance counters on
<6>[ 0.790000] input device check on
<6>[ 0.800000] Actions configured
<6>[ 0.800000] Netfilter messages via NETLINK v0.30.
<6>[ 0.800000] nf_conntrack version 0.5.0 (1976 buckets, 7904 max)
<4>[ 0.810000] nf_conntrack_rtsp v0.6.21 loading
<4>[ 0.820000] nf_nat_rtsp v0.6.21 loading
<6>[ 0.820000] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 0.830000] TCP: westwood registered
<6>[ 0.830000] TCP: hybla registered
<6>[ 0.830000] TCP: vegas registered
<6>[ 0.840000] NET: Registered protocol family 17
<5>[ 0.840000] Bridge firewalling registered
<6>[ 0.840000] 8021q: 802.1Q VLAN Support v1.8
<6>[ 0.850000] searching for nvram
<6>[ 0.850000] nvram size = 0
<6>[ 0.880000] Atheros AR71xx hardware watchdog driver version 0.1.0
<6>[ 0.890000] ar71xx-wdt: timeout=15 secs (max=107) ref freq=40000000
<6>[ 0.900000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
<6>[ 0.910000] Freeing unused kernel memory: 208K (802ec000 - 80320000)
<7>[ 3.240000] ar71xx-wdt: enabling watchdog timer
<6>[ 3.290000] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
<6>[ 3.360000] libphy: ag71xx_mdio: probed
<6>[ 3.960000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
<6>[ 3.970000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
<6>[ 4.280000] Loading modules backported from Linux version master-2015-06-22-0-g4732c92
<6>[ 4.290000] Backport generated by backports.git backports-20150612-0-g1b838d0
<6>[ 4.410000] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 4.440000] cfg80211: World regulatory domain updated:
<6>[ 4.440000] cfg80211: DFS Master region: unset
<6>[ 4.440000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[ 4.450000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 4.460000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 4.470000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 4.480000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 4.490000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 4.500000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<7>[ 4.920000] ath: EEPROM regdomain: 0x0
<7>[ 4.920000] ath: EEPROM indicates default country code should be used
<7>[ 4.920000] ath: doing EEPROM country->regdmn map search
<7>[ 4.920000] ath: country maps to regdmn code: 0x3a
<7>[ 4.920000] ath: Country alpha2 being used: US
<7>[ 4.920000] ath: Regpair used: 0x3a
<7>[ 4.930000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>[ 4.930000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=78
<4>[ 4.940000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
<7>[ 4.950000] ath: EEPROM regdomain: 0x0
<7>[ 4.950000] ath: EEPROM indicates default country code should be used
<7>[ 4.950000] ath: doing EEPROM country->regdmn map search
<7>[ 4.950000] ath: country maps to regdmn code: 0x3a
<7>[ 4.950000] ath: Country alpha2 being used: US
<7>[ 4.950000] ath: Regpair used: 0x3a
<7>[ 4.960000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
<6>[ 4.960000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=72
<6>[ 4.970000] cfg80211: Calling CRDA for country: US
<6>[ 4.970000] cfg80211: Regulatory domain changed to country: US
<6>[ 4.980000] cfg80211: DFS Master region: FCC
<6>[ 4.980000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[ 4.990000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[ 5.000000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[ 5.010000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[ 5.010000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[ 5.020000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[ 5.970000] eth0: link up (1000Mbps/Full duplex)
<6>[ 7.280000] device br0 entered promiscuous mode
<6>[ 7.340000] device vlan1 entered promiscuous mode
<6>[ 7.340000] device eth0 entered promiscuous mode
<6>[ 7.350000] br0: port 1(vlan1) entered forwarding state
<6>[ 7.350000] br0: port 1(vlan1) entered forwarding state
<6>[ 7.360000] device br0 left promiscuous mode
<6>[ 7.370000] device br0 entered promiscuous mode
<6>[ 7.410000] cfg80211: Calling CRDA to update world regulatory domain
<3>[ 7.430000] cfg80211: Invalid regulatory domain detected:
<6>[ 7.440000] cfg80211: Regulatory domain: 00
<6>[ 7.440000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[ 7.450000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.460000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.470000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.470000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.480000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.490000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[ 7.510000] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 7.520000] cfg80211: World regulatory domain updated:
<6>[ 7.530000] cfg80211: DFS Master region: unset
<6>[ 7.530000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[ 7.540000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.550000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.560000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.560000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.570000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[ 7.580000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[ 7.610000] cfg80211: Calling CRDA for country: US
<6>[ 7.620000] cfg80211: Regulatory domain changed to country: US
<6>[ 7.620000] cfg80211: DFS Master region: FCC
<6>[ 7.630000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[ 7.640000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[ 7.650000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[ 7.650000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[ 7.660000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[ 7.670000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[ 7.970000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
<6>[ 7.970000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 2 is up
<6>[ 8.090000] device ath0 entered promiscuous mode
<6>[ 8.100000] br0: port 2(ath0) entered forwarding state
<6>[ 8.100000] br0: port 2(ath0) entered forwarding state
<6>[ 8.280000] br0: port 2(ath0) entered disabled state
<6>[ 9.350000] br0: port 1(vlan1) entered forwarding state
<6>[ 9.490000] br0: port 2(ath0) entered forwarding state
<6>[ 9.500000] br0: port 2(ath0) entered forwarding state
<6>[ 9.640000] device ath1 entered promiscuous mode
<6>[ 9.640000] br0: port 3(ath1) entered forwarding state
<6>[ 9.650000] br0: port 3(ath1) entered forwarding state
<6>[ 10.250000] device ath0.sta1 entered promiscuous mode
<6>[ 10.250000] br0: port 4(ath0.sta1) entered forwarding state
<6>[ 10.260000] br0: port 4(ath0.sta1) entered forwarding state
<6>[ 10.410000] device br0 left promiscuous mode
<6>[ 11.100000] device vlan2 entered promiscuous mode
<6>[ 11.260000] device ath1.sta1 entered promiscuous mode
<6>[ 11.260000] br0: port 5(ath1.sta1) entered forwarding state
<6>[ 11.270000] br0: port 5(ath1.sta1) entered forwarding state
<6>[ 11.500000] br0: port 2(ath0) entered forwarding state
<6>[ 11.650000] br0: port 3(ath1) entered forwarding state
<6>[ 11.850000] device vlan2 left promiscuous mode
<6>[ 12.260000] br0: port 4(ath0.sta1) entered forwarding state
<6>[ 13.270000] br0: port 5(ath1.sta1) entered forwarding state
<6>[ 16.390000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
<6>[ 27.200000] xt_CT: No such helper c helpddtbt;ignm
<6>[ 27.210000] xt_CT: No such helper c helpddtbt;ignm
<6>[ 659.510000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
<6>[ 659.510000] Hooking IMQ before NAT on PREROUTING.
<6>[ 659.520000] Hooking IMQ after NAT on POSTROUTING.
<6>[ 660.450000] Ebtables v2.0 registered
<6>[ 743.460000] xt_CT: No such helper ed
<6>[ 743.470000] xt_CT: No such helper ed
<6>[ 744.270000] IMQ driver unloaded successfully.
<6>[ 3618.870000] device ath1.sta1 left promiscuous mode
<6>[ 3618.870000] br0: port 5(ath1.sta1) entered disabled state
Router: TP Link TLWDR4900 v1.3
Firmware: v3.0-r27456 (06/27/15) std
Kernel: 3.10.81 #5216 Sat Jun 27 03:11:12 CEST
Status: OK
Reset: No
Errors: None..so far for 2.4Ghz [did not tried 5GHz]
Issues with GUI:
1.) I can't login via GUI interface if I am connected to router via LAN port instead of WiFi.
If I try to open GUI interface router do not respond and even ping to router IP stops immediately.
This happens with http/https both interfaces for GUI.
2.) One of my Dell laptop do not get even IP address from router when connected via LAN port instead of WLAN.
While other laptop gets the IP address from the same router but above issue 1 exists. Both the laptops have Fedora 21 (latest kernel).
The above said Dell laptop gets the IP address via LAN port connection with another router (DIR-615H but slightly old dd-wrt build).
On WLAN things works fine for GUI.
Note: I have kabeldeutscheland modem acting as Bridge only, which is connected to above TP Link TLWDR4900 v1.3 router.
I have to make this kabeldeutscheland modem as bridge because they assign IPv6 to this modem and in that configuration port forwarding was not working.
http://itler.net/hitron-cve-30360-port-freigeben-port-forwarding-nutzen/
Or is this step 1 of the scripts the other users are discussing (with step 2 being the restore) ?
