This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NAT with 7.300

I just had a gotcha pop up that may get others:

After applying 7.300 update, all of my NATS were disabled. This was due to my use of the service type "ANY".

A quick work around is to make a group called "Everything" or "ALL"....etc
and add the existing "ANY" service to it.

Change your NATS to use this new group and all will be fine.

Hope this helps someone.

Matt

This thread was automatically locked due to age.

Parents

0 Paul.Carpenter over 17 years ago

I've tried your work around but it still blinks at me when I use the group.

Any other suggestions from anyone?
Cancel
Vote Up 0 Vote Down

Cancel
0 Jack Daniel over 17 years ago in reply to Paul.Carpenter

Use of the "ANY" service group has been problematic, disabling its use was done as a sanity check. You may need to create a more limited group to get best results.
Cancel
Vote Up 0 Vote Down

Cancel
0 William Warren over 17 years ago in reply to Jack Daniel

oh great. I've just killed my remote access by installing this update. So any is now disabled?
Cancel
Vote Up 0 Vote Down

Cancel
0 Jack Daniel over 17 years ago in reply to William Warren

NAT rules with a service of "any" are disabled by the update. If you need that functionality (and it hasn't broken things in the past), create a service group and add the any service definition to the group.
Cancel
Vote Up 0 Vote Down

Cancel
0 BarryG over 17 years ago in reply to Jack Daniel

Does this apply to Masquerading too?

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 William Warren over 17 years ago in reply to BarryG

Does this apply to Masquerading too?

Barry

no masquerading is NOT affected.
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 17 years ago in reply to William Warren

Just redefine inbound NAT rules without using ANY as the NATted service... this problem showed up when I loaded 7.200 at a few customer sites; redefining their NAT setup to use specific (the required) services instead cleared it right up. In 7.300 Astaro has simply disabled the ability to even use ANY, presumably to keep new users from configuring the problematic ANY rules.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BrucekConvergent over 17 years ago in reply to William Warren

Just redefine inbound NAT rules without using ANY as the NATted service... this problem showed up when I loaded 7.200 at a few customer sites; redefining their NAT setup to use specific (the required) services instead cleared it right up. In 7.300 Astaro has simply disabled the ability to even use ANY, presumably to keep new users from configuring the problematic ANY rules.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data