What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

  • 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!

Last edited:
  • Like
Reactions: Gar
Hi there guys. I have two ASUS routers, an RTN16 running John's fork and an AC68U running Merlin, both latest builds. I did run some new long cables and the quality of the Cat 5 seems to be low. The cable continuity checker shows OK but don't know how good that is as a transmission quality gauge. How do I check for data transmission errors/retries at the switch portion? Would like to look at individual ports. Is there a command or commands I can use? (Most of the cables end up at the RTN16 with John's fork, that's why I ask here).
Thanks!
 
Thanks for confirming....sounds like Comcast had a hiccup...
Hopefully it's now working for @luni now as well.

Just as an FYI....on Cox my address starts with 2600

@john9527 @jrmwvu04 @dave14305

I must just have the worst timing. I had to reboot my router but upon reboot it picked up ipv6 and my network devices are now passing ipv6 tests again. Thanks everyone.

For posterity:
  1. I still had "Prefix delegation requires address request" set to yes from previous experiments, but as previously mentioned, that's likely not required. Leaving it, since it's working ¯\_(ツ)_/¯
  2. Prefix of 64 since I don't have complex subnetting needs, but supposedly you can get a /60 from comcast if you want.
  3. IPv6 System Log is showing a WAN 2001: and a LAN 2601: which matches comcast's ipv6 setup
Thanks everyone for your time and John for all the work you do.
 
Any idea what this is keep getting it now on latest firmware, never seen it before: Jul 18 22:01:30 dnsmasq[607]: possible DNS-rebind attack detected: crb.kargo.com ?
 
Any idea what this is keep getting it now on latest firmware, never seen it before: Jul 18 22:01:30 dnsmasq[607]: possible DNS-rebind attack detected: crb.kargo.com ?
Did you not have DNS Rebind Protection enabled before (WAN - Internet Connection)?

The message is valid. You are trying to go to that domain and it is has an address of 0.0.0.0.
 
Hi there guys. I have two ASUS routers, an RTN16 running John's fork and an AC68U running Merlin, both latest builds. I did run some new long cables and the quality of the Cat 5 seems to be low. The cable continuity checker shows OK but don't know how good that is as a transmission quality gauge. How do I check for data transmission errors/retries at the switch portion? Would like to look at individual ports. Is there a command or commands I can use? (Most of the cables end up at the RTN16 with John's fork, that's why I ask here).
Thanks!
Is the RT-N16U in router mode or AP mode? If you're in AP mode the interface to look at is br0. If you're in router mode you need to look the interface shown by nvram get wan0_ifname.

Code:
# ifconfig br0
br0       Link encap:Ethernet  HWaddr 30:5A:3A:C7:8A:20
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5908839 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16983105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:888364441 (847.2 MiB)  TX bytes:21723650483 (20.2 GiB)
Look at the "errors" and "dropped" numbers.
 
Has anyone else had problems (or success) downloading RT-N66U_374.43_44EAj9527.zip? I'm repeatedly getting it failing at about 17.53 MB.
 
Thanks a LOT Colin.

The RTN16 is in Router mode. Or gateway, I have a wan port that goes into a fiber optic bridge and I connect to the ISP using PPOE. There are four Cat 5 cables and each goes to a downstream AP that creates its own WiFi network. DHCP remains at the RTN16 as it should.

I am looking for the error rate for the cables that come out of the four RTN16 ethernet ports, not the wan port. Isn't wan0 the wan port? That would tell me about the quality of the fiber connection, I would think.
Run the commands, here's the output. Also checked BR0.

Code:
ASUSWRT-Merlin RT-N16_3.0.0.4 Wed May 27 13:28:03 UTC 2020
Opekun@RT-N16-F56E:/tmp/home/root# nvram get wan0_ifname
eth0
Opekun@RT-N16-F56E:/tmp/home/root# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:85093211 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84956179 errors:59878 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41508570 (39.5 MiB)  TX bytes:3508690720 (3.2 GiB)
          Interrupt:4 Base address:0x2000

Opekun@RT-N16-F56E:/tmp/home/root# ifconfig br0
br0       Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          inet addr:192.168.17.1  Bcast:192.168.17.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1513625 errors:0 dropped:0 overruns:0 frame:0
          TX packets:655424 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:177799033 (169.5 MiB)  TX bytes:122794847 (117.1 MiB)

So the error rate is 0.07 %. I have no idea of what is "normal" in any case it's quite low IMHO.
Thanks!!!

Is the RT-N16U in router mode or AP mode? If you're in AP mode the interface to look at is br0. If you're in router mode you need to look the interface shown by nvram get wan0_ifname.

Code:
# ifconfig br0
br0       Link encap:Ethernet  HWaddr 30:5A:3A:C7:8A:20
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5908839 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16983105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:888364441 (847.2 MiB)  TX bytes:21723650483 (20.2 GiB)
Look at the "errors" and "dropped" numbers.
 
So the error rate is 0.07 %. I have no idea of what is "normal" in any case it's quite low IMHO.
Yes that would be the error rate to the ONT. I'm not that familiar with PPPoE setups but I'd guess that you could also do ifconfig ppp0 to get the stats for that link. (Or do ifconfig -a and look at all the interfaces. ;))

But for your actual question about errors on the LAN connections; thinking about this a bit more I suspect that because br0 isn't a physical interface (it's a bridge) that it will never report any errors. At least I've never seen any. To find the actual interface name look at the output of brctl show. I suspect it will be called vlan1. So you could then look for errors with ifconfig vlan1. But again, it's a virtual interface not a physical one so I doubt it will report anything useful.

So I think the only way to detect errors would be to send traffic down the links and look for lost packets. There aren't really any good tools to do this built into the firmware. Does the RT-N16U have Entware installed? That would allow you to install some more useful tools.
 
Thanks again, Mr Taylor!
Yes, for sure I have entware installed so I can install some testing tools if needed.
So as per your advice, I did run brctl show and ifconfig -a (output below). Only eth0 shows errors. Now, since the switch has its own brains, I am probably missing a lot of the action since on switch control I have NAT acceleration set to YES which would hide some information. Will change and try again all commands.
One thing I noticed (and this is another can of worms I am opening) is that only one interface showing 1480 as the MTU size is ppp0 which worries me about fragmentation. I don't know if that is relevant or if the code adjust the MTU somehow to optimal values.
Best regards from Patagonia....
Code:
Opekun@RT-N16-F56E:/tmp/home/root# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.bcaec5c4f56e       yes             vlan1
                                                        eth1
Opekun@RT-N16-F56E:/tmp/home/root# ifconfig -a
br0       Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          inet addr:192.168.17.1  Bcast:192.168.17.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1810479 errors:0 dropped:0 overruns:0 frame:0
          TX packets:796865 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:214421560 (204.4 MiB)  TX bytes:159211414 (151.8 MiB)

eth0      Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:98418575 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98294978 errors:60732 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2128880689 (1.9 GiB)  TX bytes:1238959623 (1.1 GiB)
          Interrupt:4 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1116351 errors:0 dropped:0 overruns:0 frame:25480306
          TX packets:1478280 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:254617002 (242.8 MiB)  TX bytes:618284488 (589.6 MiB)
          Interrupt:3 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:1106587 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1106587 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:253690106 (241.9 MiB)  TX bytes:253690106 (241.9 MiB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:10.81.38.208  P-t-P:10.81.36.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING MULTICAST  MTU:1480  Metric:1
          RX packets:68995752 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30198494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:2479782702 (2.3 GiB)  TX bytes:3397336627 (3.1 GiB)

vlan1     Link encap:Ethernet  HWaddr BC:AE:C5:C4:F5:6E
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1252600 errors:0 dropped:0 overruns:0 frame:0
          TX packets:896030 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:125199011 (119.3 MiB)  TX bytes:167142649 (159.3 MiB)

Opekun@RT-N16-F56E:/tmp/home/root#

Yes that would be the error rate to the ONT. I'm not that familiar with PPPoE setups but I'd guess that you could also do ifconfig ppp0 to get the stats for that link. (Or do ifconfig -a and look at all the interfaces. ;))

But for your actual question about errors on the LAN connections; thinking about this a bit more I suspect that because br0 isn't a physical interface (it's a bridge) that it will never report any errors. At least I've never seen any. To find the actual interface name look at the output of brctl show. I suspect it will be called vlan1. So you could then look for errors with ifconfig vlan1. But again, it's a virtual interface not a physical one so I doubt it will report anything useful.

So I think the only way to detect errors would be to send traffic down the links and look for lost packets. There aren't really any good tools to do this built into the firmware. Does the RT-N16U have Entware installed? That would allow you to install some more useful tools.
 
Yes, for sure I have entware installed so I can install some testing tools if needed.
So as per your advice, I did run brctl show and ifconfig -a (output below). Only eth0 shows errors. Now, since the switch has its own brains, I am probably missing a lot of the action since on switch control I have NAT acceleration set to YES which would hide some information. Will change and try again all commands.
One thing I noticed (and this is another can of worms I am opening) is that only one interface showing 1480 as the MTU size is ppp0 which worries me about fragmentation. I don't know if that is relevant or if the code adjust the MTU somehow to optimal values.
I don't think there's anything to worry about on the WAN side. The ppp0 interface is being tunnelled through eth0 so it needs to have a smaller MTU to allow for the tunnel's packet overhead. Clients use PMTUD to discover the maximum packet size to use to avoid fragmentation.

For Entware you could install a better version of ping and then flood ping the IP addresses of each of your APs. Leave it running for a while and then Ctrl-C to break out of it and see how many lost packets you have lost.
Code:
# opkg install iputils-ping
Code:
# ping -f 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
.^
--- 192.168.1.10 ping statistics ---
168034 packets transmitted, 168034 received, 0% packet loss, time 18934ms
rtt min/avg/max/mdev = 0.046/0.072/6.747/0.046 ms, ipg/ewma 0.112/0.077 ms
Remember to wiggle the cables around at each end to make sure there aren't any intermittent connections. ;)
 
(long-time Merlin and Merlin-LTS user, first time poster :) )

The current issue is with the latest LTS release (374.43_44EAj9527) on an RT-AC66U (original MIPS device, not the B1).

The problem is that regardless of the setting of LAN / DHCP Server / Enable multicast DNS (Avahi mDNS), the mDNS service does not start.

I know the MIPS routers use mDNSResponder rather than Avahi, and I see the mDNS* binaries under /usr/sbin.

But the service never runs (ps w | grep -i mdns shows no processes).

I also see syslog entries like these:

616:Jul 24 12:36:04 (none) user.notice rc_service: service 612:notify_rc start_mdns
617:Jul 24 12:36:04 (none) user.notice rc_service: INFO: rc notified of unrecognized or custom event 'mdns'


Am I missing something, or is this a bug?

Thanks,
R.
 
Am I missing something, or is this a bug?
Well, the current bug is that I should not show that option on the MIPs routers.

On the MIPs routers, there is no separate mDNS service for mDNSresponder. It's tied to the Media Server and only starts/stops with the Media Server (always been that way).
Do you think you have a need to run it independently?
 
Yes.. I don't need the media server, but I'd like to have an mDNS reflector (to copy mDNS multicast frames across network segments).
 

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