Announcement

Collapse
No announcement yet.

NG Firewall 17 Beta now available for preview

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Question: why when I restore a backup and don't want to restore the network adapter assignment I lose all dhcp assignments, bypass rules, etc. why can't I do a restore, and it brings everything, but the network adapter assignments.

    Comment


    • #17
      Originally posted by jcoffin View Post

      There was a bug in the beta allowing the wrong backup for restoring. It will be fixed in the release.
      Got a patch for that so we can test the beta more?

      Comment


      • #18
        Originally posted by djrees View Post

        Let make sure I understand. You restored a 16.5.2 backup to 17.0 Beta? That does not make sense that an older backup version worked. I will wait till it is able to take my 16.6.2 backup.
        Yes, I virtualize my untangle service. So I had a backup of my 16.5.2 instance, and (at the time) my 16.6.2 instance. When 17.0 wouldn't take my 16.6.2 backup, I spun back up my 16.5.2, made a backup, and used that backup to restore my config in 17.0.

        Understanding that, "There was a bug in the beta allowing the wrong backup for restoring. It will be fixed in the release," why wouldn't a older backup restore on a newer version? Your question makes it sound like I broke a cardinal rule...

        I can offer that 17.0 is running fine for the last couple of days. NSTR ATT.

        Comment


        • #19
          Originally posted by flynhawaiian View Post
          Question: why when I restore a backup and don't want to restore the network adapter assignment I lose all dhcp assignments, bypass rules, etc. why can't I do a restore, and it brings everything, but the network adapter assignments.
          'Network settings', in this context, means everything in Config > Network.

          Originally posted by dlsolo View Post
          why wouldn't a older backup restore on a newer version? Your question makes it sound like I broke a cardinal rule...​
          You didn't, but NG Firewall did: backup files are only valid for the version they are drawn on and one version 'newer'. A backup taken on 16.5 should only be viable on 16.5 and 16.6.
          Græme Ravenscroft • Technical Marketing Engineer
          ('gram', like the unit of measurement)
          he/him
          How can we make Arista ETM products better?

          Comment


          • #20
            Originally posted by gravenscroft View Post

            You didn't, but NG Firewall did: backup files are only valid for the version they are drawn on and one version 'newer'. A backup taken on 16.5 should only be viable on 16.5 and 16.6.
            Thanks for the clarity. Understood.

            Comment


            • #21
              Good to know. Wish there was a more advanced mode where you could check exactly what you wanted restored in the settings. Just provides a much more uniform restore method.

              Comment


              • #22
                Originally posted by changelog
                System - Network interface configuration to physical adapter association was rearranged after reboot on specific types of hardware
                I know some people here are gonna be pretty happy about that one.
                Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.5.2 to protect a 1Gbps fiber link for ~450 residential college students and associated staff and faculty

                Comment


                • #23
                  Originally posted by jcoehoorn View Post
                  I know some people here are gonna be pretty happy about that one.
                  Indeed, but the standard caveat does apply here: we don't test on hardware that isn't our own. We saw the issue occurring on a few older uSeries and zSeries platforms and conclusively fixed it for those. The fix is implemented in a way that we're confident will work for any given hardware platform, but we don't say so for sure. (And indeed, never have.)
                  Græme Ravenscroft • Technical Marketing Engineer
                  ('gram', like the unit of measurement)
                  he/him
                  How can we make Arista ETM products better?

                  Comment


                  • #24
                    Originally posted by gravenscroft View Post

                    Indeed, but the standard caveat does apply here: we don't test on hardware that isn't our own. We saw the issue occurring on a few older uSeries and zSeries platforms and conclusively fixed it for those. The fix is implemented in a way that we're confident will work for any given hardware platform, but we don't say so for sure. (And indeed, never have.)
                    My understanding is that we must do incremental upgrades if we are not on 16.6.2 to get to 17.0; so if we're on 16.5.2, we have to upgrade to 16.6.x in order to go to 17. Is that correct?

                    If so, I still have concerns because a number of our devices are in remote offices (all Untangle-branded), some several hundred miles away, and I'm concerned I'll need to upgrade to 16.6.x first which may break the interfaces prior to upgrading to v17. Please let me know if this is correct or not.

                    Comment


                    • #25
                      Originally posted by LoneWolf View Post

                      My understanding is that we must do incremental upgrades if we are not on 16.6.2 to get to 17.0; so if we're on 16.5.2, we have to upgrade to 16.6.x in order to go to 17. Is that correct?

                      If so, I still have concerns because a number of our devices are in remote offices (all Untangle-branded), some several hundred miles away, and I'm concerned I'll need to upgrade to 16.6.x first which may break the interfaces prior to upgrading to v17. Please let me know if this is correct or not.
                      Maybe you should create the .link files before you start upgrading? Here is a 17 link file info.
                      Code:
                      [root @ beta-17] ~ # locate .link
                      /etc/systemd/network/eth0.link
                      /etc/systemd/network/eth1.link
                      /usr/lib/systemd/network/73-usb-net-by-mac.link
                      /usr/lib/systemd/network/99-default.link
                      /usr/share/man/man5/systemd.link.5.gz​
                      Code:
                      [root @ beta-17] ~ # cat /etc/systemd/network/eth0.link
                      
                      [Match]
                      MACAddress=2e:07:cf:f3:b7:2e
                      Driver=!bridge
                      Type=!vlan
                      
                      [Link]
                      NamePolicy=
                      Name=eth0
                      
                      ​
                      Code:
                      [root @ beta-17] ~ # cat /usr/lib/systemd/network/99-default.link
                      #  SPDX-License-Identifier: LGPL-2.1-or-later
                      #
                      #  This file is part of systemd.
                      #
                      #  systemd is free software; you can redistribute it and/or modify it
                      #  under the terms of the GNU Lesser General Public License as published by
                      #  the Free Software Foundation; either version 2.1 of the License, or
                      #  (at your option) any later version.
                      
                      [Match]
                      OriginalName=*
                      
                      [Link]
                      NamePolicy=keep kernel database onboard slot path
                      AlternativeNamesPolicy=database onboard slot path
                      MACAddressPolicy=persistent​
                      Not sure if you need more than the ethx files.

                      Good luck

                      Comment


                      • #26
                        Originally posted by LoneWolf View Post

                        My understanding is that we must do incremental upgrades if we are not on 16.6.2 to get to 17.0; so if we're on 16.5.2, we have to upgrade to 16.6.x in order to go to 17. Is that correct?
                        It is correct: there are no cumulative upgrades.
                        Græme Ravenscroft • Technical Marketing Engineer
                        ('gram', like the unit of measurement)
                        he/him
                        How can we make Arista ETM products better?

                        Comment


                        • #27
                          Originally posted by flynhawaiian View Post
                          Good to know. Wish there was a more advanced mode where you could check exactly what you wanted restored in the settings. Just provides a much more uniform restore method.
                          The backup file is a.gz of a .js file. You might be able to edit it at your own risk. LOL

                          Comment


                          • #28
                            Originally posted by donhwyo View Post

                            The backup file is a.gz of a .js file. You might be able to edit it at your own risk. LOL
                            Had to extract 5 layers, but I found the settings. Thanks!

                            Comment


                            • #29
                              Any update on when 17 will be out of beta?

                              Comment


                              • #30
                                Originally posted by hd908 View Post
                                Any update on when 17 will be out of beta?
                                It has been about two weeks. I would probably give them one or two more weeks. Think they are just verifying everything before a full rollout to avoid an immediate patch.

                                Comment

                                Working...
                                X
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎