Polisy cannot be found after router reboots.

[xgfreon]

I have my home router setup to reboot every other day. after a reboot my polisy cannot be found and no longer runs programs. I have to hard reboot the polisy to get it back again. why wont it reconnect to the network when the router comes back online?

[Techman]

For some reason the router isn't seeing the Polisy. Make sure the Router is set up to "use the router as a DHCP server".

Try reserving a fixed IP address to the Polisy in your Router

[xgfreon]

It has a reserved ip from the router. It doesn’t always get lost on reboots but it’s more than half the times. I use ASUS with Merlin custom firmware. A few of the Alexa echo devices will require a reboot on occasion as well. I guess I’m just looking to make sure it’s not polisy related before I dig into a router firmware bug.

[MrBill]

The real question is why are you rebooting your router every other day?  That seems like treating the symptoms not the disease.

[larryllix]

12 hours ago, xgfreon said:

It has a reserved ip from the router. It doesn’t always get lost on reboots but it’s more than half the times. I use ASUS with Merlin custom firmware. A few of the Alexa echo devices will require a reboot on occasion as well. I guess I’m just looking to make sure it’s not polisy related before I dig into a router firmware bug.

I had a lot of trouble with that combination. I was running an AC68u ??? with the Merlin firmware. Turns out that version had an NVRAM shortage, ASUS knew it and replaced it with double = 128KB NVRAM later in the production.

When I went back to the ASUS firmware the problem cleared up for a while but re-appeared later. I tried adding two of the latest Ax92u mesh routers to the pile and it made them a mess also. Until I garbaged the AC68u and had one Ax92u routers fixed by ASUS my problems persisted. Look for revision 'A' IIRC.

When the power blinked or I rebooted the router, every device would contact the DHCP server for an IP address. Having about 80 devices, sometimes my ISY994 and/or my polisy would not get an IP address, or it was forgotten due to a shortage of router memory. Of course ISY994 and polisy would attempt to carry on with IP addresses of 0.0.0.0 and that a made a mess of my LAN network. Things got very intermittent and undependable for about a year or more.

The Ax92u routers didn't have the same NVRAM shortage. They have other problems. Putting my HA back onto an old Netgear router (without power killing mesh) made things work like the old days. Faster and totally reliable again.

In the end, Merlin firmware kept adding new features without consideration if the router had the hardware to even support them and ASUS routers? hmmmmm.. I still have a few hairs left on my head.

 

[jec6613]

13 hours ago, xgfreon said:

It has a reserved ip from the router. It doesn’t always get lost on reboots but it’s more than half the times. I use ASUS with Merlin custom firmware. A few of the Alexa echo devices will require a reboot on occasion as well. I guess I’m just looking to make sure it’s not polisy related before I dig into a router firmware bug.

It definitely is a router firmware bug of some description.  The Polisy adheres strictly to the DHCP and DNS protocol, which can cause issues with some buggy DHCP and DNS implementations.

Is the Polisy pingable via IP and just not findable?  In which case, it's an issue with the DNS not working properly.  If not, it's an issue with DHCP not issuing an IP and Polisy being strict doesn't retry for a while.

[xgfreon]

5 hours ago, larryllix said:

I had a lot of trouble with that combination. I was running an AC68u ??? with the Merlin firmware. Turns out that version had an NVRAM shortage, ASUS knew it and replaced it with double = 128KB NVRAM later in the production.

When I went back to the ASUS firmware the problem cleared up for a while but re-appeared later. I tried adding two of the latest Ax92u mesh routers to the pile and it made them a mess also. Until I garbaged the AC68u and had one Ax92u routers fixed by ASUS my problems persisted. Look for revision 'A' IIRC.

When the power blinked or I rebooted the router, every device would contact the DHCP server for an IP address. Having about 80 devices, sometimes my ISY994 and/or my polisy would not get an IP address, or it was forgotten due to a shortage of router memory. Of course ISY994 and polisy would attempt to carry on with IP addresses of 0.0.0.0 and that a made a mess of my LAN network. Things got very intermittent and undependable for about a year or more.

The Ax92u routers didn't have the same NVRAM shortage. They have other problems. Putting my HA back onto an old Netgear router (without power killing mesh) made things work like the old days. Faster and totally reliable again.

In the end, Merlin firmware kept adding new features without consideration if the router had the hardware to even support them and ASUS routers? hmmmmm.. I still have a few hairs left on my head.

 

Yea im at like 60 devices and on 88u running diversion and the other toys on merlin. Its probably time to let go of all that.

ram always maxed and cpu's get maxed over time, hence the reboots. 

[larryllix]

I

34 minutes ago, xgfreon said:

Yea im at like 60 devices and on 88u running diversion and the other toys on merlin. Its probably time to let go of all that.

ram always maxed and cpu's get maxed over time, hence the reboots. 

I never had problems with the Ax92u routers for the quantity of devices being kept track of but I had my HA devices (about 50 mostly bulbs) all on an AP - my old Netgear router. It put out a lot more signal power than the ASUS units after they discovered each other and became a mesh. It seems they turn the output power down so the zones are smaller and don't disturb the neighbours as much.

Even though I still had a single Ax92u handling all the DHCP entries and keeping track of the connection list it always did one thing badly. Certain devices would just lose their rights to connect with the Internet/WAN side. Signals were good. Connections inside the LAN were good and worked. Some devices would lose the connection between WAN and LAN about once per month at random. Never figured it out.

The think I hated the most was there was never any reporting of any problem in logs, on screen etc. There was no way of knowing anything was happening except that random things would stop working. Most of the time a reboot or soft reboot wouldn't fix it. It took a power cycle of the router.

Also when meshed the 5GHz band went so quiet my wife's iPad couldn't use it in the same room. The high end WiFi 6 was excellent though.

Edited September 21, 2022 by larryllix