Never create a Host/Network definition bound to a specific interface.
Always leave all definitions with 'Interface: >'.
Last is what I call Rule #4:
When creating DNATs for traffic arriving from the internet, in "Going to:" always use the
"(Address)" object created by WebAdmin when the Interface or the Additional Address was defined.
Using a regular Host object will cause the DNAT to fail as the packets won't qualify for the traffic selector.
First, are you sure that the cameras have the IP of "Internal (Address)" as default gateway?
Next is what I call Rule #3:Never create a Host/Network definition bound to a specific interface.
Always leave all definitions with 'Interface: >'.
Last is what I call Rule #4:When creating DNATs for traffic arriving from the internet, in "Going to:" always use the
"(Address)" object created by WebAdmin when the Interface or the Additional Address was defined.
Using a regular Host object will cause the DNAT to fail as the packets won't qualify for the traffic selector.
Any luck with those?
Cheers - Bob
First, are you sure that the cameras have the IP of "Internal (Address)" as default gateway?
Next is what I call Rule #3:Never create a Host/Network definition bound to a specific interface.
Always leave all definitions with 'Interface: >'.
Last is what I call Rule #4:When creating DNATs for traffic arriving from the internet, in "Going to:" always use the
"(Address)" object created by WebAdmin when the Interface or the Additional Address was defined.
Using a regular Host object will cause the DNAT to fail as the packets won't qualify for the traffic selector.
Any luck with those?
Cheers - Bob