Recent content by MinkyMomo

  • ATTENTION! As of November 1, 2020, you will not be able to reply to threads 6 months after the thread is opened. Threads will not be locked, so posts may still be edited by their authors.
  1. M

    Automating a home water main shutoff valve

    I went with YoLink myself; loving it so far but this coming winter will be its first, so keeping a eye on it...
  2. M

    Custom firmware build for R7800 v. 1.0.2.75.1SF & v. 1.0.2.75.2SF

    Reporting no anomalies with IPv6 on 1.0.2.75.2SF. Thank you, Voxel!
  3. M

    Custom firmware build for R7800 v. 1.0.2.74.2SF & v. 1.0.2.74.3SF

    I lost the ability to connect to my Sonos devices from the phone app upon upgrading from 74.1SF to 74.2SF, and dropped back to 74.1SF; upon upgrading to 74.3SF, my Sonos devices are back. I do run OpenVPN server on my router.
  4. M

    Custom firmware build for R7800 v. 1.0.2.67SF & 1.0.2.67.1SF

    Out of curiosity, I set up pi-hole in a new VM. My R7800 is on 67SF with IPv6 enabled; neither stubby nor dnscrypt is enabled. It remained responsible for DHCP, and advertised a single DNS entry that points to the pi-hole VM. pi-hole itself was configured with Cloudflare as the only upstream DNS...
  5. M

    Custom firmware build for R7800 v. 1.0.2.67SF & 1.0.2.67.1SF

    I tried v2.3.7.6 of the Nighthawk app. I'm running 67SF on my router, and connected locally to it. I tried to turn remote management ON and failed; the app reports "Some error occurred while enabling/disabling remote management". I don't use remote management myself, but it does appear that...
  6. M

    Kamoj information add-on V3 for Netgear R7800 X4S and R9000 X10 (Temperatures a.o.)

    Nice work, Kamoj... I'm puzzled by the screenshot you provided though--the version strings all say R7800 and yet there's a phantom 802.11ad radio listed... Is this the same bug previously reported by percy3? Perhaps an old screenshot?
  7. M

    Custom firmware build for R7800 v. 1.0.2.61SF

    If AT&T's wifi calling feature is anything like T-Mobile's, you ought to be good with 61SF -- I haven't had any issues with the latter...
  8. M

    Custom firmware build for R7800 v. 1.0.2.61SF

    Re: ping response, that was an oversight. As for DoS protection, I had been running some software before that didn't like that feature enabled. I can't for the life of me remember now what it was, but I'm pretty sure I'm no longer running it :)
  9. M

    Custom firmware build for R7800 v. 1.0.2.61SF

    I've been running 61SF with stubby OFF for several hours now, and my wired/wireless connections have been stable. Perhaps not coincidentally, I noticed in my logs that I've been under DoS attack (ACK Scan, TCP/UDP Echo, TCP/UDP Chargen, Ascend Kill, SYN/ACK Scan), and "Disable Port Scan and DoS...
  10. M

    Custom firmware build for R7800 v. 1.0.2.61SF

    I've been running 61SF with stubby ON since it came out; I was running 60SF without stubby before that. Since yesterday, I've had both wireless radios cut out suddenly, and the router become unreachable through a wired connection. I've done a factory reset and reloaded my settings from backup...
  11. M

    Custom firmware build for R7800 v. 1.0.2.61SF

    Another fantastic update, Voxel. Upgraded from 1.0.2.60SF, enabled stubby (using stock settings for now), and all's well. Thanks!
  12. M

    Kamoj debug-page add-on for Netgear R7800 X4S running Voxel Firmware

    wl_channel=0 wla_channel=157 Prior to reenabling Telnet to obtain these results, I viewed the debug page and saw CH:0 for the 2.4GHz radio. I do have several clients connected to the 5GHz radio at this time.
  13. M

    Kamoj debug-page add-on for Netgear R7800 X4S running Voxel Firmware

    I see this as well (CH:0,...,RSSI:No device connected).
Top