Release Notes

‍

4.14

‍

New statistics per subscriber groups (Status->Subscribers->Subscriber_Groups).Subscriber groups defined from GUI or REST API.

Throughput statistics now with L3/L4 breakdown in Statistics->Throughput->Overview.Previous overview now in Statistics->Throughput->Optimization).

Time and Volume quota management in Status->Subscribers->Quotas(in addition to existing REST API).

New Status->Subscribers->Attributes, withbetter information, replacing old Status->Radius/REST/Billing->Subscribers.

Better Status->Policies (Flow, Rate, Monitoring),with better information, replacing old Status->Radius/REST/Billing->Policiesand Status->Policies.

Flow details with DPI domains in Status->Flows->Details,replacing Status->Flows->Per Subscriber.

System logs from GUI.

Node DPI information is available via REST API.

General disabling of shaping and in Configuration->OptimizationSettings.

New software bypass in Configuration->OptimizationSettings.

Automatic detection of DPDK/PCAP interface mode in installationconfiguration wizard.

4.13

‍

Export feature to write table content to a csv file.

HTTP redirection when quota exhausted.

New REST API node metrics:

• Traffic volume
• Flows
• Latency
• Retransmissions
• Congestion
• Traffic at maximum speed.

Detailed network interface information.

‍

4.12

‍

Integration with Visp.net billing system.

RADIUS Connect-Info support (from 4.12.3).

‍

4.11

‍

Enforcement of time and/or volume subscriber quotas through the REST API.

From 4.11.3,  policy flow options to define traffic types not subject to quotas and to decide behavior when quota exhausted (blocking or slow down speed).

Metrics of congestion and traffic near top speed through the REST API.

Subscriber status table includes a warning counter of KPIs exceeding their threshold, to facilitate focusing on subscribers experiencing quality issues.

New TCPO Statistics over time, with an overall acceleration value and simpler charts.

TCPO Speed & Acceleration Status can now be calculated over up to one week.

‍

4.10

‍

The Subscriber Dashboard can now be requested by either IP Address or subscriber ID.

The DPI statistics can now be filtered by either IP Address or subscriber ID.

The main clients for each service can now be shown by either IP Address or subscriber ID.

The top subscribers by volume can now be shown by either IP Address or subscriber ID.

The latency per service graphs have been extended to 1 month (instead of just three days).

New dashboard alarms for NTP and forBilling Systems Synchronization.

DPI now detects IMAP, POP and SMTP overSSL/TLS.

‍

4.9

Improved Automatic Congestion Management.

Support for policy selection through Radius Class AVP

Support for IPv6 subscriber addresses in REST interface

‍

4.8

New subscriber monitoring page in Status->Subscribers (Statistics->Subscribers->Metrics deprecated).

DPI statistics of up to one month.

New Powercode integration with better performance.

Integration with Sonar billing system (v2)

‍

4.7

Subscriber ID searchable in GUI

Integration with Splynx billing system

Subscriber dashboard window

SNMP configuration

‍

4.6

TCPO Acceleration metrics per service/application

DNS for Powercode & Azotel integration

New Bequant logo in GUI

Azotel: block subscribers without a valid subscription (from 4.6.3).

Faster TCPO metrics (from 4.6.3).

Improved shaping, including improved FQ-CODEL (from 4.6.3).

‍

4.5

Azotel billing integration.

Histograms with main client/server IP addresses per service.

Modal charts in Subscriber metrics.

Multiple Powercode equipment categories (from 4.5.2).

ACM enabled for billing dynamic policies (from 4.5.2).

XBox software update DPI signature (from 4.5.2).

‍

4.4

New Automatic Congestion Management, based on advanced machine-learning algorithms, to automatically detect congestion situations and, in those case, apply a dynamic limit to mitigate the latency and packet losses caused by the congestion.

New Time Profiles, to allow specifying subscriber flow and rate policies as a function of the day-of-week and the time-of-day

Integration with Powercode billing systems

Integration with Cisco qos-policy RADIUS AVPs

‍

4.3

Shaping policies per flow: it is now possible to set a limit per flow, in addition to existing combined limit to all flows of the same subscriber. Applicable to scenarios with NAT.

Sortable data tables more scalable.

In DPI Service Analysis, possibility to exclude DPI samples generated by monitoring policies (to eliminate biases caused by those policies, for example, because of full DPI of specific IPs).

4.3.3

Fixes the issue of slow speeds when doing shaping or rate-limiting when turning off overall TCPO.

‍

4.2

Sortable data tables in:

• Status->Flows->Per Subscriber
• Status->Radius/REST->Subscribers
• Status->Subscribers
• Status->Policies
• Statistics->Subscribers->Metrics

Administration->General settings

• Host name
• IPv6 prefix for subscribers
• UDR production rate

‍

4.1

Speedtest DPI identification.

Latency per service charts.

Automatic UDR rate production.

Subscriber metrics available via REST API.

‍

4.0.25

Corrections.

4.0.24

Corrections.

4.0.23

Rate-policy profile, to define policy flow rules based on the name of the policy rate of the subscriber.

RADIUS Ascend AVPs supported (data-rate and xmit-rate).

In policy flows, drop rules for Internet-incoming SYN, UDP and IP other flows.

TCP improvements.

4.0.22

Up to 3 months of Subscriber metrics (usage, latency,retransmission, max speed, flows).

Dynamic policy rate creation from RADIUS.

Overall retransmission metrics.

PPS in Dashboard.

TCP improvements.

Niagara bypass.

4.0.21

Corrections.

4.0.20

Support of 25 Gbps and 100Gbps with Intel E810 network interfaces.

Better management of REST/API policies and subscribers.

Access to subscriber status and usage from subscriber tables.

DPI for QUIC-IETF and QUIC-vQ050.

DPI for Bittorrent.

Load a policy configuration respecting the server specific configuration (to load the same policies to several BQN servers).

RADIUS client description field.

Automatic Congestion Detection (ML).

4.0.19

Corrections.

4.0.18

Show API policies in GUI.

Show subscriber API policy assignments in GUI.

More graphical dashboard.

4.0.17

Subscriber usage of up to three months.

4.0.16

Corrections.

4.0.15

Status Flow per Subscriber introduced.

Status Subscribers much improved.

Cambium platform.

4.0.14

Traffic counter improvements.

Burst transition duration.

Corrections.

4.0.13

New Dashboard, with more information and more frequent updates.

Improved TCP.

4.0.12

Corrections.

4.0.11

REST API includes subscriber and policy IDs.

More IPs in OAM firewall.

4.0.10

Renovated system alarms.

SNMP traps.

New MIB.

Clearer DoS over time chart.

4.0.9

API Rest can specify rate policy parameters.

4.0.8

Centralized DoS thresholds.

4.0.7

Configuration backup/restore.

4.0.6

UDR generation in Subscriber monitor policy.

Tracking flows can be subject to shaping.

4.0.5

API REST

Subscribers and flows per Policy (Status->Policies).

Subscribers per Policy over time(Status->Subscribers->Per Policy).

Flows per policy over time (Statistics->Flows->Per Policy).

‍

Release Naming Conventions

BQN software release is identified by three digits (e.g., R4.1.1):

• The first digit indicates a mayor release (e.g., Release 4). A major release requires new platform packages (normally it is not compatible with platform packages from previous major releases).
• The second digit indicates a minor release within the major release (e.g., Release 4.1). Contains new functionality and it is compatible with the platform packages of its major release. Simply involves the installation of a BQN package.
• The third digit is a patch number, delivering corrections of the minor release. This is the convention from R4.1 onwards (R4.0 was delivering also functionality using the third digit).

‍

‍