IP route issue with -n option in latest version v2.9.xx

[tlsalex]

1. I tried to add -n option to edge.conf in the latest DEV version. It gives me some error info as bellow:

19/Feb/2021 09:03:13 [edge_utils.c:3309] Adding supernode = xx.xx.xx.xx:8080
19/Feb/2021 09:03:13 [edge.c:907] WARNING: Switching to AES as key was provided.
19/Feb/2021 09:03:13 [edge.c:918] Starting n2n edge 2.9.0 Feb 18 2021 17:37:24
19/Feb/2021 09:03:13 [edge.c:924] Using compression: none.
19/Feb/2021 09:03:13 [edge.c:925] Using AES cipher.
19/Feb/2021 09:03:13 [edge_utils.c:304] Number of supernodes in the list: 1
19/Feb/2021 09:03:13 [edge_utils.c:306] supernode 0 => xx.xx.xx.xx:8080
19/Feb/2021 09:03:13 [transform_aes.c:210] setup_aes_key 128-bit key setup completed
19/Feb/2021 09:03:13 [edge_utils.c:3030] waiting for netlink response...
19/Feb/2021 09:03:13 [edge_utils.c:3064] Add xx.xx.xx.xx/32 via 192.168.2.10
19/Feb/2021 09:03:13 [edge_utils.c:3030] waiting for netlink response...
19/Feb/2021 09:03:13 [edge_utils.c:3049] ERROR: [err=101] route: Add 0.0.0.0/1 via 192.168.99.22
19/Feb/2021 09:03:13 [edge_utils.c:367] ERROR: routes setup failed
19/Feb/2021 09:03:13 [edge.c:941] ERROR: Failed in edge_init

2. In the stable v2.8 version , if I add -n=0.0.0.0/0:192.168.99.22. it will create a route that looks something like bellow: ip route add 0.0.0.0/1 via 192.168.99.22 dev edge0 In theory , it's not correct to tunnel all traffic , as only the traffic that destine for 0.0.0.0-127.255.255.255 will send to 192.168.99.22, other traffic will go though the default gateway. I think the same thing will happen in the latest DEV version.

I am not sure I am right, just mentions here.

[tlsalex]

Any update ?

[Logan007]

If -n is buggy and no one is able to repair it, shall we disable this feature?