Closed m4h3 closed 6 years ago
Hi Marc, Already available. Here is the doc:
http://smc-python.readthedocs.io/en/latest/pages/reference.html#ipv4natrule
On Tue, Nov 21, 2017 at 9:04 AM, Marc Hébrard notifications@github.com wrote:
Hey,
It would be nice to have support fw NAT rules.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gabstopper/ansible-stonesoft/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AOIA1cMaqMEW7YYJsUihjlaUYfMR5-C8ks5s4uaTgaJpZM4Ql-1K .
I'm confused. I'm aware about the smc-python capability, but I don't see an ansible mapping to rule_nat.* objects
You're right. I was replying from a smc-python perspective. I don't yet have the NAT in the ansible package. Also, i will update the package tonight, I think the latest model is more clean than the previous. I've also collapsed the engine creation so all interfaces can be created in one fell swoop.
On Tue, Nov 21, 2017 at 2:07 PM, Marc Hébrard notifications@github.com wrote:
I'm confused. I'm aware about the smc-python capability, but I don't see an ansible mapping to rule_nat.* objects
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gabstopper/ansible-stonesoft/issues/1#issuecomment-346145692, or mute the thread https://github.com/notifications/unsubscribe-auth/AOIA1VBFD0XUF3gmr3RH8IPDK-JDgqZyks5s4y1-gaJpZM4Ql-1K .
NAT rules have been added and exist on the develop branch. There is also a howto in the develop based docs link from the README as well.
Hey,
It would be nice to have support fw NAT rules.