Tuna mode and Usage about nkn-tunnel HOT 2 CLOSED

And I found that the listening address changes every restart,
that means let's say if A side client restart, B side needs to renew the forwarding address to re-establish connection.

follow up:
I found a way to make listening address fixed, which is to get a seed/addr pair on nsh.nkn.org then fill -s parameter.
Is it supposed that the nTunnel client itself have this option natively built-in?

from nkn-tunnel.

And I found that the listening address changes every restart, that means let's say if A side client restart, B side needs to renew the forwarding address to re-establish connection.

Yes that's expected. If you pass a secret seed in, the address will be fixed. Otherwise a random one is generated on each start.

follow up: I found a way to make listening address fixed, which is to get a seed/addr pair on nsh.nkn.org then fill -s parameter. Is it supposed that the nTunnel client itself have this option natively built-in?

A secret seed is just an arbitrary 32-byte array (64 hex characters), you can use any ways to generate one. A few examples:

• You can use nknc to generate a wallet and get secret seed
• You can generate a wallet at wallet.nkn.org and get it using show secret seed.
• You can even generate it at something like https://www.browserling.com/tools/random-hex

If we have such feature built-in into nkn tunnel, it will probably print out secret seed in stdout and will be recorded in bash history, which makes it not that secure... We will probably add it if we can think of a better way to handle the wallet I/O part.

from nkn-tunnel.