|Gameman Advanced Kid
Joined: 18 Nov 2012
|Posted: Mon Jan 31, 2022 7:34 Post subject: dd-wrt logging for devs meaningless?
|This has been on my mind for a while.
In the past, I used to test dd-wrt firmware like this. And I only did for probably a short time.
I would fire up putty with logging enabled(I used windows), hook up the router to serial, and turn the router on. And as I was setting up the router while it was hooked up to the router, putty would be logging EVERYTHING into a text file.
Like I would be setting up the router as if it was going to be my main router but only as a test.
If I came across what I thought was an issue at least, I would report it along with posting a serial log. But I stopped doing that because I believe at the time someone told me it was meaningless of me to do it that way.
Years later to now, there was another user I was talking to in another social part of dd-wrt where he was being stubborn about wanting to find out what the error with his wifi issue was in the logs. Even when I insisted he should update his firwmare build on his router, he still wanted to look in the logs and also told me that I was one who "throws poo at something until it works".
So I told him that I am not going to help him any further and didnt care about him talking about how I am trying to "save face".
Is there ANYTHING useful in dd-wrt logging that would help developers? I am referring to copying logs from the webgui or serial and sending it to developers.
If so, how often is it useful?
For people who are new to the dd-wrt forums >> http://www.catb.org/~esr/faqs/smart-questions.html#rtfm
|barryware wrote: |
|It takes a "community" to raise a router.. |
Internet Connection 1
Gateway Router > Linksys WRT3200ACM
Internet connection 2
NAS-AP > Linksys WRT32x
DD-WRT non-official LIVE element/matrix chat
Joined: 16 Nov 2015
Location: UK, London, just across the river..
|Posted: Mon Jan 31, 2022 10:49 Post subject:
|I'm not gonna even ask about this chap's name...
In general when DDWRT is loading, there are lots of "false positives"...and this is the way how it works..don't get me wrong firmware is ok...unless more testers complain on something new, than its worth serial log investigation..
In my believe, providing a serial output could be valuable when issues occur and there is a demand for it...otherwise looking at it and not understanding it correctly, it may look with lots of "false positives"...
TP-Link WR740Nv1 ---DD-WRT 49934 WAP
TP-Link WR1043NDv2 -DD-WRT 50308 Gateway,DNS,AP Isolation,Ad-Block,Firewall,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 -DD-WRT 50308 Gateway,DNS,Ad-Block,Firewall,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 -Gargoyle OS 1.13.0 AP,DNS,QoS,Quotas
Netgear R7800 --DD-WRT 50357 Gateway,DNS,AD-Block,AP&Net Isolation,VLAN's,Firewall,DoT,Vanilla
Netgear R9000 --DD-WRT 50146 Gateway,DNS,AD-Block,AP Isolation,Firewall,Forced DNS,DoT,2,4Ghz only,Vanilla
Netgear R7000 ---DD-WRT 50357 Gateway,DNS,AD-Block,Firewall,Forced DNS,VLAN's,DoT,VPN
NOT USING 5Ghz ANYWHERE
Stubby for DNS over TLS I DNSCrypt v2 by mac913