Same here.Tried the test build; get a signature update failed on my 88u.
Same here.Tried the test build; get a signature update failed on my 88u.
ov 18 21:14:41 kernel: CONSOLE: 095693.856 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.866 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.874 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.881 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.888 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.896 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.904 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.911 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095693.918 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.203 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.211 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.219 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.226 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.236 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.243 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.249 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.261 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.270 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.278 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.284 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.291 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.299 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.306 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.313 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.321 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.329 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.336 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.343 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.350 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.362 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.369 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.380 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:41 kernel: CONSOLE: 095694.386 wl0.0: wlc_send_bar: seq 0xbf tid 0
Nov 18 21:14:42 kernel: CONSOLE: 095695.203 wl0: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 39
Nov 18 21:14:42 kernel: CONSOLE: 095695.252 wl0.0: wlc_send_bar: seq 0xc3 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.812 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.827 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.842 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.857 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.873 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.892 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.909 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.924 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.943 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.958 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.973 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:14:43 kernel: CONSOLE: 095695.993 wl0.0: wlc_send_bar: seq 0xc5 tid 0
Nov 18 21:15:20 kernel: CONSOLE: 095732.534 wl0.0: wlc_send_bar: seq 0x19f tid 0
Nov 18 21:15:20 kernel: CONSOLE: 095733.209 wl0: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 39
Nov 18 21:15:26 kernel: CONSOLE: 095739.069 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 0 initiator 0 reason 39
Nov 18 21:15:26 kernel: CONSOLE: 095739.070 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 1 initiator 0 reason 39
Nov 18 21:15:26 kernel: CONSOLE: 095739.070 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39
Nov 18 21:15:26 kernel: CONSOLE: 095739.071 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 6 initiator 0 reason 39
Nov 18 21:15:27 kernel: CONSOLE: 095739.954 wl0.0: wlc_send_bar: seq 0x1c1 tid 0
Nov 19 14:01:55 kernel: CONSOLE: 155949.125 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 1 initiator 0 reason 39
Nov 19 14:01:59 kernel: CONSOLE: 155952.924 wl0: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xf1c for 1000 ms
Nov 19 14:02:04 kernel: CONSOLE: 155958.452 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39
Nov 19 14:02:07 kernel: CONSOLE: 155961.629 wl0.0: wlc_send_bar: seq 0x30d tid 2
Nov 19 14:02:14 kernel: CONSOLE: 155967.779 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39
Nov 19 14:02:19 kernel: CONSOLE: 155973.642 wl0.0: wlc_send_bar: seq 0x30e tid 2
Tried tlthe test build get a signature update failed on my 88u.
Is there some reason the Traffic Analyzer tabs were reversed in 382.1 from 380.4? I only use the real time traffic analyzer which used to be on the first tab. Now I have to close the demo note popup for the app analyzer every time I go to Traffic Analyzer and then switch to the real time traffic tab.
Hi Running latest merlin 382 (AC88u) I see a lot of logs entry for kernel console. IS this normal?
Just because I merged the menu code from upstream, so it switched the order back to whatever Asus uses. I could re-switch that hem back.
I have just started to use an AC86U and overall I'm impressed with its performance with a VPN client.
I do not have to close the popup demo note but would have to click on the second graph for the info noted. However the first graph is also just as useful and so I see it as being fine as it is.
Could I ask what changes with the test build posted, sorry but I haven't seen a change post.
30e5de4 httpd: use WAN interface instead of hardcoded eth0 when retrieving QoS stats
1e07605 build: make sure that BUILDREV/MERLINUPDATE propagates to child build processes
96fe7fa libogg: updated to 1.3.3
08a1a18 libvorbis: updated to 1.3.5
d1c02a2 Updated documentation
d0d5632 rom: install the correct version of TM sig update script when merlinupdate is enabled
95b1ad9 openssl: updated to 1.0.2m
9ecf631 Updated documentation
09dbd8e rc: add support for postconf/custom config for mcpd
5c5161e modprobe: add aliases so xt_set and ipt_set both get automatically modprobed
fd44d57 kernel: add module alias to modprobe.conf for cifs
57502ae kernel41: make xt_recent built-in instead of module
0a1fdd6 Merge branch 'odhcp6c'
510229e Bumped revision to 382.1_1
fffcb83 build: generate a separate sha256sums-382.txt file for 382 builds
8f9c31a odhcp6c: dhcpv6: allow IA_NA mode downgrade with forced IA_PD
5557a68 odhcp6c: md5: size-optimize the code, performance doesn't really matter
dd4cbd5 odhcp6c: fix IFA_F_* include
d732a54 odhcp6c: sync with upstream
I have to use WAN ClientId DHCP option 61 for my ISP. When trying to set this in the WebUI it says Applying... then the field returns as empty.
Previously on the RT-AC88U, the "Enable Web Access from WAN" feature worked seamlessly for both HTTP (on, say, port 8080) and HTTPS (on port 8443). After updating to 382.1, it appears HTTPS is the only option for this feature now, but I'm unable to establish a connection from off-site using https://<Router-WAN-IP>:8443. Looks like the connection is being refused. Are there any new or additional requirements to make this feature work? Thanks.
Thanks. Haven't changed anything on the remote PC side... was actually connected over the HTTP WAN interface to perform the firmware update (from 380.68.4), which worked like a charm. Immediately after the update (and after I realized HTTPS was the only option now) I could no longer connect. VPN (PPTP) works fine using the same WAN IP (and the built in DDNS host name). Power cycled the AC88U, and tried again with Chrome, Firefox, and IE, and from different remote PCs, but none can connect to the WAN interface. Anything else I can try?WAN access works fine for me, I do all my RT-AC86U tests over that router's WAN interface since it sits within my LAN. Double check the port that you are using, and make sure you aren't behind a double NAT.
Anything else I can try?
Hi Running latest merlin 382 (AC88u) I see a lot of logs entry for kernel console. IS this normal?
Code:ov 18 21:14:41 kernel: CONSOLE: 095693.856 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.866 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.874 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.881 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.888 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.896 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.904 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.911 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095693.918 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.203 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.211 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.219 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.226 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.236 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.243 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.249 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.261 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.270 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.278 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.284 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.291 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.299 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.306 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.313 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.321 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.329 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.336 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.343 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.350 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.362 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.369 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.380 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:41 kernel: CONSOLE: 095694.386 wl0.0: wlc_send_bar: seq 0xbf tid 0 Nov 18 21:14:42 kernel: CONSOLE: 095695.203 wl0: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 39 Nov 18 21:14:42 kernel: CONSOLE: 095695.252 wl0.0: wlc_send_bar: seq 0xc3 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.812 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.827 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.842 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.857 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.873 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.892 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.909 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.924 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.943 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.958 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.973 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:14:43 kernel: CONSOLE: 095695.993 wl0.0: wlc_send_bar: seq 0xc5 tid 0 Nov 18 21:15:20 kernel: CONSOLE: 095732.534 wl0.0: wlc_send_bar: seq 0x19f tid 0 Nov 18 21:15:20 kernel: CONSOLE: 095733.209 wl0: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 39 Nov 18 21:15:26 kernel: CONSOLE: 095739.069 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 0 initiator 0 reason 39 Nov 18 21:15:26 kernel: CONSOLE: 095739.070 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 1 initiator 0 reason 39 Nov 18 21:15:26 kernel: CONSOLE: 095739.070 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39 Nov 18 21:15:26 kernel: CONSOLE: 095739.071 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 6 initiator 0 reason 39 Nov 18 21:15:27 kernel: CONSOLE: 095739.954 wl0.0: wlc_send_bar: seq 0x1c1 tid 0 Nov 19 14:01:55 kernel: CONSOLE: 155949.125 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 1 initiator 0 reason 39 Nov 19 14:01:59 kernel: CONSOLE: 155952.924 wl0: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xf1c for 1000 ms Nov 19 14:02:04 kernel: CONSOLE: 155958.452 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39 Nov 19 14:02:07 kernel: CONSOLE: 155961.629 wl0.0: wlc_send_bar: seq 0x30d tid 2 Nov 19 14:02:14 kernel: CONSOLE: 155967.779 wl0: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 2 initiator 0 reason 39 Nov 19 14:02:19 kernel: CONSOLE: 155973.642 wl0.0: wlc_send_bar: seq 0x30e tid 2
So that appears to be under Administration -> System -> Service, and I can only access it by first turning on the "Enable SSH" option (it was set to "No"). So set it to "LAN + WAN" and make sure "Enable SSH Brute Force Protection" is set to No (appears to default to No)? What about "Allow SSH Port Forwarding" (it's defaulted to No)? Leave it at the default? Thanks for your help.Disable SSH Brute Force Protection.
So that appears to be under Administration -> System -> Service, and I can only access it by first turning on the "Enable SSH" option (it was set to "No"). So set it to "LAN + WAN" and make sure "Enable SSH Brute Force Protection" is set to No (appears to default to No)? What about "Allow SSH Port Forwarding" (it's defaulted to No)? Leave it at the default? Thanks for your help.
UPDATE: Sorry, I wasn't sure where you wanted me to set those other parameters, so I started to do more experimenting. I set "Enable Web Access from WAN" to "No" and clicked Apply. The router interface became inaccessible for a couple minutes, but eventually came back. So I logged back in and toggled "Enable Web Access from WAN" back to "Yes" and clicked Apply. Again, the interface became inaccessible for a couple minutes, but when it came back, HTTPS access over WAN was working! I noticed that the "Authentication Method" under "Local Access Config" had also been changed to "BOTH" (previously -- after the initial firmware upgrade -- it was still set to "HTTP"). So I'm guessing "Local Access Config" needs to change to "BOTH" or "HTTPS" when enabling web access from WAN, and probably if I had done a factory reset as part of the firmware update process all settings would have changed properly during reconfiguration?
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!