RAXE300-100NAS will not accept port triggering rules

---

VideoGuy wrote:

The RAXE300 is your new router? Which router showed that similar issue before?

 

I had a Netgear Nighthawk R7900P (?).  I had similar problems with it.  Then, I located that Sensi app note and programmed those rules and if memory serves, everything worked right after.  Fast-forward 3 months and my internet service went down for a day.  When it came back on and I rebooted my modem and Netgear router (to solve other IoT device issues), the thermostat nightmare began again.

 

At the risk of going down the wrong path, why am I able to program port forwarding rules and not port trigger rules?

---

Can only guess. Potential reason is one of the ports is already occupied, typically the ubiquitous 80 or 443, for example by some UPnP-SSDP-enabled systems on the LAN (UPnP. NAT-PMP IGD Port Mapping Protocol), reserving a some port forwarding for it's own purpose, pointing to another LAN IP address, making it impossible to configure another port forwarding on top pf it.

Very vague, port trigger is always triggered by establishing a connection to a port forwarded service. Port triggering is done by defining a port which does trigger the open (NAT port forward) additional ports and/or protocols, for example you establish a connection to a server eg. on 80 (http) or 443 (https), from the Internet, to the public IP address (where a DNS entry is pointing to) which does trigger additional port forwardings. 

When looking over that famous IoT help, I see different IoT models with probably gain overlapping services. But this almost certainly isn't the case. Simply because no port forwarding is -ever- used or required for generic IoT devices.

Said this: The IoT service provider does certainly have diagnostic peek-and-poke options way beyond of what we can do here in the community. And fighting red herrings does barley lead to any results.