XML Import for Internetv4 Objects

Disclaimer: This information is provided as-is for the benefit of the Community. Please contact Sophos Professional Services if you require assistance with your specific environment.

Overview

This Recommended Read highlights how to Import via XML Intervnetv4 objects.

We have a KBA to create an Internetv4 Object in our KB: https://support.sophos.com/support/s/article/KB-000037154?language=en_US 

This KB uses a smaller script to create the objects via CLI. 

These object(s) are used to define the WAN in general. Uses cases like SD-WAN Policy-based Routes or NAT are possible.

If you do not want to create the object via script, you can use the XML Export in this thread. 

Using XML 

Simply download the .zip. (Located at the bottom of this RR)  Unzip it once (you should get a .tar) and upload the .tar to the SFOS Appliance in Backup & Firmware - Import Export.

Case Example

One example of the use case in PBR:

XML File

:Internetv4_version2.zip



Updated Disclaimer
[edited by: Erick Jan at 10:28 AM (GMT -7) on 17 Apr 2023]

Top Replies

  • That's great, thanks LuCar Toni

    I enhanced the object a little bit, as 2 of the non routeable RFC5737 networks 198.51.100.0/24 und 203.0.113.0/24 are not included (or more exactly excluded) in the internet v4 object. I for example use those ranges in my internal lab network for documentation reasons (as a 203.x.x.x IP looks more "real" or "public" for a WAN Interface IP address address than a 172.x.x.x for example). So I attach the slightly modified "IPv4Internet_excl_RFC5737" object here. Feel free to use LuCar Toni's version or that one. As most likely 99,xxx% of the people anyway doesn't use those RFC5737 ranges, it won't make any noticeable difference anyway.

    Same instruction as above - first extract the .tar out of the .zip file and import in in your Sophos Firewall.

    stage-community-sophos-comv11.telligenthosting.net/.../IPv4Internet_5F00_excl_5F00_RFC5737_5F00_v2_5F00_2.zip

    Update 2021-08-26: Updated Object XML API Version Header to support import into SFOS v17.x onwards

    Jump to answer
Parents Reply
  • Just FYI: There is a general problem in V18.5 MR2 and V19.0 EAP1, preventing this import. Objects already imported in a previous version are 100% functional. This is fixed in the upcoming Releases (V18.5 MR3 // V19.0 EAP2). 

    __________________________________________________________________________________________________________________

Children
No Data