Networking — Info Tab

The Info tab is the live monitoring dashboard for the Networking section — connection status, bandwidth graphs, VPN and WAN-bundle quality, IP Shaping diagnostics, the IP Ban table and recent network events. It is read-only; everything you see here is configured on the Settings tab.

The full Networking Info page — Inside Network, IP Shaping, IP Ban, and Recent Events sections.
The full Networking Info page — Inside Network, IP Shaping, IP Ban and Recent Events sections.

The Info tab is divided into four sections, each in its own card. Let's walk through each one.


Inside Network

This section shows your LAN Connections. Click the expand arrow (▸) to open it. Three sub-tabs appear: Overview, ARP Monitor and SNMP Monitor.

Overview

LAN Connections — Overview tab showing three connections: LAN (green), WAN DHCP, and WAN ETHLTE.
LAN Connections — Overview tab showing three connections: LAN (green), WAN DHCP and WAN ETHLTE.

Each connection appears as a pill-shaped button with a status indicator:

Click on a connection to see its bandwidth statistics: Line Load (current and historical) and Top 5 (which devices/services use the most bandwidth). On a multi-path resource (AIPT2 tunnel or WAN bundle), the Select Paths dropdown next to the resource selector lets you overlay several paths on the same Line Load graph to compare them — see View traffic analysis.

ARP Monitor

Status-icon convention varies by panel. Connection cards on the Overview sub-tab use smiley faces; the ARP and SNMP Monitor tables use ✓/✗ ticks — same meaning, different visuals.
ARP Monitor tab — buttons for Poll Interval, New Host Alert, and New +.
ARP Monitor — Monitored tab showing devices with their status.

Monitors devices on your network using ARP (Address Resolution Protocol — how devices discover each other on a local network). The ARP Monitor has three sub-tabs:

Sub-tabWhat It Shows
MonitoredDevices you have chosen to watch (with status, history and editable entries). Columns are documented below.
All HostsEvery device the Abilis has seen on the network — whether you're monitoring it or not.
Unknown HostsDevices that appeared on the network but are not in your monitored list. Each unknown host has an Add To Monitor button so you can start watching it.

Columns on the Monitored sub-tab:

ColumnWhat It Shows
PortThe Abilis interface (e.g. Ip-1) where this device was last seen.
IP AddressThe device's current IP.
MAC AddressThe device's hardware address — the unique 48-bit identifier burned into its network card.
VendorManufacturer name, derived from the first three bytes of the MAC (the OUI prefix) looked up against the public IEEE vendor list. Blank or "Unknown" if the prefix isn't registered.
DescriptionFree-text label you set yourself.
State✓ = device is responding to ARP probes (up). ✗ = no response (down).
SinceHow long the device has been in its current state.
Max downTolerance window in seconds — how long the device may go silent before its State flips to ✗.

Three buttons at the top right:

New Host Alert Configuration — choose what happens when a new device is detected.
New Host Alert Configuration — choose what happens when a new device is detected.

The Alert Channel dropdown offers five options:

OptionWhat Happens
NoAlerts disabled.
1 - Sends e-mailAn email notification is sent to the configured address.
2 - Sends SMSAn SMS is sent (requires GSM/LTE hardware).
3 - Sends callAn automated phone call is made.
4 - Turns on DOActivates a digital output configured via Automation hardware — e.g. flashes an LED, triggers a relay or fires an external alarm.

Click Save to apply, or Cancel to close without saving.

SNMP Monitor

SNMP Monitor tab — service monitoring with state indicators.
SNMP Monitor — monitors services on network devices.

Monitors services on network devices using SNMP (Simple Network Management Protocol). Each entry shows:

Same Poll Interval and New + buttons as ARP Monitor.

VPN Connections

If your Abilis has VPN tunnels configured (connecting to other Abilis units or remote offices — see Networking How-To → Set up a VPN tunnel), this section shows their status in real time. Click the expand arrow (▸) next to VPN Connections to open it.

Three view modes are available:

VPN Connections — VPN matrix view showing colour-coded quality bars over time.
VPN Connections — VPN matrix showing connection quality over four time periods.
ViewWhat It Shows
VPN matrixColour-coded bars showing connection quality over time (5 seconds, last minute, last 15 minutes, last hour). This is the default and most useful view.
Map viewGeographic view of tunnel endpoints (if coordinates are configured).
List viewSimple text list of all tunnels with their status.

The colour legend for the VPN matrix:

ColourMeaning
Within norm — tunnel is working well
Fair — minor quality reduction
Less than fair — noticeable quality issues
Almost unusable — serious problems
Out of service — tunnel is down
Backup — backup tunnel (standby)
Inactive — tunnel is configured but not running
A healthy VPN should show solid green bars across all time periods. If you see yellow or red, the connection is degrading — check the internet quality on both sides.

Outside Network

Below the Inside Network panel, the Outside Network section shows the status of your WAN (internet-facing) connections — how the Abilis reaches the outside world.

WAN Bundles

Outside Network — WAN Bundles showing tunnel quality over time with colour-coded bars.
Outside Network — WAN Bundles showing tunnel quality over time with colour-coded bars and status icons.

A WAN Bundle groups up to six upstream transports — internet lines (DSL, fibre, LTE) and/or VPN tunnels that ride on top of them — into one logical link. The Abilis spreads traffic across them for extra bandwidth and fails over automatically when one degrades; underneath, this is its AIPT2 tunnel technology.

Each bundle row (e.g. "Tunnel to AWS…", "Tunnel to MIX") shows:

Click the expand arrow (▸) on a bundle to open its detail panel, then switch between two levels of detail with the Basic view / Advanced view toggle:

ViewWhat It Shows
Basic viewOne quality bar per line — a quick Good/Fair/Poor read of each line across time. Best for spotting when and where a problem struck.
Advanced viewThe full diagnostic: each line split into Upload and Download, every column coloured by which impairment is biting, plus per-direction bandwidth figures and the editable preferred treatment type.
WAN bundle Tunnel to MIX in Advanced view — six lines each with Upload and Download quality graphs, a preferred treatment type dropdown and an Overall strip with a Bad-to-Good scale.
Advanced view of the Tunnel to MIX bundle — each line shows separate Upload and Download quality, the preferred treatment type sits top-left and the Overall strip at the bottom combines them all.

Reading the timeline. Each line gets its own strip, split into an Upload half (above the centre line) and a Download half (below it). Time runs left to right — from about ninety minutes ago on the left to Now on the right. Every coloured column is one measurement: its colour tells you which problem occurred and its height tells you how bad it was at that instant. The centre line is the healthy baseline; the taller a column grows away from it, the worse the quality at that moment — the same scale the Overall strip prints along its edge (Good in the middle, then Fair, Poor and Bad toward the top and bottom). A healthy line hugs the centre as a thin flat trace; a struggling line sprouts tall coloured spikes. Because Upload and Download are drawn separately, you can tell at a glance whether a problem is hitting one direction or both.

Close-up of a WAN-bundle quality strip — short yellow congestion bars, then a tall cluster of blue, red and yellow spikes, then calm again.
Close-up of one line's timeline — a calm stretch of low yellow bars, then a burst where tall blue, red and yellow spikes pile up (jitter, lost packets and congestion at once), then a return to calm. The taller the spike, the worse that moment.

The colour legend has two kinds of entry. The first four are impairments — coloured spikes on a line that is still working, each naming the problem that hit at that moment:

ColourMeaning
Lost Packets — packets that never arrived and had to be resent
Line Congestion — the line is running close to its bandwidth limit
Jitter — uneven gaps between arriving packets
Trip time delayed — the round trip is taking longer than usual

The last three are whole-line states — a solid band that fills the strip when a line stops carrying normal traffic, rather than a per-moment spike:

ColourMeaning
Inactive — configured but not in use, like a standby backup
Local Fault — the line is down because of a fault on your side of the link
Network Error — the line is down because of a fault further out in the provider's network
Treatment types are QoS traffic classes. Networking theory rates every link on four things — lost packets, delay, jitter and available throughput — and treats each kind of traffic by whichever matters most to it: a phone call needs low delay and few drops, while a video stream mainly wants bandwidth and tolerates a more congested, slower path. Choosing a treatment type is how you tell the bundle which of those four to weigh most heavily, line by line.

By default a bundle simply balances the load. The preferred treatment type dropdown lets you single out one kind of traffic and route it, line by line, onto whichever line scores best on the metric that matters most to it. Pick a type and click Save. Hovering an option pops up Abilis's own one-line explanation of what it optimises — the same logic the table below spells out.

The preferred treatment type dropdown open, showing None, VPN, VoIP, Surfing and Streaming.
The preferred treatment type dropdown — None, VPN, VoIP, Surfing or Streaming.
TypeBest forHow it picks a line
Noneeverything (default)No preference — spreads traffic evenly to balance the load across all lines.
VoIPphone callsThe line with the fewest lost packets, least jitter and lowest delay — and it sends a backup copy on the second-best line, so one dropout can't break the call. Weighs lost packets 40%, jitter 33%, trip time 27%.
VPNinteractive work — remote desktop, video calls, online gamesThe most responsive line: delay first, then spare bandwidth, then jitter and loss. Weighs trip time 33%, throughput 28%, jitter 22%, lost packets 17%.
StreamingvideoThe line with the most spare bandwidth, so the picture holds its bitrate; delay and jitter are ignored because the player buffers. Weighs throughput 67%, lost packets 33%.
Surfingweb browsing, email and downloadsThe most reliable line (fewest lost packets), so pages and files don't stall on resends; delay and jitter are ignored. Weighs lost packets 62%, throughput 38%.
This dropdown is the one editable control on an otherwise read-only Info tab. The preference lives on the client end of the tunnel — the side that sends the traffic — so set it there, not on the far Abilis.

The Overall row at the bottom blends every line into the bundle's combined health and is the one strip that prints the quality scale on its edge — Good at the centre, then Fair, Poor and Bad toward the top and bottom. The lines above carry their own resource names (e.g. Ip-242 FTTC_TIM, Ip-240 FTTC_80…) with a "+" icon you can click for per-line details.

If a single line shows intermittent yellow or red but the Overall bar stays green, the bundle is doing its job — traffic is being routed around the weaker line.

IP Shaping

IP Shaping limits the speed of "bandwidth-hungry" traffic so that other users get a fair share of the connection. It targets steady high-volume flows (a download, a backup) and leaves bursty human traffic alone (web browsing, email). The GUI describes it as: "IP Shaping aims to reduce the priority of traffic recognised as existing between two 'machines', in order to give higher priority to the work of humans."

When no traffic is currently being shaped, you will see: "No IP Shaping active at the moment".

When traffic IS being shaped, a Diagnostics section appears showing which connections are being throttled, with real-time graphs comparing actual usage to the allowed limits.


IP Ban

The Abilis automatically blocks IP addresses that make too many failed login attempts (brute-force protection). The banner reads: "Banned 0 attackers responsible for 0 malicious trials" (the numbers update in real time).

Click the expand arrow (▸) to see the ban list and the Unban Addresses button. Click Preferences to configure the banning behaviour:

IP Ban section expanded — showing the Unban Addresses button and Preferences panel with all configurable fields.
IP Ban section expanded — showing the Unban Addresses button and Preferences panel with all configurable fields.

The Preferences panel shows:

SettingDefaultWhat It Controls
Ban hosts after10 unsuccessful trialsHow many failed login attempts trigger a ban.
Within an interval of1440 minutes (24 hours)The time window in which those attempts must occur.
Ban hosts for10080 minutes (7 days)How long the ban lasts.
Send an alert if the table capacity reaches 80%☐ (off)Warns you if the ban list is getting full.
Ban table capacity3000Maximum number of banned IPs.
Changing "Ban table capacity" requires a reboot — the rest of these fields apply on Save. Plan the change for outside business hours.
You can also customise these values per attacked port (e.g. stricter rules for SSH than for HTTPS) and maintain a whitelist of IP addresses that bypass IP Ban entirely. Both are CLI-only — see the v9.0 reference manual under keyword IPBAN preferences.

Click Save and apply all changes or Close.


Recent Events

Recent Events log — a chronological list of network status changes.
Recent Events log — a chronological list of network status changes.

A chronological feed of the latest network status changes. Each row shows:

If you see repeated "is initializing... / is ready" cycles in quick succession, the network interface may be unstable — check the physical cable connection.
Anteklab Technical Support Email: tem@antek.it
Tel: +39 0376 16262,27