I've never used a BS build. I've never used any other builds other than yours. _________________ Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14) Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
Nope i didn't as the problem only got worse with the newest r37945 build, where I could not get the IPcams to connect to my R7800 in any way, no matter the settings I tried in advanced WIFI settings. The only thing that helped was to go back to previous builds. So something is getting worse with the builds regarding the 2.4Ghz radio.
This time there was no interference from neighbours. But I wonder if its normal to spam with dumbass responses like marketing for ones dissocial disorder?
with https got many of those Kong..im using Ffx for my routers only
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Sat Dec 15, 2018 19:05 Post subject:
i guess its tls 1.0 that i disabled, but still works
and gives me an access somehow and details are not in plain text... just on few of my networks i use http's as i do not trust the clients especially on R7800 _________________ 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
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Dec 15, 2018 20:03 Post subject:
<Kong> wrote:
Alozaros wrote:
with https got many of those Kong..im using Ffx for my routers only
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Dec 13 21:27:11 R7800 daemon.err httpd[5744]: SSL accept error
Your browser tries to use a cipher that the webif does not accept.
can this be the cause of super slow webif over https? (wan)? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Nope i didn't as the problem only got worse with the newest r37945 build, where I could not get the IPcams to connect to my R7800 in any way, no matter the settings I tried in advanced WIFI settings. The only thing that helped was to go back to previous builds. So something is getting worse with the builds regarding the 2.4Ghz radio.
This time there was no interference from neighbours. But I wonder if its normal to spam with dumbass responses like marketing for ones dissocial disorder?
Try latest r37961std from Brainslayer or r37985MKong build but only with reset and manual config.
Or the all workingr37495M [10/28/18] k3.18.124 from Kong.
Well the thing is, it wasn't always like that. A couple of months ago (I don't know exactly when, sorry. But definitly this year.) that worked like a charm and without any problems.
HTTPS has been broken for quite some time. It's just getting increasingly worse. If you use syslog, you would have noticed errors even when it seemingly worked. There's a bunch of weird stuff going on behind the scenes.
As far as I know this is a browser problem, as webif uses a self signed cert for https and some browser have issues with it. Might be an issue since some browsers now consider self signed certs as insecure.
I have been looking into support for letsencrypt, but it is a pain in the ass, as you have to expose a webserver on the wan side while you go through the letsencrypt cert issue process and you have to renew the certs after a certain amount of time. If I find the time for it, I'll try to implement a service for that, but it will only work on builds that come with php and lighttpd.
safari on latest ios
latest firefox on windows
latest edge on windows
latest chrome on windows
all "trigger" the https syslog spam on every router i touch with https on, it wasnt always like this either iirc, after some httpd changes it started from no where..
remote management over https is also as slow as dial up.. stock firmwares over https remote management is as fast as http. so slow i have to vpn then use http over that to get a mix of security and usable speed.
my free syslog host recently went from a tiny 100mb a month to a nearly unusable 50mb a month.. https spam isnt helping.
I just ran a test using https on windows, on a 37900 build I see these:
daemon.err httpd[1679]: Request Error Code 408: No request appeared within a reasonable time period
but that is already fixed in 37908, no other error message and I can click around like crazy. I just tried wan https on a 37900 broadcom build I see no slowdown at least not with chrome under linux.
OK, so whatever was the problem, I can no longer reproduce it.
What I did:
- Re-enabled HTTP web access (this made things fast again)
- Disabled HTTP access again (HTTPS only) and the web interface stayed reasonably fast (37945M).
No error messages in /var/log/messages whatsoever...
I did the same (multiple times even) and my syslog errors persist. It's like some background process is using a login ID other than "root". Why the message is being logged as severity 3 I have no idea, it's just a reminder message anyway. _________________ Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14) Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
Having troubles with my iPhone XR, latest iOS, and the 5GHz band. The phone will connect without trouble to the 2.4GHz band but when trying to switch to 5GHz it will often return "bad password." Other times it's simply "unable to join network." And then eventually it is no longer listed. I have several other Apple devices on the 5GHz in the same location without issue.
I looked through the syslog and saw this frequently with the iPhone:
Dec 18 19:12:23 DD-WRT daemon.info hostapd: ath0: STA e4:b2:fb:d3:fd:c8 IEEE 802.11: disassociated
Dec 18 19:12:24 DD-WRT daemon.info hostapd: ath0: STA e4:b2:fb:d3:fd:c8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Is anyone else having problems with the time set by NTP servers?
On build 37910M it was off by (I forgot exactly how much) about 13 hours and 22 minutes. Now, with 37985M, it is off by just an hour and 22 minutes. It's not a daylight savings time error, either. My timezone is US Central/Chicago, and it is 1h:22m behind; if it was a DST issue, it would be an hour ahead, but the 22 minutes is still very strange.
I've tried us.pool.ntp.org and time.nist.gov, and neither correct the issue (I've rebooted), which leads me to believe it's within the firmware.
I don't recall the problem being in 37900M, which was the first build I tried. I never had time problems with Kongac and my r7000.
EDIT:
I did more fiddling changing around time zones and rebooting many times, and now the discrepancy is 46 minutes, but still an hour behind. This is weird.
I just "cut the cord" - I turned off DirecTV and moved from sonic.net bonded DSL to xfinity gigabit. As part of this I bought a r7800 to replace my older r7000, which has been running ddwrt for years.
I am currently on v3.0-r37985M kongat (12/16/1
The only strangeness I've seen with the r7800 in the dd-wrt builds I've tried (from the October 2018 stable build to the most recent test build) is getting ipv6 to work. I had to set eth0 to promiscuous mode to get ipv6 connections to transit the router. Once this was done, using the command "ifconfig eth0 promisc" the r7800 is working perfectly, including ipv6 connectivity.
With the r7800 and xfinity/comcast gigabit, I'm getting about 800mb down and 40mb up on wired connections, and up to about 550mb down by 40mb up on wireless.
To the prior poster, ntp is working fine for me...
NTP is fine for me as well. US/Central time zone, using us.pool.ntp.org. _________________ Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14) Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
