What's new

[Release] Asuswrt-Merlin 384.13 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!

Status
Not open for further replies.
DNS Rebind protection is not meant for just IoT...
 
take a closer look at the man's post...

his sig says ax88u,

his loc is cold :cool:

lol yes model in the sig.

And location Canada and its late fall going into winter.

And router sits on a laptop cooling pad :)
 
lol yes model in the sig.

And location Canada and its late fall going into winter.

And router sits on a laptop cooling pad :)
But is the AX88U problematically warm under normal use?
 
But is the AX88U problematically warm under normal use?

No not at all.

You should normally see temps in the 65-75c on the cpu depending on your ambient Temps.

I have the cooling pad from a previous router and just decided to keep using it.
 
You should normally see temps in the 65-75c on the cpu depending on your ambient Temps.

That sounds very warm to me, for 24/7 usage... And how can you see the temp, in the firmware-gui?
 
That sounds very warm to me, for 24/7 usage... And how can you see the temp, in the firmware-gui?

The soc in this router is rated for something close 100c so 65-75c temps are perfectly fine. And yes you can see the temps in the Gui.
 
I'm having this issue on my 86u where after a few days usually around 6 days or so it reboots on its own for no reason OR freezes where no internet access (only LAN access) and GUI wont load.

This was a fresh reset about a month ago with no old loaded settings. I do have the Statistics enabled etc not sure if thats the cause or not though.
 
Just a quick question, to make sure I do not make a bad buy:
The Asus RT-AX88U Nordic Router is a good future proof buy right? Both for Merlin/John fork and in general correct?

Edit:
Or is one of the other Asus routers better?

Get it, it's the best ASUS router available today. I bought mine last year on black Friday for $249 and I'm still very happy buying it. I replaced an AC86U and AC88U which both had many more issues than I ever had with the AX88U routers. This year I added a second one that I bought on an open box sale from Amazon for $229. Now with the latest firmware they added support for WPA3 and I'm sure it will get many more feature updates through the years since it's one of the top routers that ASUS sells.
 
Okay, now what would you get for your parents that is still somewhat future-proof? I just plan to set up Merlin, Skynet, and Diversion and call it good. Their bandwidth and performance requirements are extremely small. Email. Web browsing. Skype calls. Streaming music. Perhaps occasional Netflix. AC86Us are $153 on Amazon right now. AC68Us on sale at NewEgg for under $100, but if @RMerlin is thinking of dropping some of the older models I don't want to get caught with having to replace the 86s-or-68s next year... I can't see spending over $200 on something that often sees under 1GB of traffic per day though.
 
I have an issue since I started using Asuswrt (but might be nothing to do with it and I just had avoided it before).

I have a NAS that connects to the router via an ASUS WiFi bridge (PCE-AC68, so it connects via 1Gb Ethernet then gets something like a 900Mbps WiFi link, much more than using any other route as it's a long way away from everything else as it's a backup, I also have an EA-AC87U which I might like even more). I should add that usually the NAS is asleep and is just woken up for backups (although as it's R/O to everything except a special backup account that's probably not critical, but better safe than sorry).

But after a while you lose the ability to access the NAS by name, although the IP address still works fine (and after using that the name doesn't reappear). I don't think it's the NAS as it used to be fine.

Is there anything I can tweak that might help?

Also right now I've been getting a bunch of these:

Warning 2019/11/30 13:19:28 System 127.0.0.1 Network & Virtual Switch Infrastructure [Network & Virtual Switch] Failed to connect to the internet. System default gateway "Adapter 1" and all adapters failed to connect to the internet after checking NCSI.

Which are strange and might or might not be related (I can still access the NAS by its IP address) and I don't know much about the Network Communications Services Interface on linux? Adapter 1 is the correct adapter and has a static IP address I can access okay. No idea if it's a clue. There's also a number of these in the router log.

Nov 28 10:52:17 kernel: br0: port 1(vlan1) received tcn bpdu
Nov 28 10:52:17 kernel: br0: topology change detected, propagating


Which I don't recall either, so this may all be unrelated to my not being able to access the NAS by name (which is a problem as the NAS that wants to backup to it loses sight of it too, usually between backup jobs without it going to sleep in-between, sometimes before it starts one).

RT-AC87U, Asuswrt 13
Note the NAS has been running for about 36 hours straight and was fine when I first woke it, so probably not sleep related.


P.S. In order to avoiding posting too often is there any exclusion I can add to avoid my security camera filling the log with stuff like:

Oct 12 10:23:14 dnsmasq[228]: possible DNS-rebind attack detected: p2p16.reolink.com


(Where the p2p16 changes with each entry.)
 
P.S. In order to avoiding posting too often is there any exclusion I can add to avoid my security camera filling the log with stuff like:

Oct 12 10:23:14 dnsmasq[228]: possible DNS-rebind attack detected: p2p16.reolink.com


(Where the p2p16 changes with each entry.)
If you have enabled JFFS custom scripts in Administration / System tab of the GUI, you can create a custom config file for dnsmasq on the router using ssh (which must also be enabled to perform these steps).

Create the file /jffs/configs/dnsmasq.conf.add using the nano editor. Paste this line in the file:
Code:
rebind-domain-ok=/reolink.com/
Then run the command:
Code:
service restart_dnsmasq

I’m making assumptions you can use SSH and the nano editor. If not, we can help with that.

Or you can just disable DNS rebind protection on the WAN page to stop the messages, but you throw the baby out with the bath water if you choose that route.
 
Thanks for that, sorry for the late reply but I'm noticeably unwell, hopefully won't last much longer tho as it's getting annoying... (okay, it's day 3 so not bubonic plague, hopefully anyway).

Plus no I don't have custom scripts enabled but I could do that. (BTW do they survive an upgrade or need re-installing? Although with my router not currently supported by 14 I may not be in a rush.) I have no issues with ssh/linux command prompts, although the cut-down ones can cause a bit of hunting around to see what is supported (plus is it busybox or multiple clever things - generally that is, I know what it is on my three Qnap boxes). I might have just typed vi tho and got vim which is supported, and I'm happy using even if it's some new-fangled thing... :)

Actually I'll probably edit it (well, paste it) on a PC with my editor set for unix line endings, dump it in a shared directory then move it and chmod it via Putty or Solar (err, the former until I change the high-DPI settings on the latter, there's always something extra along the way).

Oh and if anyone knows why it disappears from the network I'd really appreciate any input on that, most of the stuff I haven't tried will take a long time to do and have a very low chance of success.
 
I am getting a lot of this messages, what does this mean ?

Nov 30 01:42:01 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 03:44:49 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 04:37:43 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 05:45:04 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 05:53:44 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 07:02:34 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 08:17:39 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 09:01:27 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 10:59:15 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 11:24:21 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 13:30:35 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 15:37:39 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 15:38:54 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 16:09:06 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 16:43:18 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 17:08:25 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 18:55:58 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 19:21:50 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 19:28:40 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 19:54:03 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 21:26:59 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 21:52:16 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 22:42:24 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 23:07:26 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Nov 30 23:09:06 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Nov 30 23:44:59 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Dec 1 01:07:09 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Dec 1 04:36:48 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Dec 1 04:49:59 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Dec 1 06:30:51 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Dec 1 06:52:17 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Dec 1 08:35:35 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
Dec 1 08:48:16 acsd: eth1: NONACSD channel switching to channel spec: 0x1006 (6)
Dec 1 09:13:53 acsd: eth1: NONACSD channel switching to channel spec: 0x1808 (6l)
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

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