I've solved the issue by using a different test mesh node Form join.fips.network. The US node was always rejecting connection attempts. I'm connected now 🙌

Hey I'm trying to connect to the fips test mesh but I'm currently stuck at connecting to the test-us01 peer. I've tried UDP and TCP. My node is using a rfc1918 address and is natted behind a Firewall. In a tcpdump I see that there is no reply to UDP packets and with TCP they are getting resetted directly after the initial TCP handshake. (For UDP I've forwarded port 2121 on my Firewall and there is no block) When checking fipsctl show connections that the handshake_state is "sent_msg1". Is the test-us01 peer currently up and running?

$ sudo fipsctl show connections { "connections": [ { "direction": "outbound", "expected_peer": "", "handshake_state": "sent_msg1", "idle_ms": 1741, "link_id": 1, "resend_count": 1, "started_at_ms": 1779981188560 } ] }

- OS: Ubuntu 22.04 - fips: 0.4.0-dev Daemon looks good: Mai 28 17:13:08 enjOYD systemd[1]: Started FIPS Mesh Network Daemon. Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.418385Z INFO fips: FIPS 0.4.0-dev (rev 2809f0351e) starting Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.418400Z INFO fips: Loaded config file path=/etc/fips/fips.yaml Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.418688Z INFO fips: Loaded persistent identity from key file path=/etc/fips/fips.key Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419150Z INFO fips::upper::hosts: Loaded hosts file path=/etc/fips/hosts count=8 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419365Z INFO fips::upper::hosts: Loaded hosts file path=/etc/fips/hosts count=8 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419414Z INFO fips: Node created: Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419421Z INFO fips: npub: Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419432Z INFO fips: node_addr: c5de878088f033cd8c2523323be32898 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419436Z INFO fips: address: fdc5:de87:8088:f033:cd8c:2523:323b:e328 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419440Z INFO fips: state: created Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419443Z INFO fips: leaf_only: false Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419501Z INFO fips::transport::udp: UDP transport started local_addr=0.0.0.0:2121 recv_buf=4194304 send_buf=4194304 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419530Z INFO fips::transport::tcp: TCP transport started local_addr=Some(0.0.0.0:8443) mtu=1400 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.419536Z INFO fips::node::lifecycle: Transports initialized count=2 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.429768Z INFO fips::node::lifecycle: Spawned FMP-encrypt worker pool workers=20 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.559122Z INFO fips::node::lifecycle: Spawned FMP-decrypt worker pool workers=20 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.560079Z INFO fips::node::lifecycle: Nostr overlay discovery enabled Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.560402Z INFO fips::discovery::nostr::runtime: nostr notify loop entered Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579251Z INFO fips::node::lifecycle: TUN device active: Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579257Z INFO fips::node::lifecycle: name: fips0 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579259Z INFO fips::node::lifecycle: address: fdc5:de87:8088:f033:cd8c:2523:323b:e328 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579262Z INFO fips::node::lifecycle: mtu: 1280 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579264Z INFO fips::node::lifecycle: effective MTU: 1203 bytes Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579433Z INFO fips::upper::hosts: Loaded hosts file path=/etc/fips/hosts count=8 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579447Z INFO fips::node::lifecycle: DNS responder started for .fips domain (auto-reload enabled) bind=[::1]:5354 hosts=8 mesh_ifindex=Some(90) Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579454Z INFO fips::node::lifecycle: Node started: Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579455Z INFO fips::node::lifecycle: state: running Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579457Z INFO fips::node::lifecycle: transports: 2 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579459Z INFO fips::node::lifecycle: connections: 1 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579461Z INFO fips: FIPS running Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579472Z INFO fips::node::handlers::rx_loop: RX event loop started Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.579550Z INFO fips::control::unix_impl: Control socket listening path=/run/fips/control.sock Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.680222Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://nos.lol' Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.725576Z INFO fips::discovery::nostr::runtime: nostr notify loop received first event elapsed_ms=165 Mai 28 17:13:08 enjOYD fips[2841642]: 2026-05-28T15:13:08.865028Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://relay.damus.io' Mai 28 17:13:09 enjOYD fips[2841642]: 2026-05-28T15:13:09.133390Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://offchain.pub' Mai 28 17:13:09 enjOYD fips[2841642]: 2026-05-28T15:13:09.244946Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://relay.damus.io msg=["EVENT","c6889b21c81b81ac1b0aa7d201f174a6",{"content":"{\"identifie> Mai 28 17:13:09 enjOYD fips[2841642]: 2026-05-28T15:13:09.485613Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://relay.damus.io msg=["EVENT","c6889b21c81b81ac1b0aa7d201f174a6",{"content":"{\"identifie