What's new

[Beta] Asuswrt-Merlin 380.60 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

is that kind of internet disconnected errors just with 380_60 version? what is situation with 380_59 firmware?
Code:
WAN Connection: ISP's DHCP did not function properly.
stop_nat_rules: apply the redirect_rules!
WAN Connection: WAN was restored.
start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
 
is that kind of internet disconnected errors just with 380_60 version? what is situation with 380_59 firmware?
Code:
WAN Connection: ISP's DHCP did not function properly.
stop_nat_rules: apply the redirect_rules!
WAN Connection: WAN was restored.
start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
I don't know if this error is firmware bug specific, the only time I saw it is when I change the power supply of my ONT which means it's an actual ISP outage and nothing have to do with the router. I think it's just a little chatty in describing WAN outages.
 
Not sure if this is the best place to report bugs, but here we go. I'm using a RT-AC68R and with this beta build as well as the latest stable, if you have any single quotes in your device names, it breaks the javascript on the page since they are not escaped.

The variables dhcp_staticlist_array and dhcp_staticlists break the js at declaration. I wouldn't mind NOT having quotes in the device nicknames, but I'm now unable to change them and any page with that list has a bunch of broken JS.

Let me know if there is any other data/stuff you need from me on this. I'm a developer and actually am interested in contributing as well.

** Update ** I simply copied the JS from the script tab, fixed it, executed in the console and ran initial() again. This let me update the device nickname that was causing the issue.
 
Last edited:
When you look into GUI did you see this?"Network cable unplugged" message, and required a reboot to restore external connectivity, is this your issue?
I cant upgrade to beta because of this, i got this message every 2-3 days and not only after service interruption from my provider.Router need reboot
So i decided to stick with .58 until Asus fix this

yup! but it isn't 'random' it only happens after my ISP modem goes down.
 
Asus broke something in the wanduck service, and that code is a complete maze, impossible for me to debug. We'll have to wait and hope that their next release will resolve that issue (3831 does contain a number of changes to wanduck). It doesn't happen to everyone, and it doesn't happen for me, so I can't do anything about it.

roger!
 
Not sure if this has been reported.. On 5ghz everytime I unselect Band1 Channels and hit apply it just rechecks it and sticks me on band1 channels. Don't like reduced transmission power so don't want those channels.
 
Trying to use curl on the AC3200 (380.60 b2) and getting a missing certificates error:
Code:
curl: (77) error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
I could have sworn I read somewhere (but can't find it now) that Merlin includes the needed certificates for curl to work with https.. (but "cd /, find -name ca-certificates.crt" returns nothing, and /etc/ssl doesn't exist on the filesystem.)

Regression caused by a bad merge - fixed.
 
Asus RT AC5300 380.60 Beta 2 "set AP isolated" does not work for 2.4 GHz and 5 GHz-1 bands although it does work on the 5 GHz-2 band and if you turn access to Intranet OFF on ALL guest network it works.
 
I installed 380.60 Beta 2 on my RT-AC68U and for sure signal from 5GHz is stronger. I have range in place where I couldn't find 5GHz signal. Also speed of network increased in my opinion.
 
Beta 1 and Beta 2 are both causing me some problems on my AC87. "Random" router reboots every 3-12 hours.

The visual symptom is that all the lights on the router come on, where they are normally in Stealth Mode. Internet connectivity to all LAN devices is down at during this time. The router recovers automatically, establishes internet connectivity and establishes the VPN connection all automatically - just like any other power cycle.

There have been no changes to my usage patterns or hardware (no new devices, not suddenly doing heavier-than-normal streaming, etc)
I've shut off QoS, app analysis, never used any of the AiProtection or AiCloud features, IPv6 is off, basically everything is off or default.
I do have it set as an OpenVPN TAP client with an automatic/persistent connection, but that's been enabled for months.

Here's a snip of the log from the few minutes before it rebooted to when it did the reboot (always easy to find the events in the log since the log time goes bad until NTP kicks in). I can't paste the enter reboot sequence since it is more than 10k characters, but let me know if there is something specific I should search for and I'll add that.


Code:
Jul 22 05:15:23 openvpn[3814]: Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Jul 22 05:25:34 openvpn[3814]: Extracted DHCP router address: 10.0.3.1
Jul 22 05:39:37 openvpn[3814]: Extracted DHCP router address: 10.0.3.1
Jul 22 05:53:39 openvpn[3814]: Extracted DHCP router address: 10.0.3.1
Jul 31 17:00:12 kernel: klogd started: BusyBox v1.20.2 (2016-06-22 15:12:53 EDT)
Jul 31 17:00:12 kernel: Linux version 2.6.36.4brcmarm (merlin@mint-dev) (gcc version 4.5.3 (Buildroot 2012.02) ) #2 SMP PREEMPT Wed Jun 22 15:20:50 EDT 2016
Jul 31 17:00:12 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Jul 31 17:00:12 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jul 31 17:00:12 kernel: Machine: Northstar Prototype
Jul 31 17:00:12 kernel: Ignoring unrecognised tag 0x00000000
Jul 31 17:00:12 kernel: Memory policy: ECC disabled, Data cache writealloc
Jul 31 17:00:12 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60416
Jul 31 17:00:12 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Jul 31 17:00:12 kernel: Memory: 255480k/255480k available, 6664k reserved, 0K highmem
Jul 31 17:00:12 kernel: Virtual kernel memory layout:
Jul 31 17:00:12 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Jul 31 17:00:12 kernel:     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Jul 31 17:00:12 kernel:     DMA     : 0xf7e00000 - 0xffe00000   ( 128 MB)
Jul 31 17:00:12 kernel:     vmalloc : 0xd0800000 - 0xf0000000   ( 504 MB)
Jul 31 17:00:12 kernel:     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
Jul 31 17:00:12 kernel:     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Jul 31 17:00:12 kernel:       .init : 0xc0008000 - 0xc003d000   ( 212 kB)
Jul 31 17:00:12 kernel:       .text : 0xc003d000 - 0xc03aa000   (3508 kB)
Jul 31 17:00:12 kernel:       .data : 0xc03c2000 - 0xc03e52a0   ( 141 kB)
Jul 31 17:00:12 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
Jul 31 17:00:12 kernel: Mount-cache hash table entries: 512
Jul 31 17:00:12 kernel: CPU1: Booted secondary processor
Jul 31 17:00:13 kernel: Found a AMD NAND flash:
Jul 31 17:00:13 kernel: Total size:  128MB
Jul 31 17:00:13 kernel: Block size:  128KB
Jul 31 17:00:13 kernel: Page Size:   2048B
Jul 31 17:00:13 kernel: OOB Size:    64B
Jul 31 17:00:13 kernel: Sector size: 512B
Jul 31 17:00:13 kernel: Spare size:  16B
Jul 31 17:00:13 kernel: ECC level:   8 (8-bit)
Jul 31 17:00:13 kernel: Device ID: 0x 1 0xf1 0x80 0x1d 0x 1 0xf1
Jul 31 17:00:13 kernel: bio: create slab <bio-0> at 0
Jul 31 17:00:13 kernel: PCI: no core
Jul 31 17:00:13 kernel: PCI: no core
Jul 31 17:00:13 kernel: PCI: Fixing up bus 0
Jul 31 17:00:13 kernel: PCI: Fixing up bus 0
Jul 31 17:00:13 kernel: PCI: Fixing up bus 1
Jul 31 17:00:13 kernel: VFS: Disk quotas dquot_6.5.2
Jul 31 17:00:13 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jul 31 17:00:13 kernel: pflash: found no supported devices
Jul 31 17:00:13 kernel: bcmsflash: found no supported devices
Jul 31 17:00:13 kernel: Boot partition size = 524288(0x80000)
Jul 31 17:00:13 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jul 31 17:00:13 kernel: nflash: squash filesystem with lzma found at block 28
Jul 31 17:00:13 kernel: Creating 4 MTD partitions on "nflash":
Jul 31 17:00:13 kernel: 0x000000000000-0x000000080000 : "boot"
Jul 31 17:00:13 kernel: 0x000000080000-0x000000200000 : "nvram"
Jul 31 17:00:13 kernel: 0x000000200000-0x000004000000 : "linux"
Jul 31 17:00:13 kernel: 0x00000039d57c-0x000004000000 : "rootfs"
Jul 31 17:00:13 kernel: Registering the dns_resolver key type
Jul 31 17:00:13 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jul 31 17:00:13 kernel:  2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jul 31 17:00:13 kernel: Available 7 bytes at (off,len):
Jul 31 17:00:13 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
Jul 31 17:00:13 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
Jul 31 17:00:13 kernel: Creating 2 MTD partitions on "brcmnand":
Jul 31 17:00:13 kernel: 0x000004000000-0x000007ec0000 : "brcmnand"
Jul 31 17:00:13 kernel: 0x000007ec0000-0x000008000000 : "asus"
Jul 31 17:00:13 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jul 31 17:00:13 kernel: ctf: module license 'Proprietary' taints kernel.
Jul 31 17:00:13 kernel: Disabling lock debugging due to kernel taint
Jul 31 17:00:13 kernel: et_module_init: passivemode set to 0x0
Jul 31 17:00:13 kernel: et_module_init: txworkq set to 0x1
Jul 31 17:00:14 kernel: et_module_init: et_txq_thresh set to 0x400
Jul 31 17:00:14 kernel: =================
Jul 31 17:00:14 kernel: robo chk regs:
Jul 31 17:00:14 kernel: ===================
Jul 31 17:00:14 kernel: (0x00,0x5d)Port 5 States Override: 0xfb
Jul 31 17:00:14 kernel: (0x00,0x5f)Port 7 States Override: 0xfb
Jul 31 17:00:14 kernel: (0x00,0x0e)Port 8 States Override: 0x0a
Jul 31 17:00:14 kernel: (0x00,0x08)Port 8 IMP Control Register: 0x00
Jul 31 17:00:14 kernel: (0x02,0x00) Global Management Config: 0x00
Jul 31 17:00:14 kernel: (0x02,0x00) 802.1Q VLAN Control 5: 0x00
Jul 31 17:00:14 kernel: (0x02,0x03) BRCM HDR Control Register: 0x00
Jul 31 17:00:14 kernel: (0x00,0x0b) Switch Mode Register: 0x06
Jul 31 17:00:14 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.126 (r561982)
Jul 31 17:00:14 kernel: wl_module_init: passivemode set to 0x0
Jul 31 17:00:14 kernel: wl_module_init: igs set to 0x0
Jul 31 17:00:14 kernel: wl_module_init: txworkq set to 0x1
Jul 31 17:00:14 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jul 31 17:00:14 kernel: _ Reboot message ... _______________________________________________________
Jul 31 17:00:14 kernel: <4>Emergency Sync complete
Jul 31 17:00:14 kernel: <6>mod epilog takes 0��U�fies
Jul 31 17:00:14 kernel: <6>IDPfw: Exit IDPfw
Jul 31 17:00:14 kernel: <4>Stop the IPS/AppID engine...
Jul 31 17:00:14 kernel: <6>IDPfw: Exit chrdev /dev/idpfw with major 191
Jul 31 17:00:14 kernel: <7>[udb_exit:959] Free udb at cdd26000
Jul 31 17:00:14 kernel: <7>[udb_exit:960] Free app at d2e96000
Jul 31 17:00:14 kernel: <7>[udb_exit:961] Free patrol table at d2eb9000
Jul 31 17:00:14 kernel: <4>
Jul 31 17:00:14 kernel: <4>gro disabled
Jul 31 17:00:14 kernel: <4>Attempt to kill tasklet from interrupt
Jul 31 17:00:14 kernel: <6>device eth0 left promiscuous mode
Jul 31 17:00:14 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 17:00:14 kernel: <6>device eth0 entered promiscuous mode
Jul 31 17:00:14 kernel: <6>br0: topology change detected, propagating
Jul 31 17:00:14 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 3(tap15) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: topology change detected, propagating
Jul 31 17:00:14 kernel: <6>br0: port 3(tap15) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 3(tap15) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 3(tap15) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 3(tap15) entering disabled state
Jul 31 17:00:14 kernel: <6>br0: port 2(eth1) entering forwarding state
Jul 31 17:00:14 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 17:00:14 kernel: <6>device eth0 left promiscuous mode
Jul 31 17:00:14 kernel: <6>device vlan1 left promiscuous mode
Jul 31 17:00:14 kernel: <6>br0: port 1(vlan1) entering disabled state
Jul 31 17:00:14 kernel: <6>device eth1 left promiscuous mode
Jul 31 17:00:14 kernel: <6>br0: port 2(eth1) entering disabled state
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver cdc_mbim
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver cdc_ncm
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver qmi_wwan
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver cdc_wdm
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver rndis_host
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver cdc_ether
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver asix
Jul 31 17:00:14 qcsapi: write qcsapi conf ok
Jul 31 17:00:14 WAN Connection: ISP's DHCP did not function properly.
Jul 31 17:00:14 kernel: <6>usbcore: deregistering interface driver usblp
(the FIREWALL-START: line is from a custom script that just adds firewall filters to block DHCP requests from the two OpenVPN sites from being served by the wrong router. That scripts been working fine for months too)
 
Noticed a kernel panic during reboot of my AC88U, may not occur every time, but likely when uptime is longer than one day

Code:
Aug  1 08:00:16 kernel: _ Reboot message ... _______________________________________________________
Aug  1 08:00:16 kernel: <1>Unable to handle kernel NULL pointer derefere��U�at virtual address 00000000
Aug  1 08:00:16 kernel: <1>pgd = 9fb90000
Aug  1 08:00:16 kernel: <1>[00000000] *pgd=5fadf031, *pte=00000000, *ppte=sfs file: /sys/class/net/eth0/speed
Aug  1 08:00:16 kernel: <4>module:  nf_nat_sip    7f65a000    5031
Aug  1 08:00:16 kernel: <4>module:  nf_conntr
Aug  1 08:00:16 kernel: <4>module:  nf_conntrack_h323    62a000    1144
Aug  1 08:00:16 kernel: <4>module:  nf_conntrack_ftp    7f623000    4909
Aug  1 08:00:16 kernel: <4>module:  ip6table_mangle    7f61d000    7000    769
Aug  1 08:00:16 kernel: <4>module:  ohci_hcd    <4>module:  tfat    7f4c8000    191383
Aug  1 08:00:16 kernel: <4>module:  ext2    7f4b3000    53816
Aug  1 08:00:16 kernel: <4>module:  ext4    7f472000    00    49581
Aug  1 08:00:16 kernel: <4>module:  crc16    7f458000    1007
Aug  1 08:00:16 kernel: <4>module:  ext3    7f7f424000    42863
Aug  1 08:00:16 kernel: <4>module:  mbcache    7f41d000    4599
Aug  1 08:00:16 kernel: <4>module:  module:  sg    7f403000    20031
Aug  1 08:00:16 kernel: <4>module:  sd_mod    7f3f7000    22199module:  nf_conntrack_pptp    7f36oto_gre    7f361000    887
Aug  1 08:00:16 kernel: <4>module000    3296
Aug  1 08:00:16 kernel: <4>module:  dpsta    7f006c000    21433
Aug  1 08:00:16 kernel: <4>module:  lacp     7f040000    19511
Aug  1 08:00:16 kernel: <4>module:  rtl8365mb    7f000000    192290
Aug  1 08:00:16 kernel: <4>Moduntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntractp ip6table_mangle xt_length ohci_hcd ehci_hcd thfsplus tntfs(P)_mod scsi_wait_scan scsi_mod usbcore ip6t_LOG ip6table_filter jfnf_conntrack_proto_gre dpsta(P) dhd]
Aug  1 08:00:16 kernel: <4>CPU: 1    Tainted: P    >PC is at strcmp+0x4/0x38
Aug  1 08:00:16 kernel: <4>LR 2e000  r8 : 9f82fd44
Aug  1 08:00:16 kernel: <4>r7 : 8044  r0 : 00000000
Aug  1 08:00:16 kernel: <4>Flags: NzCv  ISA ARM  Segment user
Aug  1 08:00:16 kernel: <4>Control: 10c53c7d  Table: 5fb9004a  DA 00000000 80061658 00000011 9f820: 2c643634 34327830 00006535 8800200 00000001 00000000 88111fc0>fde0: 00000001 88111fc0 9f82fe08 800b6bcc 00000000 800b7d1c 9fbbdb98 00000008
Aug  1 08:00:17 kernel: <0>fe00: 9fbbdc14010 800bd8d4 9f82fec0 00000000 900 9f82fe98 00000000 ffffffff 9fc54
Aug  1 08:00:17 kernel: <0>fea0: 9faea070 00000000 80486504 ffffffff 00000000 9f82ff82ff28 00000000 00000000 00000000000 00000001 8010e9a4
Aug  1 08:00:17 kernel: <0>ff00: 2a8 00000000 00000001 9950ca08 00000001
Aug  1 08:00:17 kernel: <0>ff20: 9fae3f08 00000001 000a1184 00000000 00000000 00000000 8041eef8 9fae3f08
Aug  1 08:00:17 kernel: <0>ff4080: 00000000 00000000 9f816040 00000000 2ac46c30 00000011 7ef7d254 00000004
Aug  1 08:00:17 kernel: <0>ffa0: 80050c68 80050ac0 2ac46c30 00000011 0000000ffc0: 2ac46c30 00000011 7ef7d2547ef7d240 2ac3e7ac 2afb32ec 00000 ^C964>] (_nvram_set+0x8c/0x114) from [<80061658>] (nvram_set+0x24/0x94)
Aug  1 08:00:17 kernel: <4>[<80061658>] (nvram_set+0x24/0x94) from [<80061744>] (dev_nvram_write+0x7c/0x104)
Aug  1 08:00:17 kernel: <4>[< (vfs_write+0xb4/0x148) from [<800df7b8>] (sys_write+0x40/0x70)
Aug  1 08:00:17 kernel: <4>[<800df7b8>] (sys_write+0x40/0x70) from [<80050ac0>] (ret_fast_syscall+0x0/0x30)
Aug  1 08:00:17 kernel: <0>Code: e5c (e7d02003)
Aug  1 08:00:17 kernel: <4>---[ end trace 35f87a4a77a4b55f ]---
Aug  1 08:00:17 kernel: <0>Kernel panic - not syncing: Fatal exception
Aug  1 08:00:17 kernel: <4>[<8005701c>] (unwind_back] (panic+0x7c/0x1a8)
Aug  1 08:00:17 kernel: <800546f0>] (die+0x1a4/0x1dc) fr4
Aug  1 08:00:17 kernel: <4>fd00: a0000093 ffffffff
Aug  1 08:00:17 kernel: <4>[<803d116c>] (__dabt_svc+0x4c/0xtrace+0x0/0xf8) from [<80050334>] (do_IPI+0x114/0x154)
Aug  1 08:00:17 kernel: ____________________________________________________________________________
The message would be inserted into boot meesage during the boot, so the timestamp is incorrect
not much services running on the router, I just enabled 6 to 4 tunnel, LACP and AiProtection on it.
 
RT-AC68U, on the General Log page, should the Clear button remove the log entries permanently? It appears to only clear them visibly until the router is rebooted, well, a power on/off anyway. Is this the intended behavior?

It removes the files from /tmp/ however it might take a few minutes before it overwrites the jffs copy with the new logfile, so if you reboot immediately, it might not have a chance to overwrite the permanent copy.

This is working properly for me.
 
It used to be the case, but no longer, because the two fields have different limitations. A valid hostname for instance cannot contain a space, but a device description can. So, there was no way to conciliate the two, short of separating them.



The original page from Asus was one where you could control the speed of the fan (back during development when the RT-N66U had a fan) or control power output. With the RT-AC68U, it also controlled the Turbo button, which was also dropped during development. With those settings dropped, there was only the temperature monitoring left, with a now irrelevant page title.

I could probably rename the page, I'm just worried about the potential problems it might generate down the line, so I never really gave it much thought. I even considered removing that page completely for a while, as the forums kept getting flooded with worried posts about router temperatures, with people assuming it was too hot without being aware of the engineering specifications of the chips involved.



I haven't changed any of the help fields, neither added any, due to potential clashes with Asus's dictionary files (merging modified versions of them would be really difficult, and simplifying the process of merging new GPL is increasingly important with all the changes Asus did these past few years). Might be something that was broken in a recent Asus release, I'll have to test it.



There's "vi". Not very novice-friendly, but I never added nano because of its extensive requirements (it requires termcap/ncurse with everything associated to it). For now the best is to plug a USB flash drive, and setup Entware. You can then install nano (or your preferred alternative) from Entware.



The possibility to customize most of the router service's configurations or insert custom scripts at various points is what I consider Asuswrt-Merlin's biggest original feature, which sets it apart from most other third party firmwares. The rest are just tweaks or minor features that can be found in most third party firmwares.
The original page from Asus was one where you could control the speed of the fan (back during development when the RT-N66U had a fan) or control power output. With the RT-AC68U, it also controlled the Turbo button, which was also dropped during development. With those settings dropped, there was only the temperature monitoring left, with a now irrelevant page title.

I could probably rename the page, I'm just worried about the potential problems it might generate down the line, so I never really gave it much thought. I even considered removing that page completely for a while, as the forums kept getting flooded with worried posts about router temperatures, with people assuming it was too hot without being aware of the engineering specifications of the chips involved.
So, what is the performance tuning button for and what is it supposed to do? Whenever I click on it the router logs me out and message telling me to log back in. What's up with this??
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top