NetBird Peer Connectivity Issues in Mojaloop Deployment #531
Description
Issue Description
NetBird mesh network experiencing partial connectivity where some peers connect successfully while others remain stuck in "Connecting" state indefinitely.
Current Status
Management/Signal: ✅ Connected to both servers
Relays: ✅ 2/3 Available (fixed after service restart)
Peer Connectivity: ❌ Only 1/4 peers successfully connected
Symptoms
No ICE Candidate Negotiation: Stuck peers show ICE candidate (Local/Remote): -/-
No WireGuard Handshakes: All stuck peers show Last WireGuard handshake: -
Stale Connection Updates: All stuck peers have identical old timestamps (12+ minutes)
No Relay Fallback: Despite relay servers being available
Network Environment
Mixed network topology with peers on different subnets (10.106.0.x, etc.)
Likely containerized/cloud deployment given hostnames
One peer (desktop) successfully establishing P2P connections
Troubleshooting Attempted
✅ Service restart (fixed relay connectivity)
✅ Verified relay server accessibility
✅ Confirmed management/signal server connectivity
❌ Unable to access remote peer machines for service status
Expected Behavior
All peers should establish either P2P or relay-based connections within a few minutes.
Questions for Mojaloop Team
Are there specific firewall rules or security groups that need to be configured for NetBird in Mojaloop deployments?
Should all peer machines have NetBird services restarted simultaneously after network changes?
Are there known issues with NetBird 0.52.1 in containerized Mojaloop environments?
What's the recommended approach for debugging NetBird connectivity issues across multiple Mojaloop nodes?