Network interfaces (IP1/IP2)PRO
Roles and configuration of IP1, IP2 and additional interfaces.
Overview
IP1 and IP2 provide flexibility for separation of production traffic, management, redundancy and bonding.
Roles
| Interface | Default Role | Typical Use |
|---|---|---|
| IP1 | Primary Internet / streaming | Outbound video, ISS, upgrades |
| IP2 | Management (LAN) | Local config access, ISS path, secondary/backup uplink |
Management Mode (IP2)
When IP2 is in management mode the unit acts like a small router (IP1=WAN, IP2=LAN). Do NOT connect IP2 to a corporate LAN in this mode to avoid DHCP conflicts.
Failover & Bonding
- Failover: Unit sends on first working interface; if loss detected switches within seconds to next (Stream continues if Bifrost; TCP sessions may re-buffer).
- Bonding (Bifrost): Aggregates bandwidth from multiple interfaces (e.g., dual LTE + fiber) for capacity & redundancy.
Internet Availability Tests
Every 10 s an offline interface probes sequentially:
- iss.intinor.se:22017
- iss.intinor.se:80
- 8.8.8.8:53 If any succeeds interface considered online.
Static vs Dynamic
- Static: Predictable addressing for firewall/NAT pinholes.
- Dynamic (DHCP): Faster deployment; use DHCP reservation for consistency.
Additional Interfaces
Optional wired/wireless NICs can extend bonding sets. Treat each as candidate path for Bifrost or failover pool.