I can already guess how it will market Merlin, send us to Mars!
That's why this project is so great, and without the great you, there would be no such great project.I grew up on C64 BBSes, not mobile texting or typing in WhatsApp
Can you format the following git log into a human-readable changelog, categorizing fixes and additions?
(followed here with the output from git log 386.9..HEAD)It looks like a typesetting format prepared for markdown.
Yes, if it's a markdown-formatted log,
Never paid attention to the radio temperatures, it was always the CPU, and much better now since I did the mod.
when 300 baud, a serial line and ascii dinosaurs ruled the the world...I grew up on C64 BBSes, not mobile texting or typing in WhatsApp
Feb 19 18:12:54 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Feb 19 18:12:54 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0nvram show, and try to shorten settings where possible, making changes such as...-vpn_server2_ncp_ciphers=CHACHA20-POLY1305:AES-128-GCM:AES-256-GCM:AES-128-CBC:AES-256-CBC
+vpn_server2_ncp_ciphers=AES-256-CBCssh-ed25519 instead of ssh-rsa for SSH access (566 bytes -> 94 bytes)❯ for line in `nvram show | grep -Eo '^[^=]+\=$' | cut -d"=" -f 1`; do nvram unset $line; done
size: 62231 bytes (3305 left)
❯ nvram show | wc -c
size: 52779 bytes (12757 left)
52759
❯ nvram commit
#
# reboot router and reconnect
#
❯ nvram show | wc -c
size: 62124 bytes (3412 left)
62104RMerlin explained the reasons why older AC routers are seeing these low NVRAM errors crop up, see this link:
The solution for now seems to be, do a hard factory reset after flashing 386.9 and manually reconfigure the router (don't restore from a backed up config file). Or try some of the suggestions in this thread, like this from SSH:
for line in `nvram show | grep ^[^=]*=$ `; do var=${line%*=}; nvram unset $var; done; nvram commitI assume you've done the same for the following VPN client settings:
vpn_client_ncp_ciphers=
vpn_client1_ncp_ciphers=
vpn_client2_ncp_ciphers=
vpn_client3_ncp_ciphers=
vpn_client4_ncp_ciphers=
vpn_client5_ncp_ciphers=#!/bin/sh
####################################################################
# CleanupNVRAMvars.sh
# To remove deprecated NVRAM entries for VPN & SSH keys.
# Last Modified: Martinski W. [2023-Feb-23]
####################################################################
set -u
_UnsetNVRAMvars_()
{
if [ $# -eq 0 ] || [ -z "$1" ] ; then return 1 ; fi
local Count="$(nvram show 2>/dev/null | grep -c "^$1")"
if [ $Count -gt 0 ]
then
if [ $# -eq 2 ] && [ -n "$2" ] && \
$doNVRAM_unset && echo && ! _PromptForYesOrNo_ "$2"
then return 10 ; fi
if "$firstRun" ; then firstRun=false ; echo "$SEPstr1" ; fi
for KeyStr in $(nvram show 2>/dev/null | grep "^$1")
do
if ! echo "$KeyStr" | grep -qE ".*[=]+.*"
then Count=$((--Count)); continue ; fi
echo "KeyName: [${KeyStr%%=*}]"
$doNVRAM_unset && nvram unset "${KeyStr%%=*}"
done
echo "VARs COUNT: [$Count]"
$doNVRAM_unset && \
echo "COUNT AFTER: [$(nvram show 2>/dev/null | grep -c "^$1")]"
echo "$SEPstr1"
doNVRAM_commit=$doNVRAM_unset
return 0
else
echo "NVRAM variables [${1}.*] NOT FOUND."
return 1
fi
}
_PromptForYesOrNo_()
{
read -n 1 -p "$1 [Y|N] N?" YESorNO
if [ -z "$YESorNO" ] ; then return 1 ; fi
echo
if [ "$YESorNO" = "Y" ] ; then return 0 ; fi
return 1
}
firstRun=true
doNVRAM_unset=false
doNVRAM_commit=false
SEPstr0="=================================================="
SEPstr1="--------------------------------------------------"
if [ $# -gt 0 ]
then
if [ "$1" = "-unset" ]
then doNVRAM_unset=true
else echo "*UNKNOWN* Parameter [$1]." ; exit 1
fi
fi
echo -n "NVRAM " ; nvram show | grep "^size: "
echo "$SEPstr0"
_UnsetNVRAMvars_ "vpn_crt_client"
_UnsetNVRAMvars_ "vpn_crt_server"
_UnsetNVRAMvars_ "sshd_.*.key="
for VPNnum in 5 4 3
do
_UnsetNVRAMvars_ "vpn_client${VPNnum}_" "Remove ALL OpenVPN Client${VPNnum} variables?"
[ $? -eq 10 ] && echo "Skipping OpenVPN Client${VPNnum} variables."
done
echo "$SEPstr0"
echo -n "NVRAM " ; nvram show | grep "^size: "
if ! "$doNVRAM_commit"
then echo "NOTHING to commit."
else nvram commit ; echo "Completed successfully."
fi
#EOF#./CleanupNVRAMvars.sh -unsetThat's a very good point, in particular for lower-powered routers such as the RT-AC68U.
./CleanupNVRAMvars.sh -unsetI have found this works until reboot. The keys will reappear.
Yes, you're absolutely right. I had forgotten that back in 2020, for the RT-AC68U routers, I had set up the "old" 2020 version of the script to run during every reboot from the "/jffs/scripts/init-start" script. That's why since then, whenever I checked the free NVRAM space, the router always appeared to have just enough, and we never saw the "Low NVRAM" warning message.
./CleanupNVRAMvars.sh "5 4 3 2 1"./CleanupNVRAMvars.sh "5 4 3" -forceunsetmkdir -m 755 -p /jffs/scripts
curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused pastebin.com/raw/VhqMzBtt | tr -d '\r' > /jffs/scripts/CleanupNVRAMvars.sh
chmod 755 /jffs/scripts/*.sh
Ahhh, that explains “Feb 24 12:05:16 dnsmasq[2237]: reducing DNS packet size for nameserver 8.8.4.4 to 1232” in my SysLog. Excellent
Why would these log entries appear of spanning tree protocol is disabled?
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!