Recent content by GeneM

OMG, apologies. I didn't even see those fields above the log. o_O That did it. Thanks for the follow-up.

Greetings. My log file is getting bombarded with successful Dropbear messages, everytime Home Assistant is checking on things (ssh is only open to LAN.) I'd like to say this started with 384.13_1, but I can't be 100% certain. Is there anything I can do to reduce this logging level? Or...

Thank you for taking the time to pull together this post. I agree. Though the nvram tool sounds like something I can't use to restore, browsing the backup files it created certainly provides a lot of this into in a text format, so that will also help along with the screenshots. Not looking...

Yep: Just finished adding it. Thanks. Without that nvram tool, this will be approaching prohibitive. I can start with the built-in saves, test after the factory, and if the log messages are gone, try to just restore those saves. If they restart .... Gentlemen: Thank you for your time today...

Ok, disabled QoS. I saw that earlier and am now wondering if that's on me somehow. I would like to ensure the Adaptive QoS handles our Voip. Well, I'll play with these Wemos to see if a full reset etc helps, but if not, I need to figure out how to set those two files to zero on every boot....

It is, tnx. Now what! I'll need to reboot the router to see whether these cost/bust settings revert, but this isn't great for three days of investigation. That said, you guys have been great. I wouldn't be here w/o you. I'd be re-entering in my router config until the wee-hours, with no change!

Not getting it: Set cost to 0: no log entries Set cost to 15: they're back: Feb 23 15:39:32 kernel: net_ratelimit: 9 callbacks suppressed Feb 23 15:44:32 kernel: net_ratelimit: 30 callbacks suppressed Feb 23 15:45:32 kernel: net_ratelimit: 25 callbacks suppressed Set cost to 15, burst to 70...

ok, two of my 6 units restart the logging. Plugged one in next to me here - messages restarted Feb 23 15:35:32 kernel: net_ratelimit: 18 callbacks suppressed Feb 23 15:36:32 kernel: net_ratelimit: 21 callbacks suppressed Feb 23 15:37:32 kernel: net_ratelimit: 41 callbacks suppressed Feb 23...

Good question. Took a bit, but I see I instanced it (at least) in Home Assistant's UPnP add-in. I think I would, yes. Second Wemo plug in, the log started. Hoping the other 5 don't do the same...

:oops: LMAO Getting too old. You gotta love-it when trying to trace a log message has you moving furniture. Ok, yanked all 6 Wemos - and that appears to have stopped the logging. Now - off to put one back at a time.

I'm starting to think that. I can go yank the 6 of them... (I think) big time... Attaching a txt file.

SSH to the router w/admin is not letting me edit the files. The site I found that suggests: sysctl -w net.core.message_cost=0 sysctl isn't there (or isn't there for me) either. I haven't used Linux since HP-UX in the early 90s! Not seeing anything strange in WireShark. Maybe I should just live...

I'm considering editing the files: /proc/sys/net/core/message_cost /proc/sys/net/core/message_burst to limit suppression. A simple reboot should get them back to 5 and 10. (Linux: Getting rid of “net_ratelimit: N callbacks suppressed” messages)

What! OMG. What are my options? All this config, VPNs, certificates, .... I'd live with the log issue rather than doing all this reconfig from scratch (if I wasn't hosting a bot!). Is this really what's expected of everyone at (each | major) firmware upgrade?

Firewall>General> Is "Enable DoS protection" Yes Are you hosting something on your router.... That's what I've been fretting over for two days now. I do not believe so. However, I recently added a Rasp Pi with Home Assistant. But, I shut that down, and this doesn't stop.