IPv6 Configuration of PortaSwitch

Add native IPv6 support across the full PortaSwitch stack — not just PortaSIP signaling (already partially covered since MR58 via DNS64/NAT64 translation) — so that PortaBilling's BillingEngine (RADIUS nodes/NAS, Diameter Gy/Ro, broadband NetAccess) and PortaConfigurator (node/VIPA binding) can authorize, rate, and bill sessions that arrive over IPv6-only or dual-stack networks, with no dependency on NAT64/CGNAT translation layers.

Currently, neither PortaBilling nor PortaSIP natively support IPv6 except the following 2 options:

• PortaConfigurator since MR62 (FR-50) - provides an ability for the user to assign/modify IPv6 address(es) to/on network interface only
• and we also have NAT64 support on PortaSIP side since MR58 (external IPv6-to-IPv4 conversion with IPv6 sip signalling support on PortaSIP components side).

• CSPs 
  • Mobile operators (4G/5G), ISPs, MVNOs
  • Especially those moving to IPv6-only cores (common in 5G)

• Internal operator teams

  • Network engineering (core, IMS, packet core)
  • Billing / revenue assurance
  • IT / DevOps / security teams

• End subscribers (indirectly)

  • Mobile users on IPv6-only networks
  • IoT devices at massive scale
  • Enterprise customers needing modern connectivity

• Future-proofing the network
  • IPv4 exhaustion is already a reality. IPv6 is not optional long-term
• Cost reduction as IPv4 forces operators into expensive workarounds like carrier-grade NAT (Carrier-Grade NAT) infrastructure, logging overhead (legal compliance for NAT mappings), performance bottlenecks while with IPv6:
  • Less NAT → simpler architecture
  • Lower infrastructure and operational cost
  • Reduced logging complexity

• New revenue streams (especially IoT) as IPv6 can potentially unlock:

  • Massive IoT deployments (millions of devices with public IPs)
  • Enterprise VPN / private networking services
  • Smart city / automotive / industrial use cases

• Better service quality & simpler troubleshooting

  • No NAT traversal issues (fewer broken VoIP/video sessions)

• Regulatory & ecosystem alignment

  • Many regions mandate or strongly encourage IPv6 adoption
  • Device ecosystems (Android/iOS) already assume IPv6 availability
  • Roaming partners increasingly expect IPv6 compatibility