I used this way to add the printer manually using the standard Windows driver.
Hope you can make ver 384.18 for RT-AC87U as well soon so that we can get same features as other models.
You can just install this patch from Microsoft to fix the issue.
https://support.microsoft.com/en-us/help/4567523/windows-10-update-kb4567523
Similar to this post:Since I have upgraded to 384.18, I am facing below issue of "This account already exists, Please enter a different name" whenever I try to make any change to Administration>System tab. Though, I have not put my cursor on login section:
View attachment 24534
I guess he hopes for ASUS to come around and issue a FW in line with the newer Code...That's impossible, the 384.18 code is no longer compatible with the closed source components Asus provides for this model.
Make sure you check which unit (0 or 1) got called.
There are multiple WAN events during boot.
This is my wan-event script, apparently at boot time it executes on both WANs (0 and 1) without looking if Wan0 is down or not. I dont get any issues and the scripts execute as expected and on proper events after the first boot.
Code:#!/bin/sh # Determine FL-UP if [ "$1" = "0" ] && [ "$2" = "connected" ]; then /jffs/scripts/personal/Fiberlink/FL-Connected fi # Determine FL-Down if [ "$1" = "0" ] && [ "$2" = "disconnected" ]; then /jffs/scripts/personal/Fiberlink/FL-Disconnected fi # Determine Jazz-UP if [ "$1" = "1" ] && [ "$2" = "connected" ]; then /jffs/scripts/personal/Jazz/Jazz-Connected fi # Determine Jazz-Down if [ "$1" = "1" ] && [ "$2" = "disconnected" ]; then /jffs/scripts/personal/Jazz/Jazz-Disconnected fi
It's much easier to use wan-event this way:@RMerlin Were you able to reproduce this issue?
It's much easier to use wan-event this way:
https://www.snbforums.com/threads/wan-start-script-also-run-on-wan-stop.61295/
I guess he hopes for ASUS to come around and issue a FW in line with the newer Code...
@RMerlin Were you able to reproduce this issue?
From what info I have, this won't be happening, hence my decision to stop waiting and to pull the plug now.
The script is doing what it's meant to do: it gets executed whenever there is a WAN-related event done by the router. So, multiple calls are normal. You will need your script to be intelligent about it, and to pay attention to which specific event and for which unit it got called.
Just as a heads-up for people using access restriction on the system page, it does not work when you select 'HTTPS' only as the authentication method. HTTP remains active, and the access restriction code assumes it is disabled. Therefore HTTP remains accessible for everyone on the network.
Selecting BOTH properly filters HTTP.
When I have it set to HTTPS only.
I cannot access http.
Yeah, they're too busy developing stuff no one wants like open natFrom what info I have, this won't be happening, hence my decision to stop waiting and to pull the plug now.
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!