Recent content by Bill_Stewart

I wanted to see if I could reduce the amount of time that the router would get a private IP address. I have successfully accomplished this by changing the following settings in the configuration: Home Network -> Subnets & DHCP: DHCP Lease: 0:0:3:0 <i.e., 3 minutes, which is the minimum...

I am pretty confident this is confirmed. I tested rebooting the router early this morning and watched the IP assignment on its WAN interface after the reboot completed. At first, the WAN interface got a private IP from the BGW320-505's DHCP server, but a few minutes later it got a public IP...

Yes, probably after the lease expires and it goes to renew it.

As of Feb 2026 I am an AT&T subscriber and they provided a BGW320-505 as the gateway device. I already have a robust ASUS router set up with the features I want and I want to use the BGW320-505 as the gateway only. Here's my working configuration for those who might be curious: Home Network ->...

The Keep Connect device detected another DNS failure and power-cycled the cable modem, restoring connectivity with no input from me. This device seems to be well designed and works as advertised.

I would think it would be highly advisable that the "server" software stays updated as security vulnerabilities are discovered.

The Keep Connect device reported a DNS failure early this morning (1:37am local time), rebooted the cable modem, and emailed me that the reboot completed. So far, I can report that this device works as advertised.

I haven't had an outage yet, so the Keep Connect hasn't been tested. Perhaps I will disconnect the cable modem's coax and test that way. I'll post results of that testing some other time.

Ah ok, that makes more sense.

Please explain what you mean by "locally or remotely." By remotely, are you saying you can manage the Keep Connect device when you are not connected to your home network?

You don't have to have a subscription to use it. As I understand it, a subscription would only be needed to access the device remotely.

I don't consider AsusWRT on my consumer-grade router to be high enough quality software to avoid at least one reboot a week to prevent odd "issues." A weekly scheduled reboot has been my practice for several years now and has worked very well. The outage is less than 5 minutes, is in the middle...

My cable modem (an SB8200v3) has been stable since I installed the Keep Connect device. I still schedule my router to soft reboot weekly. No issues yet.

I think it's not good practice in general to use plain http if there are credentials in use. Agreed the risk is pretty low as long as the Keep Connect device credentials don't match anything else.

I have it set up, and it seems to have a fairly healthy number of configuration settings. For now the web interface is only available over unsecured http (not https), which I think is an oversight the vendor needs to rectify. I am going to contact them about it.