Skip to content

Suite4 modules

Access & Network

Connect and authorise every session

Terminate PPPoE subscribers on a DPDK-based gateway, decide access and speed in RADIUS AAA and keep the IP logs that lawful lookups depend on. Each layer speaks standard RADIUS to the next.

Live sessionsIllustrative
SubscriberAccessGatewayIPStatus
FTTH-44120PPPoEbng-01100.64.18.23Authorised
FTTH-51877PPPoEbng-02100.64.22.140Authorised
ENT-2209IPoEbng-01203.0.113.14Authorised
WIFI-GUEST-88Hotspotap-lobby10.20.4.77Captive portal
FTTH-39002PPPoEbng-02–Rejected: expired plan

4 authorised · 1 rejectedIP logs retained · Trace

About Access & Network

Access & Network is the part of i2iCore that sits between a subscriber and the internet. It is RADIUS AAA and BNG software with a captive-portal platform for public Wi-Fi and an IP log store for carrier-grade NAT. Network engineers and NOC teams use it to decide who may connect, what speed each session gets and what evidence the operator keeps afterwards.

i2i AAA is the RADIUS server. It authenticates and authorises each session, records accounting and can disconnect or re-shape a live session. i2i BNG terminates PPPoE subscribers on standard x86 servers, applies the speed the plan calls for and runs carrier-grade NAT. i2i Hotspot adds captive portals, plans and vouchers for venue Wi-Fi, while authentication stays in your AAA.

i2i Trace is the log management module for compliance teams. It collects NAT flow records and router syslog, holds them for the retention period your regulator sets and answers which public IP address and port was in use at a given time. Each module has its own page and console, so you can start with the one that solves today's problem.

What you get done

RADIUS AAA, a software BNG, Wi-Fi portals and IP logs for every subscriber session.

  • Access decided by plan, status and policy, then accounted for
  • CGNAT with NAT event logs on standard x86 servers
  • Captive portals and vouchers for public Wi-Fi
  • IP logs mediated and kept for the period you set

Better together

How the Access & Network modules work together

  1. Authenticate at the gateway

    A subscriber logs in over PPPoE on i2i BNG, which sends the request to i2i AAA as RADIUS. AAA checks the subscriber record and returns the plan speed, and later changes to a live session are sent as CoA.

  2. Write usage into billing

    i2i AAA records the Start, Interim and Stop accounting stream and writes usage into the i2i billing schema, with a daily usage roll-up. Accounting therefore reaches invoicing without a separate export step.

  3. Run public Wi-Fi on the same AAA

    i2i Hotspot supplies the portal, plans and vouchers for guests. RADIUS authentication stays in your AAA server, such as i2i AAA, which runs the Wi-Fi authorise and accounting steps and tracks the sessions.

  4. Keep the NAT records

    i2i BNG can send NAT events as syslog or IPFIX to a log store such as i2i Trace. Trace keeps them under the active compliance profile and answers lookups by public IP, port and time.

FAQ

Access & Network: frequently asked questions

Do I need all four modules to get value?

No. Each module has its own page and console. i2i AAA works with i2i BNG and i2i Hotspot as RADIUS clients, and i2i BNG speaks standard RADIUS, You can start with the module that answers your most pressing need and add the others later.

Does i2i Hotspot replace my AAA server?

No. Hotspot supplies the captive portal, subscriber, plan and voucher data and the management screens. RADIUS authentication stays in your AAA server, such as i2i AAA, and Hotspot reads or receives session and accounting data from that side.

Can i2i Trace tell me which subscriber used an IP address?

Trace answers which public address and port was in use at a given time and exports the record as evidence. It does not map an address to a subscriber itself. That step uses your own subscriber or RADIUS data, and the operator matches the private address against it.

Which authentication methods does i2i AAA support?

PAP and CHAP, MS-CHAPv2 in the RADIUS layer, and EAP-TLS, EAP-TTLS and EAP-PEAP for 802.1X networks. For EAP-TLS you load the issuing certificate authorities into the Trust Anchors screen, so only clients whose certificates chain to a trusted root are admitted.

What does i2i BNG run on?

Standard x86 servers under Debian, with a customised VPP forwarding engine and DPDK network drivers, so there is no proprietary hardware to buy. Capacity grows by adding another node. Its command line supports set, show, commit and rollback, and it also has a web interface, SNMP and Prometheus metrics.

Can subscriber speed change without a new login?

Yes. Both i2i AAA and i2i BNG handle CoA and Disconnect. Support can change a speed when a customer upgrades, and a time-of-day policy can send CoA to running sessions when a schedule changes, so the subscriber does not need to reconnect.