Open a support ticket by clicking on the help button on the right of this page.
Printable View
Open a support ticket by clicking on the help button on the right of this page.
16.1.1 is the most recently available public release everyone no matter what can get. If you've got a unit stuck on v15.1, then I'm left to assume you've got the bad v15.1 build that won't upgrade. It seems some of the z4s are shipping with it, based on the threads around here...Quote:
Originally Posted by tangofan
The only way I know to fix that issue yourself is to reinstall the unit. Untangle support can do something to fix it as well, but as of yet they haven't publicly disclosed what needs done.
Not just z4s. My home system got stuck somewhere back near that level, and support had to "unstick" it so the upgrade would show. They did it once, and it upgraded fine-- I believe to 16.0. But the next release was missing again. They fixed it for me again to get to 16.1, and now that system made the 16.2 jump with no outside help. Both times they got me moving without a re-install.
Hi there
I have multiple public IPs that will be used on devices behind Untangle and would like to use the FW capabilities on Untangle to control incoming and outgoing traffic for these servers.
I have configured the NAT and Port Forward rules and everything is working. However, because we have multiple servers hosting Plesk licenses, the license key does not register as it sees the servers public IP as the firewall.
Is there a way for showing a particular servers OUTBOUND, public IP differently? to the firewalls?
You are looking for 1:1 NAT. There is a wiki page for configuring this. All the IPs are added to aliases in the WAN, then configure the port forwards with matching NAT rules.Quote:
Originally Posted by ZamirRhemtulla
https://wiki.untangle.com/index.php/1:1_NAT
A JCoffin linked, what you're after are NAT Rules. They control what public address internal devices translate to when they go online. Just the inverse of Port Forward rules, which control what private address public requests translate to.Quote:
Originally Posted by ZamirRhemtulla
But a word of caution... NAT Rules do exactly what you tell them to do.
Let me say that again... they do EXACTLY what you tell them to do!
Be precise... as specific as you possibly can be. If you aren't... those rules can over match and cause some really hard to troubleshoot insanity in your day! In the name of the hair left on your head! Please, be careful.
Thanks Rob, it sounds like I indeed have a problem and need to do something about the upgrade eventually.Quote:
Originally Posted by sky-knight
BTW I looked at https://www.untangle.com/cmd/download/ng-firewall to download 16.1.1, but it seems that they only have 16.2 available for download. Is there a way to get downloads of older versions? If not, I'll probably just wait a couple of weeks and then install 16.2 manually.
https://wiki.untangle.com/index.php/...wall_DownloadsQuote:
Originally Posted by tangofan
Thanks so much. May I humbly suggest that you put this link on the bottom of the main website. I can understand that you want folks to only get the latest version, in my case I actually HAD to install an older version, since 16.2 refused to read my configuration file from 15.1.Quote:
Originally Posted by jcoffin
In the end I installed 16.0.1, restored my configuration file successfully and then immediately was offered an upgrade. That upgrade turned out to be 16.2 afterwards. When Untangle tells you that an upgrade is available, it doesn't tell you the version, which would be another nice thing to have.
Checked my Untangle this morning and an update was there waiting for me.
I'm now on: 16.2.0.20201222T155603.0217896f9c-1buster
Upgrade went through without any problems :cheers: