05/Dec/2023 01:45:24 [sn_utils.c:395] added allowed community 'N2NGroup' [total: 1]
05/Dec/2023 01:45:24 [sn_utils.c:1296] assigned sub-network 10.222.10.0/24 to community 'N2NGroup'
05/Dec/2023 01:45:24 [sn_utils.c:340] added user 'HomeServer' with public key 'rkt9LCIxkfadwpKcGq0QW9FznTI43JKIbPhy5wsYQmm' to community 'N2NGroup'
05/Dec/2023 01:45:24 [sn_utils.c:440] loaded 1 fixed-name communities from ./community.list
05/Dec/2023 01:45:24 [sn_utils.c:443] loaded 0 regular expressions for community name matching from ./community.list
05/Dec/2023 01:45:24 [sn_utils.c:115] started shared secrets calculation for edge authentication
05/Dec/2023 01:45:24 [sn_utils.c:131] calculated shared secrets for edge authentication
05/Dec/2023 01:45:24 [sn_utils.c:140] calculating dynamic keys
Are you able to retest this against the recently released fork n3n and raise a ticket there if it is still happening? We would be happy to investigate it further as part of that new project.
Sorry for my poor English
I've tried following setting on both Windows 11 and Archlinux(on WSL2), none of them works, supernode just exit after few seconds
community.list:
supernode parameter: Arch: supernode -p 60666 -c ./community.list -F MyN2N -v Windows: .\supernode.exe -p 60666 -c "D:\N2N\community.list" -v
supernode exits after following messages
Any ideas?