Builds since about 40831 have cpufreq set to "performance" (always 1400 MHZ) for this router on both cores.
If you prefer "ondemand" (idles at 800MHZ until needed)
Use this command in CLI or save as startup:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
To flash the proper firmware, first I go to the router database and flash the factory to dd-wrt file then flash the firmware I choose. Am I correct in this?
Posted: Fri Oct 11, 2019 12:43 Post subject: Forgeting everything
My health is declining and I keep forgetting stuff.
Sometimes I just give up and steam something, lol..
But this one has got me posting questions again...
dd-wrt starts its servers on [::]:{port number here}.
I can telnet into and connect to anything on the ip4v listening sockets and see that it works fine (2 way data). I am just confused about ipv6 and the way it works. If I try to telnet into say the web interface on [::]:80 from the shell, I try to type
telnet ::80, or telnet ::1:80 (or telnet ::1 80) and it doesn't say "connected!" like it does with ipv4 addresses. It just does to a page that echoes what I type indefinitely (like it is a null connection).
The reason for all of this is that every server I bind to the local [::] or the supposed ipv6 loopback [::1] does not allow any connections to it. I can't communicate to any socket even though they show they are listening! No connections can every get to it.
This is standard, full nvram reset, dd-wrt, with simple entware installed on a usb disk.
obviously I may be missing a kernel flag I can set via the echo command or maybe it is the firewall? I just need some help as to figure out why nothing can ever connect to anything on ipv6 loopback, and just for kicks I tried binding some servers to the linklocal on the br0 device (the bridge) on mine it is %9, so [fe80::%9] is link local for bridge, but maybe I don't understand it right. As I think that it is unicast only? Anyway, I tried to bind servers to those types of addresses only to be greated with "unable to bind to socket" errors for any fe80::{scope} that I tried.
So between nothing communicating on [::]:{port#here}, or [::1]:p# , or fe80::{scope}. I am at one of those points where I could use some direction.
--- Just an update ---
I used nmap and it confirms what I thought
root@northpole:/etc# nmap -6 ::1
Starting Nmap 7.70 ( https://nmap.org ) at 2019-10-11 09:23 EDT
Nmap scan report for ::1
Host is up.
All 1000 scanned ports on ::1 are filtered
Nmap done: 1 IP address (1 host up) scanned in 201.88 seconds
root@northpole:/etc# nmap 127.0.0.1
Starting Nmap 7.70 ( https://nmap.org ) at 2019-10-11 10:02 EDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000096s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
Nothing is accessable via the linklocal and loopback for IPv6, it is all closed. I can only access the IPv4 side of the server ports...
--> DD-WRT v3.0-r41269 std (10/10/19)
Any suggestions to try?
All righty then! So I did some more digging and installed ipv6calc, generated a ULA fdab:cdef:1234:: for the lan switch, then added it to firewall just to be sure it wasn't stopping anything, and nmap still can't access it. I also can't telnet into it directly. So something is blocking it. I can ping it from the router, and from a remote box, but I can't get any process to access any ports on the ULA.
At this point I would like to know for academic reasons, so feel free to chime in.
But, alas, I am giving up for now... Time to go binge watch Farscape.
Last edited by roadrun777 on Sat Oct 12, 2019 5:42; edited 1 time in total
Thank you, you’ve really helped clear things up! Looks like backing everything up is the most difficult part of the whole process next to choosing the right firmware and knowing someone is happy with a stable version really helps.