tox-bootstrap daemon behind reverse proxy

[rong-00gle]

Hi,
I wanna configure tox-bootstrap daemon or tox node behind a firewall(port forwording).
nmap scan shows port is open but qtox(client) is unable to connect with node.

Does tox-bootstrap daemon work behind reverse proxy?
If no, is there any other way of putting my node behind a firewall?

[nurupo]

tox-bootstrapd uses UDP port 33445, so make sure that passes through your firewall/proxy. If you have tcp relay feature enabled, then you need to pass through the corresponding TCP ports. You can change ports in the config file.

[rong-00gle]

I have host my tox-bootstrap node(only tcp port 33445) behind cisco-asa firewall.
port forwarding done - nmap show port is open but my tox-client(qtox) unable to connect with dht node.

[nurupo]

Okay, a few things to note:

• DHT in toxcore is UDP-only
• If you don't open UDP port, tox-boostrapd won't be able to connect to other bootstrap nodes you have listed in the config file, as well as other nodes won't be able to connect to you
• The TCP is for the Relay Server functionality, which is basically your tox-bootstrapd providing a service of a DHT node to clients who can't run their own DHT node due to e.g. being behind a restrictive NAT or not able to use UDP
• qTox should be able to connect to your tox-boostrapd through either UDP or TCP, even if your tox-bootstrap node is not connected to any other node, so maybe your qTox is not configured to connect to your node through TCP? qTox should write in the log file which nodes it's connecting to.

If you node is on the internet, you can check if it works with this test page https://nodes.tox.chat/test. It sends some packets to you node and checks if it gets the correct response back. If it's in a private network, you can telnet into your node telnet <ip> 33445 to at least make sure there is something accepting TCP connections on there (I guess nmap works too).

Anyway, from what you have described it sounds like your tox-boostrapd node should have no issues with receiving TCP connections, so make sure that qTox is actually attempting to connect to it through TCP. You might want to open an issue at https://github.com/qTox/qTox and have qTox folks help you figure out why qTox is not connecting to the node if you have hard time troubleshooting it yourself.

[rong-00gle]

@nurupo
Hi,
tox clients(qtox, isotoxin) are still unable to connect(status: offline) with tox-bootstrap node hosted by me.

tox-client status client shows offline, tcp connection state is ESTABLISHED:

tox-bootstrap node status:

tox-bootstrap node status on https://nodes.tox.chat/test

What i want is host some nodes(only tcp) which will isolated from any other third-party tox-nodes, my clients will be only using tcp port to connect with tox-nodes?Must me something which i am missing, please help me with this?

[iphydf]

Please try this again with latest master (or in a few days, v0.2.14). There's more logging now so we could find out what's going wrong.

[nurupo]

@emdee-is please don't necropost with questions that are not related to the issue at hand, either open a new issue, or just ask on IRC / groupchat.