Wow, talk about reading comprehension. I give up replying to you and will see if anyone else want to chime in.Because remnants of the old driver/sdk are still resident in NVRAM after new firmware update. Is all there in the thread.... [sigh]
Wow, talk about reading comprehension. I give up replying to you and will see if anyone else want to chime in.Because remnants of the old driver/sdk are still resident in NVRAM after new firmware update. Is all there in the thread.... [sigh]
Wow, talk about reading comprehension. I give up replying to you and will see if anyone else want to chime in.
Try to enable(auto) "NAT acceleration", when NAT acceleration is disabled, it breaks the 2.4 band.I haven't done a wipe yet - so will try that later when my wife isn't here to complain about breaking the internet :/ otherwise I'll roll back I guess.
Thanks - I tried that after reading further through the thread. It turns itself back to disable after reboot (probably because I have traditional QoS on).Try to enable(auto) "NAT acceleration", when NAT acceleration is disabled, it breaks the 2.4 band.
if you read the faq on the ASUS site you'll read thisWow, talk about reading comprehension. I give up replying to you and will see if anyone else want to chime in.
Well to me.... the first before than anything else...To me, the reason to use RMerlin firmware on the supported Asus routers is the additional functionality he provides and more importantly the bug fixes he implements over Asus' own code. The latter being more important than the first for most of my customers.
I'm not investing in a license FOR Merlin... But will Gladly pay for his firmware if I needed to... If he goes another route....The more parts are made closed source by ASUS, the less they can be tampered with. So write a note to ASUS, 'cause the're the ones protecting their firmwares. Unless you would like to invest in getting RMerlin a license...
I've read the thread. RMerlin suggest a wipe "due to the switch to a new SDK + wireless driver". I don't at all think it's a dumb question to ask why RMerlin thinks a wipe is necessary, but Asus apparently doesn't. Maybe you can just let someone else answer at this point rather than tell me I'm not reading the thread again.
Hi,
today have updated my RT-AC68U from Merlin v. 378.56_2 to v. 380.57_0. The first impact I was confronted with: my USB-HDD wasn't mounted anymore. Tried to power-cycle the router and to unplug/plug the USB cable with the same result: USB drive doesn't mount. Then, re-plugged the HDD from USB3 to USB2 socket and, suddenly, it does mount on USB2. Has anyone the same problem?
That's could be the relevant part from the syslog:
Jan 1 14:46:15 disk monitor: be idle
Jan 1 14:46:19 rc_service: udhcpc 561:notify_rc start_firewall
Jan 1 14:46:19 dhcp client: bound 94.125.73.76 via 94.125.73.1 during 259200 seconds.
Jan 1 14:46:21 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 14:46:21 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 3
Jan 1 14:46:21 kernel: usb 2-1: device descriptor read/64, error -71
Jan 1 14:46:21 kernel: usb 2-1: device descriptor read/64, error -71
Jan 1 14:46:22 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 4
Jan 1 14:46:22 kernel: usb 2-1: device descriptor read/64, error -71
Jan 1 14:46:22 kernel: usb 2-1: device descriptor read/64, error -71
Jan 1 14:46:22 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 5
Jan 1 14:46:23 kernel: usb 2-1: device not accepting address 5, error -71
Jan 1 14:46:23 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 6
Jan 1 14:46:23 kernel: usb 2-1: device not accepting address 6, error -71
Jan 1 14:46:23 kernel: hub 2-0:1.0: unable to enumerate USB device on port 1
Jan 1 14:46:24 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 2
Jan 1 14:46:24 kernel: usb 3-1: device descriptor read/64, error -62
Jan 1 14:46:24 kernel: usb 3-1: device descriptor read/64, error -62
Jan 1 14:46:24 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 3
Jan 1 14:46:25 kernel: usb 3-1: device descriptor read/64, error -62
Jan 1 14:46:25 kernel: usb 3-1: device descriptor read/64, error -62
Jan 1 14:46:25 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 4
Jan 1 14:46:25 hour monitor: daemon is starting
Jan 1 14:46:25 kernel: usb 3-1: device not accepting address 4, error -62
Jan 1 14:46:26 kernel: usb 3-1: new full speed USB device using ohci_hcd and address 5
Jan 1 14:46:26 kernel: usb 3-1: device not accepting address 5, error -62
Jan 1 14:46:26 kernel: hub 3-0:1.0: unable to enumerate USB device on port 1
Jan 1 14:46:30 crond[458]: time disparity of 221146 minutes detected
Jan 1 14:50:37 kernel: htb: htb qdisc 14: is non-work-conserving?
Regards
Take a look at the firmware update page hereif you read the faq on the ASUS site you'll read this
""
※Notice: After upgraded the firmware please press the hardware reset button of router over 5~10 seconds to reset the router. ""
Right on this page !!! Scroll down you'll see it for yourself !
http://www.asus.com/support/FAQ/1010600/
......
. I just thought it might help me/others understand things better if I heard why rmerlin thinks the sdk+wireless driver update requires a reset and Asus does not.
It looks like the NAT function is working now, compared to the other previous releases380.57 unlike previous version have bad habit regarding to SIP: it receive UDP answer from the SIP server only if "SIP Passthrough" in the NAT Passthrough is turned ON (default).
I don't need any passthrough since my machine is connected directly to the router and its NAT and I don't use any VPN, so I disable it and it works in all previous firmwares.
SIP clients (hardware and software ones) always have a wide set of their own ways to get external IP: STUN servers, UPnP, etc., then telling it via HTTP-like headers , "rport", ICE, etc. along with internal one, so this is not the case. On directly connected device, at least, SIP can work without any special handling, moreover, when ICE is used, it can work via sequence of locally connected machines (I don't know about VPN thing here) and turning "SIP Passthrough" damages proper SIP response from the device in all such cases.It looks like the NAT function is working now, compared to the other previous releases
You would still need NAT I think since you're SIP device is getting an internal IP from the router. Don't really see what you're trying to say here...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!