First it is not an upgrade : the configuration was first done on the 7.200 beta.
I do the following :
- delete the rule
- re-create exactly the same snat at the same position
- I click edit and it display as a DNAT !
- I reboot : same trouble, no packet filter ( please notice: if i use the livelog of the packet filter, i see my attemps en green : so it is not my rules that forbidden my attemps ...)
- I OFF next on the rule #8 ==> Everything OK !...
I missed the details at first glance- your configuration won't work, we can't SNAT an entire network out to "any" for a specific service. It will work if you create a SNAT rule for each host, but not as bulk rule.
As a general rule of thumb, the more specific the better for NAT rules.
but this rule work fine, because actually only one host on the network need it... For test I change the source ITF_LAN(Network) by a specific IP.
A/ When I do that the problem is the same : when I click edit in the SNAT rule, the editor show it as a DNAT and I need to reselect SNAT in the dropdown... Please noticed that I've several other SNAT rule (#2, #1) and when I click edit for them no problem...
B/ I will reboot this evening to see it the rule won't block my packet filter on reboot as before. I will post the result later. --> it doesn't work: after reboot(i've done the 7.290update) I need to OFF/ON my rule as before...
Hi.
Same for me here: HTTPS does not work anymore with .202.
Deleted the HTTPS rule and recreated, no luck.
Does anybody have a quick solution to that?
