Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Sat May 07, 2022 10:07 Post subject:
yep i did check it now...and its showing
so i must ve been confused to report it was US indeed...
root@Netgear:~# iw reg get
global
country CA: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
(5250 - 5350 @ 80), (N/A, 24), (N/A)
(5470 - 5600 @ 80), (N/A, 24), (N/A)
(5650 - 5730 @ 80), (N/A, 24), (N/A)
(5735 - 5835 @ 80), (N/A, 30), (N/A)
than checked "wlan1_regdomain"
wlan1_regdomain=US
and i thought it doesn't make a sense, y US...
so, i started to wonder.....but, i miss-looked the first line of global
country CA: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 30), (N/A)
and i had a wrong believe the putput its all about 5Ghz witch i don't even use...so yep, i was confused, as i was chasing an optimal WiFi settings and possible solution to an issue that I have going around...so, i adopted the believe there must be something wrong with country domains and the NVRAM variable it was showing US...so, now i see what is all about and it seems correct...
I'm sorry for the confusion and thanks for the clarification...
so, nvram setting wlan1_regdomain=US has no function at all...
and i may need to do a reset, when im physically next to the unit _________________ 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
Netgear XR500 - Gateway
Firmware Version: DD-WRT v3.0-r48810 std (05/06/22)
Kernel Version: Linux 4.9.312 #921 SMP Fri May 6 02:24:58 +07 2022 armv7l
Temperatures: CPU 56.291 °C / wlan0 60 °C / wlan1 64 °C
Current Time: Sat, 07 May 2022 15:28:57
Uptime: 17:03
Reset: No
GUI install over 48786
Installed using Brave browser over wireless
No issues
Thank you BS and thanks you gurus for your guides and wisdom _________________ Netgear XR500 - Gateway
R6700 v3 - Station Bridge
Joined: 16 Mar 2019 Posts: 353 Location: Szczecin, Poland EU
Posted: Sun May 08, 2022 8:35 Post subject: New Build - 05/06/2022 - r48810
Router/Version: TP-Link TL-WDR 3600 v. 1.5
Kernel: Linux 3.10.108-d11 #106297 Fri May 6 05:02:06 +07 2022 mips
Reset: No
Mode: Internet gateway, WIFI 5GHz AP, dnsmasq server, iptables firewall
Issues: Wireguard is active probably when it's disabled in GUI, slow WAN port, WIFI range weak. Generally device have worse work.
Status: Working with issues
Uptime: ~1 day, but today I'm make reboot via command line. I'm attach fresh syslog to check possibly problems.
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Sun May 08, 2022 9:01 Post subject:
If you have WireGuard loaded it checks for current time and it seems you do not have current time on your router, that is what it is complaining about.
You can ignore the warning if you do not want/have time setup on your router
Joined: 16 Mar 2019 Posts: 353 Location: Szczecin, Poland EU
Posted: Sun May 08, 2022 11:12 Post subject: New Build - 05/06/2022 - r48810
The current time problem is related to the fact that when I'm dump log the cable to the WAN port was not connected. I do not understand why WireGuard reports in the log when it is completely turned off in the device configuration. Due to the slow performance lately, I will probably do a clean router configuration.
This is my first update since the massive upgrade to the GUI and the overhaul of the wireless code (?). The GUI looks terrific, and the router is performing exceptionally well. Thank you. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
seems more stable than previous build (router had to be restarted at 24hrs on 48786 due to unresponsiveness)
This build is logging some strangenesess from Wireguard locking and unlocking oet1 files. Its strange becuase i have no tunnels or wireguard configured.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Mon May 09, 2022 21:45 Post subject:
it seems wireguard (and sometimes unbound) is complaining about ntp on boot up, since x86_64 takes A YEAR to boot for whatever reason, they are probably starting before ntp client does thus no time set for a while longer and they panic.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
now that ive been running this build for a bit i have some observations
there seems to be some behavioural differenes on
47692 i was able to eek out my best latency with QOS of HTB/cake, netdev max backlog 2k,
in this build the wireless 5ghz doesnt perform as well with those settings. My best overall latencies seem to be with
max backlog - 384, HFSC/FQ_codel
in both cases my networking queue length was modified to 3 from the 1000 default. In wired testing, the difference was only 2-3 ms, depending on how tested.
Not sure what could have changed that would have affected the latency by about 10ms difference in settings.
TP-Link ARCHER-C7 v5 Daul Band Wifi / Router
DD-WRT v3.0-r48810 std (05/06/22
Linux 3.18.140-d6 #141654 Fri May 6 07:24:51 +07 2022 mips
New DD-WRT install uploaded via WebUI.
Mode: Gateway
Uptime: 2 Hrs
My laptop could not connect to 5Gz with Channel set to Auto and for now it is set on channel 36.
This router is being rotated in to replace the Sig unit that will now be updated to current firmware. _________________ ARCHER-C7v5 | v3.0-r55460 std | AP Gateway
WNDR4000|v24-52189_NEWD-2_K3.x_mega|Inactive Spare
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed May 11, 2022 10:42 Post subject:
egc wrote:
You can ignore the logging about WireGuard those are harmless.
But for all you nervous nellies I will remove it in a future build
I'm not a nervous nellie, I'm and anxious whatsit, to me, since I dont use openVPN or Wireguard in DD-WRT it's not even enabled, I find it a waste of CPU cycles to read the noise Wireguard and such makes.
IDK if its possible to grab the state of the options before trying to check whatever it is that any of those are checking.