---
title: Network-Level Configuration
description: Use Network Manager to configure the management interface. Preseem manages the traffic interfaces. When changing the management IP address, edit only its management connection profile.
---

[Skip to content](https://docs.preseem.com/configuration/config#main-content)

English

Show submenu for translations

[![Preseem Logo Classic](https://docs.preseem.com/hs-fs/hubfs/Preseem%20Logo%20Classic.png?width=150&height=38&name=Preseem%20Logo%20Classic.png)](https://app.preseem.com)

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)

Open main navigation

Close main navigation

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)
- English
  
  Show submenu for translations
- Contact us

 Contact us

 Hi There! How Can We Help You?

- There are no suggestions because the search field is empty.

1. [Help Center](https://docs.preseem.com/?hsLang=en)
2. [Configuration](https://docs.preseem.com/configuration?hsLang=en)

# Network-Level Configuration

**Interface and IP Addressing**

Use Network Manager to configure the management interface. Preseem manages the traffic interfaces. When changing the management IP address, edit only its management connection profile.

The management port and default address depend on the appliance model and hardware revision. Check the table below against your appliance. If the port uses DHCP, find its assigned address in the DHCP lease records or from the console.

| **Model** | **Management Port(s)** |
| --- | --- |
| Preseem 1000 | Port 1 enp1s0 (DHCP), Port 2 enp2s0 (192.168.2.1) |
| Preseem 5000 | Port 1 enp4s0 (DHCP), Port 2 enp5s0 (192.168.2.1) |
| Preseem 10000 | enp8s0 (DHCP); Port 1 enp2s0f0 (192.168.2.1); Port 2 enp2s0f1 (192.168.3.1) |
| Preseem 20000 | enp1s0 (DHCP); Port 2 enp105s0f0 SFP/SFP+ (192.168.2.1) |
| Preseem 15K | eno1 (DHCP) |
| Preseem 40K | enp1s0 (DHCP) |

### **Set a Static IPv4 Address**

First, obtain an unused IP address, prefix length, gateway, and DNS server. Keep console access available in case the change disconnects SSH. These steps apply to an existing management connection and do not change data ports or IPv6 settings.

1. List active connections and use the DEVICE column to identify the management port. The connection name may differ from the interface name. If the profile is not listed, run nmcli connection show to include inactive profiles before continuing:
   
   ```
   nmcli connection show --active
   ```
2. Open the management connection in the interactive editor:
   
   ```
   sudo nmcli connection edit "<connection-name>"
   ```
3. At the nmcli prompt, display and record the current IPv4 settings:
   
   ```
   print ipv4
   ```
4. Enter the following commands one at a time, replacing the placeholders. If prompted to switch to manual addressing after entering the address, answer yes.
   
   ```
   set ipv4.addresses <IP/CIDR>set ipv4.method manualset ipv4.gateway <gateway-IP>set ipv4.dns <DNS-IP>
   ```
5. Enable automatic connection at startup: 
   
   ```
   set connection.autoconnect yes 
   ```
6. Check the values, save, and activate the connection. Enter each command separately. Activation may disconnect SSH. If it does, reconnect using the new address and continue with the checks in the next step. 
   
   ```
   print ipv4saveactivatequit
   ```
7. After reconnecting, check the address, default route, and DNS resolution:  
   
   ```
   nmcli device show "<management-interface>"ip -4 route show defaultgetent ahosts docs.preseem.com
   ```

Check that the interface has the intended IPv4 address, gateway, and DNS servers, that the default route is correct, and that docs.preseem.com resolves. Open a new SSH session to the management address from your workstation.

If a check fails, use the console to compare the connection with the settings you recorded. Correct the settings, reactivate the connection, and confirm that a new SSH session succeeds.

**Securing Access**  
Restrict management access to your management network and Preseem’s support IPs where needed. If the appliance uses a private address, check routing, NAT, and ACLs with your network administrator. See Firewall Configuration below for more guidance.

**Support and Cloud Integration Access**

Please refer to Section 4: [Management and Cloud Access](https://docs.google.com/document/d/1OmO43G4XA8CrXcxm7qrE632he2ezaI3PelPZbagf3GU/edit?tab=t.0#heading=h.ilklch21ytq9)

**MTU**

The MTU limit applies across the complete inline traffic path. The traffic bridge and all member interfaces must be configured with the same supported MTU value.

**Preseem V1**  
Preseem V1 supports a maximum MTU of 9216 bytes. By default, bridge interfaces are pre-configured with an MTU of 1500 bytes. A custom MTU size of 9216 bytes is supported.

**Preseem V2**  
Preseem V2 currently supports a maximum MTU of 2048 bytes. Preseem V2 does not support 9000-byte jumbo frames, and it does not support a custom MTU size \>2048.

**VLANs**

Preseem inspects and reports traffic on all supported VLANs by default. No per-VLAN configuration is required. Before altering or changing your VLAN configuration, please contact Preseem Support.

**Supported VLANs**  
Preseem inspects and reports traffic across all supported VLAN types by default, with no per-VLAN configuration required. Preseem V1 and Preseem V2 have differences in level of VLAN support, please see below for more information.

- **Single 802.1Q tag:** Supported in V1 and V2.
- **802.1ad QinQ in V1:** Limited support for an outer 802.1ad service tag and inner 802.1Q customer tag, with two tags maximum.
- **Stacked 802.1Q in V1:** Two 802.1Q tags are not supported for inspection.
- **Double-tagged traffic in V2:** Requires Preseem V2.2 or later and an Intel E810-series NIC. Intel 710-series NICs are not supported.

**Adding a Bridge (Expansion Cards / New NICs)**

Please contact Preseem Support if you plan to add additional network cards or add bridges.

- [Preseem Overview](https://docs.preseem.com/preseem-overview?hsLang=en#main-content)

    - [Deployment Models](https://docs.preseem.com/preseem-overview?hsLang=en#deployment-models)
- [Preseem Hardware](https://docs.preseem.com/preseem-hardware?hsLang=en#main-content)

    - [Legacy Hardware](https://docs.preseem.com/preseem-hardware?hsLang=en#legacy-hardware)
- [Installation & Activation](https://docs.preseem.com/installation-activation?hsLang=en)
- [Configuration](https://docs.preseem.com/configuration?hsLang=en)
- [Using Preseem](https://docs.preseem.com/using-preseem?hsLang=en#main-content)

    - [How to Use Preseem to Troubleshoot Subscriber Issues](https://docs.preseem.com/using-preseem?hsLang=en#how-to-use-preseem-to-troubleshoot-subscriber-issues)
    - [Operations](https://docs.preseem.com/using-preseem?hsLang=en#operations)
    - [How to Use Preseem to Optimize QoE](https://docs.preseem.com/using-preseem?hsLang=en#how-to-use-preseem-to-optimize-qoe)
    - [Preseem's RF Scoring and Metrics](https://docs.preseem.com/using-preseem?hsLang=en#preseems-rf-scoring-and-metrics)
- [Administering Preseem](https://docs.preseem.com/administering-preseem?hsLang=en#main-content)

    - [Upgrades](https://docs.preseem.com/administering-preseem?hsLang=en#upgrades)
    - [Planning and Configuration](https://docs.preseem.com/administering-preseem?hsLang=en#planning-and-configuration)
    - [Troubleshooting](https://docs.preseem.com/administering-preseem?hsLang=en#troubleshooting)
    - [User Management](https://docs.preseem.com/administering-preseem?hsLang=en#user-management)
- [Integrations](https://docs.preseem.com/integrations?hsLang=en)
- [FAQs and Other Explanations](https://docs.preseem.com/faqs-and-other-explanations?hsLang=en)
- [Amplify AI - Support Assistant](https://docs.preseem.com/amplify-ai-support-assistant?hsLang=en)

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)

[![Chill listening crop-3](https://docs.preseem.com/hs-fs/hubfs/Preseem_logo_large.png?width=80&height=30&name=Preseem_logo_large.png "Chill listening crop-3")](https://preseem.com/)

Copyright © 2026, Preseem (Aterlo Networks)