Author
Message
Alozaros DD-WRT Guru Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Thu Apr 20, 2023 22:27 Post subject:
blkt wrote: Once you have static leases configured in webUI (not additional options) nvram show or nvram get static_leases.
With small list added, you can quickly understand this nvram formatting so then you can nvram set static_leases.
However, this is only necessary if you want to avoid webUI later on. It is not hard at all to manage a list this way.
nvram show | grep static
static_leasenum
static_leases
and than
manually start stop DNSmasq to read the leases
stopservice dnsmasq && sleep 2 && startservice dnsmasq
I used to add static IP this way via cli...and as blkt noted, you must at least have 1,2 static IP set in GUI, so the command line commands will show output..otherwise if you just save those in advanced dnsmasq rules, those commands form above will not show much output...
In general static leases are saved in nvram and executed/present in /tmp (ram) dnsmasq.conf
i think you can even add them directly via CLI like that
dhcp-host=xx:xx:xx:xx:xx:xx,power-PC,192.168.1.101,infinite
but those will not survive reboot... _________________Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913 Last edited by Alozaros on Thu Apr 20, 2023 22:36; edited 1 time in total
Back to top
Sponsor
blkt DD-WRT Guru Joined: 20 Jan 2019 Posts: 5700
Back to top
ArjenR49 DD-WRT Guru Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Thu Apr 20, 2023 22:50 Post subject:
blkt wrote: Once you have static leases configured in webUI (not additional options) nvram show or nvram get static_leases.
With small list added, you can quickly understand this nvram formatting so then you can nvram set static_leases.
However, this is only necessary if you want to avoid webUI later on. It is not hard at all to manage a list this way.
nvram show | grep static
static_leasenum
static_leases
I think I see what you mean.
I'll try with some contrived static leases.
Perhaps it is a way to avoid 'random' IP's being sometimes given out during startup, which don't adhere to the dhcp address space I've allotted in my settings. Perhaps precisely because dnsmasq is failing to start until /jffs is ready.
Sometimes I see IP's like 192.168.1.182 etc., which are well outside of what I specify for DHCP and not at all what is listed as reserved IP. Some clients try to hold on to those. For others two IP's are shown for some time. In due time they go away, unless the client is stubborn.
Now that my reserved IP's are on a /jffs file, I have annotations in the file that I find essential to my LAN 'housekeeping'. I have info there about the machine type & amount of memory etc.
Apparently in your system, 'static leases' are edited using command nvram set <static_lease>. That would be one IP at a time ... copying one line at a time from a file that I keep somewhere. When I extract a list of 'static leases' from nvram, they'll be in some random order ... I would find that confusing.
Currently I just open the file on the jffs partition in an editor on my laptop and reboot the router when I'm done. Easy. It's probably read into ram with comment lines and all, so it takes up extra memory. I haven't noticed a problem with that, though.
Back to top
blkt DD-WRT Guru Joined: 20 Jan 2019 Posts: 5700
Posted: Thu Apr 20, 2023 23:00 Post subject:
IP are assigned based on MAC address. If you know which IP that dnsmasq will lease you can assign client static.
Otherwise please set static leases outside DHCP range to avoid conflicts with these not very random assignments.
Also, please read two redhawk posts I linked above. His explanations were very clear so I felt no need to repeat.
nvram set static_leases="" this is all in one line from left to right, listed top to bottom in webUI, it is very simple.
"Keeping a space between each of your leases (after the =1440 in your list)....and a space after the last =1440 "
nvram set static_leasenum=x number of static leases for DD-WRT and webUI to keep proper track of total count.
--dhcp-sequential-ip
"Dnsmasq is designed to choose IP addresses for DHCP clients using a hash of the client's MAC address. This
normally allows a client's address to remain stable long-term, even if the client sometimes allows its DHCP
lease to expire. In this default mode IP addresses are distributed pseudo-randomly over the entire available
address range. There are sometimes circumstances (typically server deployment) where it is more convenient
to have IP addresses allocated sequentially, starting from the lowest available address, and setting this flag
enables this mode. Note that in the sequential mode, clients which allow a lease to expire are much more
likely to move IP address; for this reason it should not be generally used."
I do not recommend sequential IP either, but description serves an explanation as to how dnsmasq DHCP works .
If both DHCP IP address range and client MACs do not change then dnsmasq does all the work for you it's static.
Back to top
egc DD-WRT Guru Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Fri Apr 21, 2023 8:24 Post subject:
ArjenR49 wrote: blkt wrote: Once you have static leases configured in webUI (not additional options) nvram show or nvram get static_leases.
With small list added, you can quickly understand this nvram formatting so then you can nvram set static_leases.
However, this is only necessary if you want to avoid webUI later on. It is not hard at all to manage a list this way.
nvram show | grep static
static_leasenum
static_leases
I think I see what you mean.
I'll try with some contrived static leases.
Perhaps it is a way to avoid 'random' IP's being sometimes given out during startup, which don't adhere to the dhcp address space I've allotted in my settings. Perhaps precisely because dnsmasq is failing to start until /jffs is ready.
Sometimes I see IP's like 192.168.1.182 etc., which are well outside of what I specify for DHCP and not at all what is listed as reserved IP. Some clients try to hold on to those. For others two IP's are shown for some time. In due time they go away, unless the client is stubborn.
Now that my reserved IP's are on a /jffs file, I have annotations in the file that I find essential to my LAN 'housekeeping'. I have info there about the machine type & amount of memory etc.
Apparently in your system, 'static leases' are edited using command nvram set <static_lease>. That would be one IP at a time ... copying one line at a time from a file that I keep somewhere. When I extract a list of 'static leases' from nvram, they'll be in some random order ... I would find that confusing.
Currently I just open the file on the jffs partition in an editor on my laptop and reboot the router when I'm done. Easy. It's probably read into ram with comment lines and all, so it takes up extra memory. I haven't noticed a problem with that, though.
You can have the best of both worlds (as stated already earlier by multiple posters) by simply adding the static leases to the Additional DNSMasq Options as text, so you can simply edit it and copy paste etc.
Quote: dhcp-host=xx:xx:xx:xx:xx:xx,power-PC,192.168.1.11,1440m
dhcp-host=xx:xx:xx:xx:xx:xx,NAS,192.168.1.12,1440m
_________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read): https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Back to top
mrjcd DD-WRT Guru Joined: 31 Jan 2015 Posts: 6290 Location: Texas
Posted: Fri Apr 21, 2023 14:37 Post subject:
new build thread --- aside from all this mess that was discussed years back
Netgear WNDR3700 V4 ...main backup router
DD-WRT v3.0-r52330 std (04/14/23)
Linux 3.18.140-d6 #169486 Fri Apr 14 16:51:41 +06 2023 mips
GUI install over r51935
all looky good and yeahuh it is live and config same as main EA8500 same cloned MAC & all but the OVPN server.
I gots its WAN plugged into my 2nd EA8500 VLAN port so its got a 192.168.1.x WAN IP ...still on it now...
Code: mrjcd@daDeb:~$ ssh root@3700v4-homeworld.mrjcd.com
DD-WRT v3.0-r52330 std (c) 2023 NewMedia-NET GmbH
Release: 04/14/23
Board: Netgear WNDR3700 V4
==========================================================
___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/
DD-WRT v3.0
https://www.dd-wrt.com
==========================================================
BusyBox v1.36.0 (2023-04-14 16:52:04 +06) built-in shell (ash)
root@3700v4-Homeworld:~# ifconfig
br0 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9E
inet addr:10.72.28.13 Bcast:10.72.28.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1033 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:112701 (110.0 KiB) TX bytes:705644 (689.1 KiB)
br1 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9E
inet addr:10.15.26.225 Bcast:10.15.26.255 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:2432 (2.3 KiB)
eth0 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1639 errors:0 dropped:0 overruns:0 frame:0
TX packets:1648 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:302541 (295.4 KiB) TX bytes:771282 (753.2 KiB)
Interrupt:4
imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:220 errors:0 dropped:0 overruns:0 frame:0
TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:30
RX bytes:131754 (128.6 KiB) TX bytes:131754 (128.6 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:832 (832.0 B) TX bytes:832 (832.0 B)
vlan1 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:973 errors:0 dropped:0 overruns:0 frame:0
TX packets:1033 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:113760 (111.0 KiB) TX bytes:705644 (689.1 KiB)
vlan2 Link encap:Ethernet HWaddr 00:13:10:xx:xx:xx
inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:666 errors:0 dropped:0 overruns:0 frame:0
TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:159279 (155.5 KiB) TX bytes:41886 (40.9 KiB)
vlan4 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:17160 (16.7 KiB)
wlan0 Link encap:Ethernet HWaddr 44:94:FC:76:A6:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:14023 (13.6 KiB)
wlan0.1 Link encap:Ethernet HWaddr 46:94:FC:76:A6:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:21276 (20.7 KiB)
wlan1 Link encap:Ethernet HWaddr 44:94:FC:76:A6:A0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:14223 (13.8 KiB)
wlan1.1 Link encap:Ethernet HWaddr 46:94:FC:76:A6:A0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:348 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:23788 (23.2 KiB)
root@3700v4-Homeworld:~# dmesg | tail -40
<6>[ 63.490000] device vlan4 entered promiscuous mode
<6>[ 63.500000] br1: port 3(vlan4) entered listening state
<6>[ 63.510000] br1: port 3(vlan4) entered listening state
<4>[ 65.170000] EXT4-fs (sda1): Ignoring removed nobh option
<6>[ 65.190000] EXT4-fs (sda1): barriers disabled
<6>[ 65.200000] EXT4-fs (sda1): recovery complete
<6>[ 65.200000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: init_itable=0,nobarrier,nobh,barrier=0
<6>[ 67.400000] br1: topology change detected, propagating
<6>[ 67.400000] br1: port 1(wlan1.1) entered forwarding state
<6>[ 69.100000] Linux kernel CIFS/SMB SERVER 3.4.6 by Namjae Jeon <linkinjeon@kernel.org>
<6>[ 69.840000] br1: topology change detected, propagating
<6>[ 69.840000] br1: port 2(wlan0.1) entered forwarding state
<4>[ 70.360000] IMQ: autocreate imq0 NS 8039c588
<4>[ 70.370000] IMQ: autocreate imq1 NS 8039c588
<6>[ 70.370000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
<6>[ 70.380000] Hooking IMQ before NAT on PREROUTING.
<6>[ 70.380000] Hooking IMQ after NAT on POSTROUTING.
<3>[ 71.630000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 71.690000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 71.750000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 71.820000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 71.880000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 72.000000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<4>[ 73.670000] IMQ: remove dev imq0
<4>[ 73.680000] IMQ: remove dev imq1
<6>[ 73.690000] IMQ driver unloaded successfully.
<4>[ 77.890000] IMQ: autocreate imq0 NS 8039c588
<4>[ 77.900000] IMQ: autocreate imq1 NS 8039c588
<6>[ 77.900000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
<6>[ 77.910000] Hooking IMQ before NAT on PREROUTING.
<6>[ 77.920000] Hooking IMQ after NAT on POSTROUTING.
<6>[ 78.560000] br1: port 3(vlan4) entered learning state
<3>[ 78.920000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 78.980000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 79.050000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 79.110000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 79.170000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<3>[ 79.300000] x_tables: ip_tables: ndpi.0 match: invalid size 264 (kernel) != (user) 256
<6>[ 93.600000] br1: topology change detected, propagating
<6>[ 93.600000] br1: port 3(vlan4) entered forwarding state
root@3700v4-Homeworld:~# uptime && date
09:29:33 up 14 min, load average: 0.00, 0.05, 0.10
Fri Apr 21 09:29:33 CDT 2023
root@3700v4-Homeworld:~#
Connection to 3700v4-homeworld.mrjcd.com closed.
mrjcd@daDeb:~$ inxi
CPU: quad core Intel Core i5-3570 (-MCP-) speed/min/max: 2170/1600/3800 MHz
Kernel: 6.1.0-7-amd64 x86_64 Up: 1d 20h 53m Mem: 10207.2/15945.4 MiB (64.0%)
Storage: 596.17 GiB (76.6% used) Procs: 238 Shell: Bash inxi: 3.3.25
mrjcd@daDeb:~$
I prolly got try put this on other WNDR3700v4 WAP seems ok build
Back to top
mrjcd DD-WRT Guru Joined: 31 Jan 2015 Posts: 6290 Location: Texas
Posted: Fri Apr 21, 2023 14:47 Post subject:
Netgear WNDR3700 V4 ...main backup router
DD-WRT v3.0-r52369 std (04/20/23)
Linux 3.18.140-d6 #169644 Thu Apr 20 05:20:14 +06 2023 mips
he's all veddy good
Back to top
blkt DD-WRT Guru Joined: 20 Jan 2019 Posts: 5700
Posted: Fri Apr 21, 2023 15:00 Post subject:
egc wrote: You can have the best of both worlds (as stated already earlier by multiple posters) by simply adding
the static leases to the Additional DNSMasq Options as text, so you can simply edit it and copy paste etc.
Quote: dhcp-host=xx:xx:xx:xx:xx:xx,power-PC,192.168.1.11,1440m
dhcp-host=xx:xx:xx:xx:xx:xx,NAS,192.168.1.12,1440m
Comparison between Additional Options (above) and native DD-WRT webUI format (below):
Code: MAC1=HOSTNAME1=192.168.1.xxx=1440
MAC2=HOSTNAME2=192.168.1.xxx=1440
Once a vertical list has been all sorted it becomes much easier to translate into a single line.
Code: nvram set static_leasenum=2
nvram set static_leases="MAC1=HOSTNAME1=192.168.1.xxx=1440 MAC2=HOSTNAME2=192.168.1.xxx=1440 "
Native DD-WRT webUI format, simplified: MAC=HOSTNAME=IP=MINUTES (SINGLE SPACE).
Back to top
mrjcd DD-WRT Guru Joined: 31 Jan 2015 Posts: 6290 Location: Texas
Posted: Fri Apr 21, 2023 15:40 Post subject:
just now installed r52369 over r51935 on the WNDR3700V4 WAP
has isolated guest net & OVPN server
tis all good
Code: mrjcd@390-Deb:~$ ssh root@citadel-switch.mrjcd.com
DD-WRT v3.0-r52369 std (c) 2023 NewMedia-NET GmbH
Release: 04/20/23
Board: Netgear WNDR3700 V4
==========================================================
___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/
DD-WRT v3.0
https://www.dd-wrt.com
==========================================================
BusyBox v1.36.0 (2023-04-20 05:20:36 +06) built-in shell (ash)
root@Citadel-Switch:~# ps
PID USER VSZ STAT COMMAND
1 root 1244 S /sbin/init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW< [kworker/0:0H]
6 root 0 SW [kworker/u2:0]
7 root 0 SW< [khelper]
8 root 0 SW< [netns]
71 root 0 SW< [writeback]
73 root 0 SW< [crypto]
75 root 0 SW< [bioset]
77 root 0 SW< [kblockd]
79 root 0 SW [kswapd0]
80 root 0 SW [kworker/0:1]
112 root 0 SW [fsnotify_mark]
126 root 0 SW< [deferwq]
127 root 0 SW [kworker/u2:2]
471 root 1004 S /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
577 root 0 SW< [cfg80211]
627 root 1780 S watchdog
818 root 4044 S hostapd -B -P /var/run/wlan0_hostapd.pid /tmp/wlan0_hostap.conf
970 root 1468 S syslogd -Z -L
972 root 1468 S klogd
1018 root 1396 S dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_ed25519_key -p 22 -s
1025 root 3344 S /tmp/openvpnserver --config /tmp/openvpn/openvpn.conf --daemon
1280 root 1896 S wland
1551 root 1308 S dnsmasq -u root -g root -C /tmp/dnsmasq.conf
1591 root 4536 S httpd -n -p 80
1594 root 976 S cron
1597 root 1548 S resetbutton
1619 root 1456 S process_monitor
2277 root 1416 R dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_ed25519_key -p 22 -s
2278 root 1472 S -sh
2280 root 1476 R ps
root@Citadel-Switch:~# dmesg | tail -50
<6>[ 16.970000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
<5>[ 16.980000] Bridge firewalling registered
<6>[ 16.990000] 8021q: 802.1Q VLAN Support v1.8
<6>[ 16.990000] searching for nvram
<6>[ 17.000000] nvram size = 524288
<6>[ 17.040000] Atheros AR71xx hardware watchdog driver version 0.1.0
<6>[ 17.040000] ar71xx-wdt: timeout=15 secs (max=107) ref freq=40000000
<6>[ 17.080000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
<6>[ 17.090000] Freeing unused kernel memory: 184K
<6>[ 24.540000] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
<6>[ 25.280000] libphy: ag71xx_mdio: probed
<6>[ 25.870000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
<6>[ 25.880000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
<6>[ 29.090000] eth0: link up (1000Mbps/Full duplex)
<0>[ 29.440000] 2 vs 0
<4>[ 29.440000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
<7>[ 30.610000] ar71xx-wdt: enabling watchdog timer
<6>[ 31.310000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
<6>[ 31.310000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 2 is up
<6>[ 31.320000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 3 is up
<6>[ 31.330000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
<6>[ 31.330000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 5 is up
<6>[ 32.690000] using kernel STP
<6>[ 32.910000] device br0 entered promiscuous mode
<6>[ 33.020000] device vlan1 entered promiscuous mode
<6>[ 33.020000] device eth0 entered promiscuous mode
<6>[ 33.030000] br0: port 1(vlan1) entered forwarding state
<6>[ 33.030000] br0: port 1(vlan1) entered forwarding state
<6>[ 33.110000] device vlan2 entered promiscuous mode
<6>[ 33.120000] br0: port 2(vlan2) entered forwarding state
<6>[ 33.120000] br0: port 2(vlan2) entered forwarding state
<6>[ 33.150000] device br0 left promiscuous mode
<6>[ 33.160000] device br0 entered promiscuous mode
<6>[ 33.180000] device br0 left promiscuous mode
<6>[ 35.610000] device wlan0 entered promiscuous mode
<6>[ 37.910000] br0: port 3(wlan0) entered forwarding state
<6>[ 37.920000] br0: port 3(wlan0) entered forwarding state
<6>[ 38.390000] device wlan0.1 entered promiscuous mode
<6>[ 38.390000] br1: port 1(wlan0.1) entered listening state
<6>[ 38.400000] br1: port 1(wlan0.1) entered listening state
<5>[ 39.620000] random: nonblocking pool is initialized
<6>[ 43.380000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 43.380000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>[ 47.400000] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 48.080000] br0: port 1(vlan1) entered forwarding state
<6>[ 48.160000] br0: port 2(vlan2) entered forwarding state
<6>[ 52.960000] br0: port 3(wlan0) entered forwarding state
<6>[ 53.440000] br1: port 1(wlan0.1) entered learning state
<6>[ 68.480000] br1: topology change detected, propagating
<6>[ 68.480000] br1: port 1(wlan0.1) entered forwarding state
root@Citadel-Switch:~# uptime && date
10:48:16 up 15 min, load average: 0.07, 0.09, 0.15
Fri Apr 21 10:48:16 CDT 2023
root@Citadel-Switch:~#
Connection to citadel-switch.mrjcd.com closed.
mrjcd@390-Deb:~$
Back to top
mrjcd DD-WRT Guru Joined: 31 Jan 2015 Posts: 6290 Location: Texas
Posted: Fri Apr 21, 2023 17:00 Post subject:
Daghter's EA8500 ...main gateway
scp 'firmware.bin' install over r51935
all good here ...NO goofy stuff in dmesg -- they also have NO samba share setup
Code: mrjcd@Will-Be-Was:~$ ssh root@10.19.96.30
DD-WRT v3.0-r52369 std (c) 2023 NewMedia-NET GmbH
Release: 04/20/23
Board: Linksys EA8500
==========================================================
___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/
DD-WRT v3.0
https://www.dd-wrt.com
==========================================================
BusyBox v1.36.0 (2023-04-20 00:27:09 +07) built-in shell (ash)
root@Julee-Rayne:~# ps
PID USER VSZ STAT COMMAND
1 root 1088 S /sbin/init
2 root 0 SW [kthreadd]
4 root 0 SW< [kworker/0:0H]
5 root 0 SW [kworker/u4:0]
6 root 0 SW [ksoftirqd/0]
7 root 0 SW [rcu_sched]
8 root 0 SW [rcu_bh]
9 root 0 SW [migration/0]
10 root 0 SW< [lru-add-drain]
11 root 0 SW [cpuhp/0]
12 root 0 SW [cpuhp/1]
13 root 0 SW [migration/1]
14 root 0 SW [ksoftirqd/1]
16 root 0 SW< [kworker/1:0H]
17 root 0 SW [oom_reaper]
18 root 0 SW< [writeback]
19 root 0 SW [kcompactd0]
20 root 0 SW< [crypto]
21 root 0 SW< [bioset]
22 root 0 SW< [kblockd]
23 root 0 SW< [kworker/u5:0]
24 root 0 SW< [watchdogd]
26 root 0 SW [kworker/0:1]
43 root 0 SW [kswapd0]
44 root 0 SW< [vmstat]
71 root 0 SW< [cryptodev_queue]
72 root 0 SW [kworker/1:1]
73 root 0 SW [kworker/u4:1]
75 root 0 SW< [bioset]
76 root 0 SW< [bioset]
77 root 0 SW< [bioset]
78 root 0 SW< [bioset]
79 root 0 SW< [bioset]
80 root 0 SW< [bioset]
81 root 0 SW< [bioset]
82 root 0 SW< [bioset]
83 root 0 SW< [bioset]
84 root 0 SW< [bioset]
85 root 0 SW< [bioset]
86 root 0 SW< [bioset]
87 root 0 SW< [bioset]
88 root 0 SW< [bioset]
89 root 0 SW< [bioset]
90 root 0 SW< [bioset]
91 root 0 SW< [bioset]
92 root 0 SW< [bioset]
93 root 0 SW< [bioset]
98 root 0 SW< [kworker/0:1H]
99 root 0 SW< [kworker/1:1H]
784 root 828 S /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
788 root 812 S /sbin/mstpd
839 root 0 SW< [cfg80211]
840 root 0 SW [kworker/1:2]
852 root 0 SW< [ath10k_wq]
853 root 0 SW< [ath10k_aux_wq]
854 root 0 SW< [ath10k_tx_compl]
855 root 0 SW< [kworker/u5:1]
858 root 0 SW< [ath10k_wq]
859 root 0 SW< [ath10k_aux_wq]
860 root 0 SW< [ath10k_tx_compl]
864 root 0 SW< [kworker/u5:2]
883 root 1656 S watchdog
1070 root 0 SW [kworker/0:2]
1140 root 4736 S hostapd -B -P /var/run/wlan1_hostapd.pid /tmp/wlan1_hostap.conf
1179 root 4732 S hostapd -B -P /var/run/wlan0_hostapd.pid /tmp/wlan0_hostap.conf
1320 root 1436 S syslogd -Z -L
1322 root 1436 S klogd
1339 root 1280 S dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_ed25519_key -p 22 -s
1730 root 4880 S httpd -n -p 80
1732 root 1404 S resetbutton
1797 root 0 SW< [kworker/u5:3]
2035 root 1780 S wland
2042 root 1960 S dnsmasq -u root -g root -C /tmp/dnsmasq.conf
2461 root 1436 S udhcpc -i eth0 -p /var/run/udhcpc.pid -s /tmp/dhcpc -O routes -O msstaticroutes
2482 root 748 S cron
2493 root 1308 S process_monitor
3252 root 0 SW [kworker/u4:2]
3264 root 1300 R dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_ed25519_key -p 22 -s
3265 root 1440 S -sh
3267 root 0 RW< [kworker/u5:4]
3268 root 1444 R ps
root@Julee-Rayne:~# iw wlan0 station dump
Station 44:d8:78:13:e6:59 (on wlan0)
inactive time: 9140 ms
rx bytes: 83313
rx packets: 533
tx bytes: 94133
tx packets: 438
tx retries: 0
tx failed: 0
rx drop misc: 219
signal: -67 [-70, -81, -70, -83] dBm
signal avg: -66 [-71, -74, -71, -78] dBm
tx bitrate: 1.0 MBit/s
tx duration: 190739 us
rx bitrate: 1.0 MBit/s
rx duration: 0 us
airtime weight: 256
expected throughput: 130.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 456 seconds
associated at [boottime]: 42.812s
associated at: 1682095576593 ms
current time: 1682096032246 ms
Radio Name: Station 90:a8:22:f5:15:24 (on wlan0)
inactive time: 10540 ms
rx bytes: 68061
rx packets: 336
tx bytes: 114057
tx packets: 308
tx retries: 0
tx failed: 0
rx drop misc: 18
signal: -66 [-75, -68, -73, -74] dBm
signal avg: -65 [-73, -68, -70, -73] dBm
tx bitrate: 1.0 MBit/s
tx duration: 197800 us
rx bitrate: 72.2 MBit/s MCS 7 short GI
rx duration: 0 us
airtime weight: 256
expected throughput: 72.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 448 seconds
associated at [boottime]: 50.459s
associated at: 1682095584241 ms
current time: 1682096032248 ms
Radio Name: Station b8:86:87:d6:4a:69 (on wlan0)
inactive time: 0 ms
rx bytes: 204999
rx packets: 1136
tx bytes: 672749
tx packets: 1068
tx retries: 0
tx failed: 0
rx drop misc: 5
signal: -59 [-61, -76, -67, -66] dBm
signal avg: -59 [-61, -76, -68, -66] dBm
tx bitrate: 1.0 MBit/s
tx duration: 1057066 us
rx bitrate: 72.2 MBit/s MCS 7 short GI
rx duration: 0 us
airtime weight: 256
expected throughput: 72.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 440 seconds
associated at [boottime]: 58.524s
associated at: 1682095592305 ms
current time: 1682096032249 ms
Radio Name: Station 90:de:80:2d:e5:83 (on wlan0)
inactive time: 6980 ms
rx bytes: 22158
rx packets: 186
tx bytes: 33443
tx packets: 139
tx retries: 0
tx failed: 1
rx drop misc: 3
signal: -64 [-80, -69, -80, -75] dBm
signal avg: -65 [-77, -68, -81, -74] dBm
tx bitrate: 1.0 MBit/s
tx duration: 59426 us
rx bitrate: 150.0 MBit/s MCS 7 40MHz short GI
rx duration: 0 us
airtime weight: 256
expected throughput: 150.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 439 seconds
associated at [boottime]: 59.543s
associated at: 1682095593324 ms
current time: 1682096032251 ms
Radio Name: Station 00:bf:af:48:43:b7 (on wlan0)
inactive time: 5140 ms
rx bytes: 70747
rx packets: 358
tx bytes: 230127
tx packets: 364
tx retries: 0
tx failed: 0
rx drop misc: 86
signal: -58 [-65, -64, -64, -61] dBm
signal avg: -59 [-67, -66, -66, -63] dBm
tx bitrate: 1.0 MBit/s
tx duration: 361018 us
rx bitrate: 1.0 MBit/s
rx duration: 0 us
airtime weight: 256
expected throughput: 65.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 438 seconds
associated at [boottime]: 60.817s
associated at: 1682095594598 ms
current time: 1682096032253 ms
Radio Name: Station 70:2a:d5:61:53:69 (on wlan0)
inactive time: 1340 ms
rx bytes: 2974760
rx packets: 24640
tx bytes: 256500461
tx packets: 168465
tx retries: 0
tx failed: 0
rx drop misc: 1448
signal: -60 [-64, -66, -69, -68] dBm
signal avg: -60 [-65, -65, -68, -68] dBm
tx bitrate: 1.0 MBit/s
tx duration: 367380938 us
rx bitrate: 300.0 MBit/s MCS 15 40MHz short GI
rx duration: 0 us
airtime weight: 256
expected throughput: 270.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:193
short preamble: yes
short slot time:yes
connected time: 420 seconds
associated at [boottime]: 78.595s
associated at: 1682095612376 ms
current time: 1682096032255 ms
Radio Name: root@Julee-Rayne:~# iw wlan1 station dump
Station ca:cf:a5:8f:f9:c0 (on wlan1)
inactive time: 5720 ms
rx bytes: 501471
rx packets: 2340
tx bytes: 6573582
tx packets: 5891
tx retries: 0
tx failed: 0
rx drop misc: 3
signal: -75 [-77, -83, -83, -87] dBm
signal avg: -77 [-80, -85, -83, -90] dBm
tx bitrate: 6.0 MBit/s
tx duration: 9650359 us
rx bitrate: 6.0 MBit/s
rx duration: 0 us
airtime weight: 256
expected throughput: 650.0Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: short
WMM/WME: yes
MFP: no
TDLS peer: no
Powersave: no
Compression: no
DTIM period: 2
beacon interval:163
short preamble: yes
short slot time:yes
connected time: 357 seconds
associated at [boottime]: 152.437s
associated at: 1682095686219 ms
current time: 1682096043443 ms
Radio Name: root@Julee-Rayne:~#
Connection to 10.19.96.30 closed.
mrjcd@Will-Be-Was:~$
Back to top
KACTET DD-WRT User Joined: 01 May 2022 Posts: 252
Posted: Sun Apr 23, 2023 14:52 Post subject:
Router/Version: Netgear XR500
Update method: WebUpgrade
File/Kernel: dd-wrt-webupgrade.bin / Linux 4.9.337 #1812 SMP Thu Apr 20 00:46:29 +07 2023 armv7l
Previous/Reset: r52242 / no
Mode/Status: Gateway / Up and running for 2:42 hours
Issues/Errors: Nothing significant
____________________________________________________________________________________________
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin / Linux 3.18.140-d6 #169602 Thu Apr 20 04:09:34 +06 2023 mips
Previous/Reset: r52330 / no
Mode/Status: AP wired and wireless / Up and running for 1:31 hours
Issues/Errors: Nothing significant
The fact is that the router connected to the Internet (to the Internet provider). And it reports an error, the orange WAN indicator flashes (the icon in the form of a planet). Internet is working, I just think it's a glitch
Thank you BS and gurus! _________________Atheros
Netgear XR500 Nighthawk - DD-WRT 54545
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 55779
Broadcom
Asus RT-AC87U R - DD-WRT 55819
Asus RT-N66U - DD-WRT 55779
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
Back to top
gilius DD-WRT Novice Joined: 18 Oct 2022 Posts: 23
Posted: Tue Apr 25, 2023 5:27 Post subject:
Router/Version: Netgear xr500
File: dd-wrt-webupgrade.bin v3.0-r52369 std (04/20/23)
Kernel: Linux 4.9.337 #1812 SMP Thu Apr 20 00:46:29 +07 2023 armv7l DD-WRT
Previous: v3.0-r52330 std (04/14/23)
Reset: air gap, power cycle, nvram erase && reboot, gui factory reset, reload nvram, scp 'file' to /tmp, write linux, gui reboot, gui nvram save.
Mode: Gateway, AP dd-wrt firmware N-Only 2.4GHz VHT40SGI, 5GHz deactivated, 2 vap
Status: Operational 72h+
Issues: None observed status timeframe
Errors:
kern.err kernel: [ 0.115025] msm_bus_fabric_init_driver
kern.warn kernel: [ 0.151781] 1b500000.pci supply vdda not found, using dummy regulator
kern.warn kernel: [ 0.151895] 1b500000.pci supply vdda_phy not found, using dummy regulator
kern.warn kernel: [ 0.151983] 1b500000.pci supply vdda_refclk not found, using dummy regulator
kern.warn kernel: [ 0.263547] 1b700000.pci supply vdda not found, using dummy regulator
kern.warn kernel: [ 0.263638] 1b700000.pci supply vdda_phy not found, using dummy regulator
kern.warn kernel: [ 0.263727] 1b700000.pci supply vdda_refclk not found, using dummy regulator
kern.warn kernel: [ 0.374140] deviceless supply s1b not found, using dummy regulator
kern.err kernel: [ 1.855509] m25p80 spi32766.0: unrecognized JEDEC id bytes: 00, 00, 00
kern.warn kernel: [ 1.860836] m25p80: probe of spi32766.0 failed with error -2
kern.err kernel: [ 2.822221] Calibration not found.
kern.err kernel: [ 2.826147] CPUidle arm: CPU 0 failed to init idle CPU ops
kern.warn kernel: [ 2.959159] thermal thermal_zone0: failed to read out thermal zone (-110)
kern.err kernel: [ 3.609789] no valid UBI magic found inside mtd5
kern.warn kernel: [ 8.080708] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
kern.warn kernel: [ 8.377028] ath10k_pci 0000:01:00.0: Unknown FW IE: 30
kern.warn kernel: [ 16.447538] ath10k_pci 0000:01:00.0: wmi debug print truncated: 128
kern.warn kernel: [ 16.824844] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
kern.warn kernel: [ 16.834528] ath10k_pci 0001:01:00.0: Unknown FW IE: 30
kern.warn kernel: [ 31.849282] ath10k_pci 0001:01:00.0: wmi command 36872 timeout, restarting hardware
kern.warn kernel: [ 31.849335] ath10k_pci 0001:01:00.0: write_file_turboqam->failed to update channel list: -108
kern.warn kernel: [ 31.889128] ath10k_pci 0001:01:00.0: cannot restart a device that hasn't been started
kern.warn kernel: [ 40.186447] ath10k_pci 0001:01:00.0: wmi debug print truncated: 128
Back to top
ho1Aetoo DD-WRT Guru Joined: 19 Feb 2019 Posts: 2975 Location: Germany
Posted: Tue Apr 25, 2023 6:00 Post subject:
Debug messages that exist for years are not errors.
Back to top
T-Fork DD-WRT User Joined: 06 Oct 2010 Posts: 53
Posted: Thu Apr 27, 2023 8:07 Post subject:
Router/Version: WNDR3700 v1 DD-WRT v3.0-r52369 std (04/20/23)
File/Kernel: Linux 3.10.108-d11 #131134 Thu Apr 20 05:14:00 +06 2023 mips
Previous/Reset: r43397, no reset just for the heck of it.
Mode/Status: Switch, neither radio active
Issues/Errors: nptclient cant resolve adress "Apr 27 10:04:07 WNDR3700 daemon.err ntpclient[7419]: Failed resolving address to hostname pool.ntp.org: Try again"
previous release has been super solid for the past three years and only downtime has been due to poweroutage.
Back to top
egc DD-WRT Guru Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Thu Apr 27, 2023 8:20 Post subject:
T-Fork wrote: Router/Version: WNDR3700 v1 DD-WRT v3.0-r52369 std (04/20/23)
File/Kernel: Linux 3.10.108-d11 #131134 Thu Apr 20 05:14:00 +06 2023 mips
Previous/Reset: r43397, no reset just for the heck of it.
Mode/Status: Switch, neither radio active
Issues/Errors: nptclient cant resolve adress "Apr 27 10:04:07 WNDR3700 daemon.err ntpclient[7419]: Failed resolving address to hostname pool.ntp.org: Try again"
previous release has been super solid for the past three years and only downtime has been due to poweroutage.
Lots of things have changed, coming from such an old build a reset to defaults and put settings in manually is highly recommended, never restore from a backup (to a different build) _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read): https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Back to top