Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 19 replies
  • Subscribers 47 subscribers
  • Views 77261 views
  • Users 0 members are here
Options
Suggested
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

Adding another NIC totally breaks XG Firewall and all dependent rules

Timothy Stewart

Hi.  I have been running XG firewall with 2 NICs - LAN and WAN.  I decided to add another for DMZ and it totally breaks the firewall.  All NICs get reassigned.  Port 1 LAN becomes DMZ, Port 2 WAN becomes LAN, and the newly added Port 2 becomes LAN instead of the unassigned DMZ.  This is crazy.  It wouldn't be so bad if it didn't break all of my rules the depend on Port 2 being WAN, which means when I reassign the new Port 3 to WAN the interface name changes and all business rules that depended on Port2_GW_DHCP get abandoned since this interface no longer exists.

Is this expected?  Is there a simple way to rename ports and reassign them to their old name, role, and position?  This seems like a major bug.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Timothy Stewart

    I also have this same issues, running XG in ESXi.  I had 3 NIC's configured at install but want to add a 4th NIC for a separate wireless network.  As soon as I add the 4th NIC and reboot the virtual appliance, I instantly lose access to any of the IP Networks configured in the XG.  I've tried randomly re-assigning the networks to each NIC so I can find the one thats now my new LAN adapter, but it doesn't work, I can never ping my internal LAN IP again.  I have to remove the 4th NIC and reboot again.  Once I do that, the XG comes up nicely like nothing ever happened.  Quite frustrating!  

  • 0 in reply to JoeChurch

    Hi folks,

    you can use the xg console in the VM to re-assign the IP addresses, that is one advantage of the VM in this situation.

    Ian,

    home UTM 9.x running in ESXi 6 e3-1275v2

    AP55c and AP10 (courtesy Astaro)

    Three other UTMs, SUM and SFM in hibernation

    XG 15.x MR3 in hibernation

  • 0 in reply to IanMorehouse

    But that doesn't help or change all of the existing rules that are assigned to NICs before the are reorderd.  See my first post.  This should probably be locked considering it is a known limitation/bug with the current release.  Hopefully v2 adresses this.

Unfiltered HTML