-
Notifications
You must be signed in to change notification settings - Fork 973
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
Does not work on ipv4 address #59
Comments
Can you give us a bit more about your environment? |
sudo ./dnsseed -h seed.myhost.com -n seedns.myhost.com -m [email protected] -t 2 -d 1 sudo netstat -tunlp tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 314/sshd https://ping.eu/nslookup/ shows: Using domain server: |
Same situation Supporting whitelisted filters: 0x1,0x5,0x9,0xd netstat -apn | grep dnsseed telnet to 188.40.135.251:53 ;btcz.ps-pool.ru. IN ANY ;; ANSWER SECTION: ;; ADDITIONAL SECTION: |
how to fix it. |
Does anyone find a solution here? I have the same issue. |
I've pulled in this PR #84 and it binds to an ipv4 but the protocol is upd6 in netstat, does that matter?
|
That shouldn't be a problem; you can bind an IPv6 socket to an IPv4 address. Does it work or not? |
@sipa well, the seeder runs but its a new instance so I'm guessing it will take awhile to crawl for nodes and index them.... |
Just to follow up - I've let the seeder run using It does still bind to the IPv6 socket, but as mentioned above, it does work. |
Seeder does not listen on ipv4 address, it works on ipv6 only.
The text was updated successfully, but these errors were encountered: