Posted: Wed Nov 09, 2022 8:56 Post subject: New Build - 11/09/2022 - r50841
Welcome to Broadcom r50841 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Try station or repeater mode but YMMV.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
r7000 continue to have the same ntp_server problem. This time I reset to factory and entered all settings again. I did the ntp_server first and it worked! Then after adding my many settings at some point it stopped working. I will have to try disabling things when I have time to see if I can find the problem. The default ntp_server settings would be a problem except the ips used do not work at all... so if for some reason the 2.pool.ntp.org fails to resolve which sometimes it does then also the ips fail and at some point it won't get a time for ntp, then dnscrypt won't work and nothing works.
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Wed Nov 09, 2022 11:13 Post subject:
Are you sure nvram is not maxxed out you have "only" 64 KB
As you are using DNScrypt you will have a catch 22 situation DNS crypt is waiting for NTP and NTP is waiting for DNS.
I use SmartDNS with DoT (no exactly the same but also secure DNS) and also had a problem that it takes very long for the correct time, you can solve this by adding in the Additional DNSMasq options:
If 2.pool.ntp.org does not work when the internet connection is working then there is a DNS problem.
It is widely known that if you use DNSSEC and the system time is not correct no DNS requests can be resolved.
Therefore the IP addresses 212.18.3.19 and 88.99.174.22 are still stored as fallback.
If these addresses do not work either, there is certainly not only a DNS problem.
By the way, you are the only one here with any NTP/DNS problems.
So I doubt it is a bug and it is probably due to your lack of understanding how NTP/DNS etc work.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Wed Nov 09, 2022 11:52 Post subject:
portsup wrote:
r7000 continue to have the same ntp_server problem. This time I reset to factory and entered all settings again. I did the ntp_server first and it worked! Then after adding my many settings at some point it stopped working. I will have to try disabling things when I have time to see if I can find the problem.
First try entering IP address of your favorite NTP server, instead of its domain name. A domain needs DNS server to resolve it into IP address.
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Wed Nov 09, 2022 11:55 Post subject: DD-WRT BS build 50841 and Asus RT-N18U
Router/Version:Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r50841 std (11/09/22)
Kernel: Linux 4.4.302-st25 #8209 Wed Nov 9 00:23:01 -00 2022 armv7l
Previous: DD-WRT v3.0-r50814 std (11/05/22)
Mode: WAN @ DHCP, Wireless @ AP (Mixed)
Status: Working {
Not 24/7; Using CTF+FA with port-forwarding;
Not using SFE, STP, IPv6, VPN, VAP;
USB storage(/jffs, /opt); NAS (ksmbd, lighttpd);
WAN DNS disabled; DDNS (no-ip.com) OK;
DNSmasq not serving DNS; Recursive DNS Unbound (/jffs/etc/unbound.conf);
Entware core (CPU: armv71) installed without problem
}
Reset: No RESET during firmware upgrade
File:https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/11-09-2022-r50841/asus-rt-n18u/
Summary
Lousy, lazy testing this time. Nothing too strange to complain about.
Code:
~# grep -i -E 'err' /var/log/messages
Jan 1 08:00:12 rt-n18u kern.err kernel: [ 0.000124] smp_twd: clock not found -2
Jan 1 08:00:12 rt-n18u kern.err kernel: [ 2.080805] bcmsflash: found no supported devices
Jan 1 08:00:12 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 9
Jan 1 08:00:12 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 9
Jan 1 08:00:12 rt-n18u daemon.info mstpd[637]: error, CTL_set_msti_bridge_config: Couldn't find bridge with index 9
Jan 1 08:00:13 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 9
Jan 1 08:00:13 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 9
Jan 1 08:00:24 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Nov 10 10:57:13 rt-n18u kern.err kernel: [ 38.568448] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Nov 10 10:57:15 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: WARNING: child process exited abnormally: 1216
Nov 10 10:57:15 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: can't execute kill 1216: No such process
Nov 10 10:57:20 rt-n18u user.info : [lighttpd] : Error on startup, returncode 255
Nov 10 10:57:22 rt-n18u user.info : [lighttpd] : Error on startup, returncode 255
Nov 10 10:57:22 rt-n18u user.info : [unbound] : Error on startup, returncode 9
Nov 10 10:57:24 rt-n18u user.info : [unbound] : Error on startup, returncode 9
Code:
~# grep -E '1216|smb' /var/log/messages
Jan 1 08:00:24 rt-n18u user.info : [ksmbd.mountd] : successfully started
Jan 1 08:00:24 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Jan 1 08:00:24 rt-n18u local5.info ksmbd: [ksmbd-worker/1216]: INFO: User already exists nobody
Nov 10 10:57:15 rt-n18u local5.info ksmbd: [ksmbd-worker/1216]: INFO: Child received signal: 15 (Terminated)
Nov 10 10:57:15 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: WARNING: child process exited abnormally: 1216
Nov 10 10:57:15 rt-n18u local5.err ksmbd: [ksmbd-manager/1215]: ERROR: can't execute kill 1216: No such process
Nov 10 10:57:15 rt-n18u local5.info ksmbd: [ksmbd-manager/1215]: INFO: Exiting. Bye!
Nov 10 10:57:15 rt-n18u user.info : [ksmbd.mountd] : samba daemon successfully stopped
Nov 10 10:57:15 rt-n18u kern.info kernel: [ 40.638254] ksmbd: kill command received
Nov 10 10:57:19 rt-n18u user.info : [ksmbd.mountd] : successfully started
Nov 10 10:57:19 rt-n18u local5.info ksmbd: [ksmbd-worker/2338]: INFO: User already exists nobody
Nov 10 10:57:19 rt-n18u user.info : [ksmbd.mountd] : config reloaded
Nov 10 10:57:22 rt-n18u user.info : [ksmbd.mountd] : config reloaded
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
r7000 continue to have the same ntp_server problem. This time I reset to factory and entered all settings again. I did the ntp_server first and it worked! Then after adding my many settings at some point it stopped working. I will have to try disabling things when I have time to see if I can find the problem. The default ntp_server settings would be a problem except the ips used do not work at all... so if for some reason the 2.pool.ntp.org fails to resolve which sometimes it does then also the ips fail and at some point it won't get a time for ntp, then dnscrypt won't work and nothing works.
It's been an issue for years, one thing that works is to specify the IP address. For example:
use the command line and do a nslookup for the time server you wish to use.
nslookup time.windows.com
time.windows.com = 40.119.6.228
Then just use the IP address. For whatever reason it doesn't resolve properly.
There are a lot of services that will not work without the correct time like DnsMasq.
Are you sure nvram is not maxxed out you have "only" 64 KB
As you are using DNScrypt you will have a catch 22 situation DNS crypt is waiting for NTP and NTP is waiting for DNS.
I use SmartDNS with DoT (no exactly the same but also secure DNS) and also had a problem that it takes very long for the correct time, you can solve this by adding in the Additional DNSMasq options:
If 2.pool.ntp.org does not work when the internet connection is working then there is a DNS problem.
It is widely known that if you use DNSSEC and the system time is not correct no DNS requests can be resolved.
Therefore the IP addresses 212.18.3.19 and 88.99.174.22 are still stored as fallback.
If these addresses do not work either, there is certainly not only a DNS problem.
By the way, you are the only one here with any NTP/DNS problems.
So I doubt it is a bug and it is probably due to your lack of understanding how NTP/DNS etc work.
The problem is my router can't make a connection to 212.18.3.19 and 88.99.174.22 for some reason and the DNS resolve for 2.pool.ntp.org fails sometimes. I think my isp is doing something funky to my DNS connections.
When you add say server=/2.pool.ntp.org/9.9.9.9 to DNSmasq it also disables DNSSEC from it
They do work most of the time, but sometimes the resolve for 2.pool.ntp.org fails and I also can't connect to the default ips. Maybe your extra dns server for pool.ntp.org will solve it, but I do want to find out why I the nvram setting ntp_server is being ignored.
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Wed Nov 09, 2022 13:36 Post subject:
Yes for the time server you use plain DNS, you have to otherwise you are in a catch 22 situation.
Alternatively you can specify an IP address, but that can be down for maintenance and if you specify a domain name you will always get a working and also fastest time server.
I know you can specify multiple IP addresses (which you should do) but if one is down it takes time before it will try the other and maybe that is down too
