Bitcoin Forum
May 05, 2024, 03:46:48 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin - Altcoin "connecting to peers" Problem  (Read 26 times)
SecCall (OP)
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
March 12, 2024, 11:31:26 PM
Last edit: March 13, 2024, 12:05:35 AM by SecCall
 #1

Hello community,

I created an altcoin based on Bitcoin v.26.0.
All clients run without error messages (seccoin-qt, seccoind, seccoin-cli etc).
For the time being, I have a hardcoded fullnode running on a Windows VPS in my network, 2 peers with different IPs and a DNS seed server (Debian 6.1.76) on which I have the adapted Sipa Bitcoin seeder running.
My problem is that the peers don't want to find each other, the peers find the full node and communicate with it, the full node finds both peers and also communicates, sends and receives data from them.
But the peers cannot find each other.

The FullNode is also hardcoded in the DNS seeder script, is found and displayed as active.
The DNS seeder responds to DNS queries and also displays them.
An nslookup is successful and shows the IP of my VPS server.

I start the seeder with this command: sudo nohup ./dnsseed -h dnsseed.xxx.com -n vps.xxx.com -m admin.xxx.com &

Excerpts from my DNS seeder:

root@vps:~/seccoin-seeder# tail -f nohup.out
Supporting whitelisted filters: 0x1,0x5,0x9,0xd,0x49,0x400,0x404,0x408,0x40c,0x4 48,0x809,0x849,0xc08,0xc48
Starting 4 DNS threads for dnsseed.xxx.com on vps.xxx.com (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
[24-03-12 13:40:29] 1/2 available (2 tried in 872s, 0 new, 0 active), 0 banned; 46 DNS requests, 9 db queries

root@vps:~# sudo netstat -tulnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 523/sshd: /usr/sbin
tcp6 0 0 :::22 :::* LISTEN 523/sshd: /usr/sbin
udp6 0 0 xxx.x.xxx.xx:53 :::* 605/./dnsseed

root@vps:~# sudo ufw status
sudo: ufw: command not found (No Firewall

Excerpt from client debug.log:

2024-03-12T17:55:56Z Loaded 0 addresses from "anchors.dat"
2024-03-12T17:55:56Z 0 block-relay-only anchors will be tried for connections.
2024-03-12T17:55:56Z init message: Starting network threads…
2024-03-12T17:55:56Z net thread start
2024-03-12T17:55:56Z dnsseed thread start
2024-03-12T17:55:56Z init message: Done loading
2024-03-12T17:55:56Z addcon thread start
2024-03-12T17:55:56Z msghand thread start
2024-03-12T17:55:56Z Waiting 11 seconds before querying DNS seeds.
2024-03-12T17:55:56Z opencon thread start
2024-03-12T17:55:56Z GUI: Platform customization: "windows"
2024-03-12T17:55:56Z New outbound-full-relay v1 peer connected: version: 70016, blocks=0, peer=0
2024-03-12T17:56:07Z Loading addresses from DNS seed dnsseed.xxx.com
2024-03-12T17:56:07Z 1 addresses found from DNS seeds
2024-03-12T17:56:07Z dnsseed thread exit
2024-03-12T17:56:57Z Adding fixed seeds as 60 seconds have passed and addrman is empty for at least one reachable network
2024-03-12T17:56:57Z Added 0 fixed seeds from reachable networks.


I haven't created any blocks yet except the genesis block as I haven't found a CPU mining script yet, maybe someone knows a good one?
But as far as I know, that can't be the reason why the peers can't find each other.
What I noticed is that my server only listens on IPv6 and port 53 remains closed even though the seeder is running.

Could that be the error?
If so, how can I make my DNS seeder server open port 53 and work on IPv6 as well as IPv4?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!