Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

About:dropped a packet with seemingly encrypted header for which no matching community which uses encrypted headers was found. #63

Open
guest3963 opened this issue Jan 24, 2025 · 3 comments
Open

About:dropped a packet with seemingly encrypted header for which no matching community which uses encrypted headers was found. #63

guest3963 opened this issue Jan 24, 2025 · 3 comments

Comments

@guest3963
Copy link

I plan to have two edges, A1 (172.16.50.1/24) and A2 (172.16.50.2/24), so that they can communicate with each other,and realize traffic encryption, header encryption, and routing forwarding between other subnets of A1 and A2 devices.

192.168.1.254(A1 eth0 IP)<->172.16.50.1(A1 tuntap IP)<->supernode<->172.16.50.2(A2 tuntap IP)<->192.168.2.254(A2 eth0 IP)

supernode remote IP&port:
10.0.0.1:53011

192.168.1.0/24(sunbet) can access 192.168.2.0/24(subnet)

let's f look at A1 and supernode, the operations I performed and the current configuration file contents:

########supernode########:
root@T3NSuperNode:/opt# ls /usr/bin/n3n-supernode -l
-r-xr-xr-x 1 root root 1442416 Jan 16 22:04 /usr/bin/n3n-supernode
root@T3NSuperNode:/opt# cat /etc/n3n/supernode.conf 
[connection]
bind=53011

[community]
cipher=Speck

[management]
port=53055
# password=fortest@11223344%

[supernode]
federation=hashSomeName
community_file=/etc/n3n/edgelist.txt

[filter]
allow_multicast=false

[logging]
verbose=4
root@T3NSuperNode:/opt# 
root@T3NSuperNode:/opt# /usr/bin/n3n-edge tools keygen A1 11223344aa
* A1 pKSJiYVpNtxcB1kPhKV7lCy2o45YvgYajsuDCyEYDWC
root@T3NSuperNode:/opt# 
root@T3NSuperNode:/opt# /usr/bin/n3n-edge tools keygen A2 aa44332211
* A2 xsWDk6gFVptVtCZN1wKyf1UAlgXLnL1aUF8+W7E+YaS
root@T3NSuperNode:/opt# 
root@T3NSuperNode:/opt# /usr/bin/n3n-edge tools keygen hashSomeName
auth.pubkey=Z94qmLNpfmRDKYuwaR1t4XT7GO2gxne+JnO4rUNKVou
root@T3NSuperNode:/opt# 
root@T3NSuperNode:/opt# /usr/bin/n3n-edge tools keygen testCyber
auth.pubkey=8MvwmJyJot+dXHHZUhRzdwJJDQmX0xRym4oCcqVGuNS
root@T3NSuperNode:/opt# 
root@T3NSuperNode:/opt# cat /etc/n3n/edgelist.txt
testCyber 172.16.50.0/24
* A1 pKSJiYVpNtxcB1kPhKV7lCy2o45YvgYajsuDCyEYDWC
* A2 xsWDk6gFVptVtCZN1wKyf1UAlgXLnL1aUF8+W7E+YaS
root@T3NSuperNode:/opt# 

########A1########
root@TN3NA1:/opt# cat /etc/n3n/edge.conf 
[community]
supernode=10.0.0.1:53011
# name=testCyber

# [connection]
# description=A1

[tuntap]
name=n3ntap
address=172.16.50.1/24
address_mode=static

[logging]
verbose=4

[filter]
allow_multicast=false

In the above situation,

supernode operation:

########supernode########
root@T3NSuperNode:/opt# n3n-supernode start
24/Jan/2025 04:22:14 [src/sn_utils.c:430] added allowed community 'testCyber' [total: 1]
24/Jan/2025 04:22:14 [src/sn_utils.c:458] assigned sub-network 172.16.50.0/24 to community 'testCyber'
24/Jan/2025 04:22:14 [src/sn_utils.c:375] added user 'A1' with public key 'pKSJiYVpNtxcB1kPhKV7lCy2o45YvgYajsuDCyEYDWC' to community 'testCyber'
24/Jan/2025 04:22:14 [src/sn_utils.c:375] added user 'A2' with public key 'xsWDk6gFVptVtCZN1wKyf1UAlgXLnL1aUF8+W7E+YaS' to community 'testCyber'
24/Jan/2025 04:22:14 [src/sn_utils.c:476] loaded 1 fixed-name communities from /etc/n3n/edgelist.txt
24/Jan/2025 04:22:14 [src/sn_utils.c:479] loaded 0 regular expressions for community name matching from /etc/n3n/edgelist.txt
24/Jan/2025 04:22:14 [src/sn_utils.c:147] started shared secrets calculation for edge authentication
24/Jan/2025 04:22:14 [src/sn_utils.c:162] calculated shared secrets for edge authentication
24/Jan/2025 04:22:14 [src/sn_utils.c:171] calculating dynamic keys
24/Jan/2025 04:22:14 [src/sn_utils.c:187] calculated dynamic key for community 'testCyber'
24/Jan/2025 04:22:14 [n3n-supernode.c:425] added federation '*hashSomeName' to the list of communities [total: 2]
24/Jan/2025 04:22:14 [n3n-supernode.c:489] auto ip address range is '10.128.0.0...10.255.255.0/24'
24/Jan/2025 04:22:14 [src/sn_utils.c:147] started shared secrets calculation for edge authentication
24/Jan/2025 04:22:14 [src/sn_utils.c:162] calculated shared secrets for edge authentication
24/Jan/2025 04:22:14 [n3n-supernode.c:499] traceLevel is 4
24/Jan/2025 04:22:14 [n3n-supernode.c:513] supernode is listening on UDP 53011 (main)
24/Jan/2025 04:22:14 [n3n-supernode.c:526] supernode opened TCP 53011 (aux)
24/Jan/2025 04:22:14 [n3n-supernode.c:533] supernode is listening on TCP 53011 (aux)
24/Jan/2025 04:22:14 [n3n-supernode.c:547] supernode is listening on TCP 53055 (management)
24/Jan/2025 04:22:14 [src/conffile.c:1418] sessiondir: /run/n3n/supernode
24/Jan/2025 04:22:14 [n3n-supernode.c:587] dropping privileges to uid=65534, gid=65534
24/Jan/2025 04:22:14 [n3n-supernode.c:607] supernode started

24/Jan/2025 04:22:24 [src/sn_utils.c:2795] timeout
24/Jan/2025 04:22:24 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:22:24 [src/peer_info.c:205] Remove 0 registrations
24/Jan/2025 04:22:24 [src/sn_utils.c:1553] purging old communities and edges
24/Jan/2025 04:22:24 [src/sn_utils.c:1592] purge_expired_communities removed 0 locally registered edges and 0 remotely associated edges
24/Jan/2025 04:22:34 [src/sn_utils.c:2795] timeout
24/Jan/2025 04:22:34 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:22:34 [src/peer_info.c:205] Remove 0 registrations

24/Jan/2025 04:22:44 [src/sn_utils.c:2795] timeout
24/Jan/2025 04:22:44 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:22:44 [src/peer_info.c:205] Remove 0 registrations
24/Jan/2025 04:22:44 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:22:44 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:22:48 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:22:48 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:22:52 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:22:52 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:22:52 [src/sn_utils.c:1666] processing incoming UDP packet [len: 38][sender: 10.0.0.1:59394]
24/Jan/2025 04:22:52 [src/sn_utils.c:1748] dropped a packet with seemingly encrypted header for which no matching community which uses encrypted headers was found
24/Jan/2025 04:22:56 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:22:56 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:22:56 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:22:56 [src/peer_info.c:205] Remove 0 registrations
24/Jan/2025 04:22:56 [src/sn_utils.c:1553] purging old communities and edges
24/Jan/2025 04:22:56 [src/sn_utils.c:1592] purge_expired_communities removed 0 locally registered edges and 0 remotely associated edges
24/Jan/2025 04:23:00 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:23:00 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:23:04 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:23:04 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:23:08 [src/sn_utils.c:1666] processing incoming UDP packet [len: 127][sender: 10.0.0.1:59394]
24/Jan/2025 04:23:08 [src/sn_utils.c:2076] Rx REGISTER_SUPER with wrong hash
24/Jan/2025 04:23:08 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:23:08 [src/peer_info.c:205] Remove 0 registrations
^C24/Jan/2025 04:23:09 [n3n-supernode.c:369] shutting down...
root@T3NSuperNode:/opt#

A1 operation:

########A1########
root@TN3NA1:/opt# ./n3n-edge \
    start \
    -l 10.0.0.1:53011 \
    -c testCyber \
    -Oconnection.description=A1 \
    -Oauth.password=11223344aa \
    -Oauth.pubkey=8MvwmJyJot+dXHHZUhRzdwJJDQmX0xRym4oCcqVGuNS \
    -Ocommunity.cipher=Speck \
    -k mySecretKey
24/Jan/2025 04:22:44 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:44 [src/peer_info.c:337] adding supernode = 10.0.0.1:53011
24/Jan/2025 04:22:44 [n3n-edge.c:790] using username and password for edge authentication
24/Jan/2025 04:22:44 [n3n-edge.c:802] enabling header encryption for edge authentication
24/Jan/2025 04:22:44 [n3n-edge.c:810] starting n3n edge 3.4.4 Thu Jan 16 08:25:39 PM EST 2025
24/Jan/2025 04:22:44 [n3n-edge.c:816] using compression: none.
24/Jan/2025 04:22:44 [n3n-edge.c:817] using Speck cipher.
24/Jan/2025 04:22:44 [src/edge_utils.c:496] number of supernodes in the list: 1
24/Jan/2025 04:22:44 [src/edge_utils.c:498] supernode 0 => 10.0.0.1:53011
24/Jan/2025 04:22:44 [src/transform_speck.c:147] setup_speck_key completed
24/Jan/2025 04:22:44 [src/edge_utils.c:536] Header encryption is enabled.
24/Jan/2025 04:22:44 [src/conffile.c:1418] sessiondir: /run/n3n/edge
24/Jan/2025 04:22:44 [n3n-edge.c:839] use manually set IP address
24/Jan/2025 04:22:44 [n3n-edge.c:857] skip PING to supernode
24/Jan/2025 04:22:44 [src/edge_utils.c:391] Setting pmtu_discovery false
24/Jan/2025 04:22:44 [n3n-edge.c:928] skip auto IP address asignment
24/Jan/2025 04:22:44 [src/tuntap_linux.c:221] Waiting for TAP interface to be up and running...
24/Jan/2025 04:22:44 [src/tuntap_linux.c:242] Interface is up and running
24/Jan/2025 04:22:44 [n3n-edge.c:962] created local tap device IPv4: 172.16.50.1/24, MAC: FE:6A:CE:68:50:35
24/Jan/2025 04:22:44 [n3n-edge.c:1031] WARNING: The build option to add libcap-dev was not used. Some actions may cause permissions messages.
24/Jan/2025 04:22:44 [n3n-edge.c:1040] dropping privileges to uid=65534, gid=65534
24/Jan/2025 04:22:44 [n3n-edge.c:1069] edge started
24/Jan/2025 04:22:44 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:22:44 [src/edge_utils.c:1217] successfully joined multicast group 224.0.0.68:1968
24/Jan/2025 04:22:44 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:44 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 2]
24/Jan/2025 04:22:44 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:22:44 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:22:44 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:22:44 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:22:44 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:22:44 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:22:44 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:22:44 [src/peer_info.c:200] Purging old registrations
24/Jan/2025 04:22:44 [src/peer_info.c:205] Remove 0 registrations
24/Jan/2025 04:22:44 [src/edge_utils.c:2238] Rx TAP packet (  90) for 33:33:00:00:00:16
24/Jan/2025 04:22:44 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:44 [src/edge_utils.c:2238] Rx TAP packet (  90) for 33:33:00:00:00:16
24/Jan/2025 04:22:44 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:45 [src/edge_utils.c:2238] Rx TAP packet (  86) for 33:33:FF:68:50:35
24/Jan/2025 04:22:45 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:46 [src/edge_utils.c:2238] Rx TAP packet (  90) for 33:33:00:00:00:16
24/Jan/2025 04:22:46 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:46 [src/edge_utils.c:2238] Rx TAP packet (  70) for 33:33:00:00:00:02
24/Jan/2025 04:22:46 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:46 [src/edge_utils.c:2238] Rx TAP packet (  90) for 33:33:00:00:00:16
24/Jan/2025 04:22:46 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:48 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:22:48 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:48 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 1]
24/Jan/2025 04:22:48 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:22:48 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:22:48 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:22:48 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:22:48 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:22:48 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:22:48 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:22:50 [src/edge_utils.c:2238] Rx TAP packet (  70) for 33:33:00:00:00:02
24/Jan/2025 04:22:50 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:52 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:22:52 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:52 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 0]
24/Jan/2025 04:22:52 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:22:52 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:22:52 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:22:52 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:22:52 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:22:52 [src/edge_utils.c:1266] send PING to supernodes
24/Jan/2025 04:22:52 [src/edge_utils.c:1078] sent=38
24/Jan/2025 04:22:52 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:22:52 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:22:56 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:22:56 [src/edge_utils.c:1628] WARNING: supernode not responding, now trying [10.0.0.1:53011]
24/Jan/2025 04:22:56 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:56 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 3]
24/Jan/2025 04:22:56 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:22:56 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:22:56 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:22:56 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:22:56 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:22:56 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:22:56 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:22:57 [src/edge_utils.c:2238] Rx TAP packet (  70) for 33:33:00:00:00:02
24/Jan/2025 04:22:57 [src/edge_utils.c:2244] dropping Tx multicast
24/Jan/2025 04:22:59 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:22:59 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:22:59 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 2]
24/Jan/2025 04:22:59 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:22:59 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:22:59 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:22:59 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:22:59 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:22:59 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:22:59 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:23:03 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:23:03 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:23:03 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 1]
24/Jan/2025 04:23:03 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:23:03 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:23:03 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:23:03 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:23:03 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:23:03 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:23:03 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:23:07 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:23:07 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:23:07 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 0]
24/Jan/2025 04:23:07 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:23:07 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:23:07 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:23:07 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:23:07 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:23:07 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:23:07 [src/edge_utils.c:2490] skipping REGISTER from self
24/Jan/2025 04:23:11 [src/edge_utils.c:1609] update_supernode_reg: doing fast retry.
24/Jan/2025 04:23:11 [src/edge_utils.c:1628] WARNING: supernode not responding, now trying [10.0.0.1:53011]
24/Jan/2025 04:23:11 [src/resolve.c:172] supernode2sock successfully resolves supernode IPv4 address for 10.0.0.1
24/Jan/2025 04:23:11 [src/edge_utils.c:1677] registering with supernode [10.0.0.1:53011][number of supernodes 1][attempts left 3]
24/Jan/2025 04:23:11 [src/edge_utils.c:1344] send REGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:23:11 [src/edge_utils.c:1078] sent=127
24/Jan/2025 04:23:11 [src/edge_utils.c:647] registering with multicast group 224.0.0.68:1968
24/Jan/2025 04:23:11 [src/edge_utils.c:1492] send REGISTER to [224.0.0.68:1968]
24/Jan/2025 04:23:11 [src/edge_utils.c:1078] sent=61
24/Jan/2025 04:23:11 [src/edge_utils.c:2324] Rx N2N_UDP of size 61 from [192.168.133.101:59394]
24/Jan/2025 04:23:11 [src/edge_utils.c:2490] skipping REGISTER from self
^C24/Jan/2025 04:23:12 [n3n-edge.c:691] shutting down...
24/Jan/2025 04:23:12 [src/edge_utils.c:1387] send UNREGISTER_SUPER to [10.0.0.1:53011]
24/Jan/2025 04:23:12 [src/edge_utils.c:1078] sent=82
24/Jan/2025 04:23:12 [src/edge_utils.c:448] closed
24/Jan/2025 04:23:12 [src/edge_utils.c:2971] **********************************
24/Jan/2025 04:23:12 [src/edge_utils.c:2972] Packet stats:
24/Jan/2025 04:23:12 [src/edge_utils.c:2973]       TX P2P: 0 pkts
24/Jan/2025 04:23:12 [src/edge_utils.c:2974]       RX P2P: 0 pkts
24/Jan/2025 04:23:12 [src/edge_utils.c:2975]       TX Supernode: 0 pkts (0 broadcast)
24/Jan/2025 04:23:12 [src/edge_utils.c:2976]       RX Supernode: 0 pkts (0 broadcast)
24/Jan/2025 04:23:12 [src/edge_utils.c:2977] **********************************
24/Jan/2025 04:23:12 [src/management.c:269] post topic=2 data0=2
root@TN3NA1:/opt#

Question One:

On the A1 system, I have tried using auth.pubkey
hashSomeName's auth.pubkey=Z94qmLNpfmRDKYuwaR1t4XT7GO2gxne+JnO4rUNKVou
Also tried A1's auth.pubkey=pKSJiYVpNtxcB1kPhKV7lCy2o45YvgYajsuDCyEYDWC

There are constant prompts on the supernode screen:
dropped a packet with seemingly encrypted header for which no matching community which uses encrypted headers was found

I've read the documentation several times, but I don't know where the problem is?

Question two:

I uncommented the management.password field of supernode.conf:

[management]
port=53055
# password=fortest@11223344%

run "supernode start", and will be prompt: Segmentation fault
How can I configure the password for the management interface with the correct location and syntax?

Question three:

If I want to generate a tap interface for the supernode itself in the testCyber ​​community and have an IP address of 172.16.50.254 so that the supernode can use this IP address to communicate with A1 and A2, can the supernode's own configuration file achieve this?
If not, do I need to run an edge process on the server at the same time to join the testCyber ​​community?

Thank you very much for your answers!
@hamishcoleman
Copy link
Contributor

In reverse order:

  • Q3, yes you need to run an edge to have a tap interface - the supernode does not duplicate the same features. The edge could load its config from the same file as the supernode, if you load them both with the same session name.

  • Q2, This sounds like a bug in the string length error logic - there is only a certain amount of space reserved for the password. It should output an informative error when that size is exceeded. We should add this as a bug that needs fixing with the sourcecode.

  • Q1, You have used a lot of features that have not had much recent testing in this example, so I would need to examine all the parts and take some time to understand exactly how your entire example is working before commenting - this might take a while to do. Perhaps if you could try turning off the optional features until you find out what the minimal config needed to reproduce this is - that might help narrowing down where the problem could be. Is there are reason you have half the config in a config file and half the config in the commandline? that also makes it a little harder to see where and what the settings are

@hamishcoleman
Copy link
Contributor

I have looked at the issue in Q2 and believe the fix in fd4d866 fixes it. This patch will be included in the next release

@hamishcoleman
Copy link
Contributor

I was able to find some time to test your config files and I think the only thing wrong with them is that the edge auth.pubkey value needs to match the key generated from the supernode.federation

I was able to use your example supernode.conf and edgelist.txt files unchanged and used this edge.conf file to test with:

[community]
#supernode=10.0.0.1:53011
supernode=localhost:53011
name=testCyber
cipher=Speck
key=mySecretKey

[connection]
description=A1

[auth]
password=11223344aa
#pubkey=8MvwmJyJot+dXHHZUhRzdwJJDQmX0xRym4oCcqVGuNS
pubkey=Z94qmLNpfmRDKYuwaR1t4XT7GO2gxne+JnO4rUNKVou

[tuntap]
name=n3ntap
address=172.16.50.1/24
address_mode=static

[logging]
verbose=4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hamishcoleman @guest3963