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.

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

Bootstrapd: IPv6 enabled, no IPv4 ports "listening" #1633

Open
leonmorlando22 opened this issue Feb 17, 2017 · 6 comments
Open

Bootstrapd: IPv6 enabled, no IPv4 ports "listening" #1633

leonmorlando22 opened this issue Feb 17, 2017 · 6 comments

Comments

@leonmorlando22
Copy link

Please, go easy on me. I'm a complete novice to Github.
I compiled toxcore with --enable-daemon flag as specified in the guide, then copied and edited tox-bootstrapd.conf. The only changes I made in the file were set enable_ipv6 to true and specify valid nodes at the bottom. I checked everything to be working both through the systemd unit with the status command and with netstat. The latter shows that only tcp6 and udp6 ports are used.

netstat -luptn | egrep "tox"
tcp6       0      0 :::33445                :::*                    LISTEN      2145/tox-bootstrapd
tcp6       0      0 :::3389                 :::*                    LISTEN      2145/tox-bootstrapd
udp6    2304      0 :::33445                :::*                                2145/tox-bootstrapd

What am I doing wrong?

@GrayHatter
Copy link
Collaborator

what guide did you follow?

@nurupo

@nurupo
Copy link
Contributor

nurupo commented Feb 17, 2017

@leonmorlando22 say if you can reproduce the same with tox-bootstrapd from https://github.com/TokTok/c-toxcore.

@nurupo
Copy link
Contributor

nurupo commented Feb 17, 2017

@leonmorlando22 toxcore uses IPv6/IPv4 dualstack, so people should be able to connect to you using your IPv4 IP address even though there is no IPv4 in netstat.

@nurupo
Copy link
Contributor

nurupo commented Feb 17, 2017

That is, unless the OS denies toxcore's request to use the dualstack, in which case it would be IPv6-only. The netstat output should look the same in both cases though, whether it uses dualstack IPv4 and IPv6, or it doesn't use dualstack and uses only IPv6. The dualstack I'm speaking of is setting IPV6_V6ONLY option of a socket to 0.

@leonmorlando22
Copy link
Author

@GrayHatter INSTALL.md on this very repo: https://github.com/irungentoo/toxcore/blob/master/INSTALL.md

@nurupo So it's not a problem that I have ports 3389 and 33445 in the "LISTENING" status only on TCP6 and UDP6? Nginx properly shows as taking 443 in both TCP and TCP6, so I thought maybe it was messing with boostrapd, but even with nginx not running, it doesn't listen on TCP.
Also, I compiled toxcore and boostrapd from the other repo and it didn't make a difference. BUT, if it's working as intended (how could I test?) then I guess I'm worrying about nothing.

Thanks for the replies!

@nurupo
Copy link
Contributor

nurupo commented Feb 17, 2017

how could I test?

Just bootstrap your bootstrap node off other bootstrap nodes and check netstat after a bit, you should see IPv4 connections from other nodes soon enough. The bootstrap_nodes option in tox-bootstrapd.conf is just an example which you should replace with actual bootstrap nodes. You can using this script to get a list of bootstrap nodes (they would be taken from https://nodes.tox.chat) in the format suitable for bootstrap_nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants