-
Notifications
You must be signed in to change notification settings - Fork 508
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
Bad IPv6 adress to listen on #54
Comments
When running the test, it fails two things (i think both have something to do with the above error): common.c:162:F:Common:test_parse_format_ipv6:0: Assertion 'addr_len == sizeof(struct sockaddr_in6)' failed common.c:187:F:Common:test_parse_format_ipv4_mapped_ipv6:0: Assertion 'addr_len == sizeof(struct sockaddr_in6)' failed |
Running it with only It seems the machine has no IPv6 support compiled in. Add |
I tried working around this, can you try again with 559dafb? Using |
Yes of course i run it together with the internal ip and domain afterwards |
Ill try to use the new build, thanks |
Using it with -4 works! When running it without the paramter is returns : iodined: Failed to get IPv6 address to listen on: '(null)': Success After that it just prints the usage, but the program doesn't resume |
I updated the logging. What does it print now (without |
iodined: Failed to get IPv6 address to listen on: '(null)': Name or service not known following the usage page |
I just ran into another problem, on my client machine it says that no tap adapter was found. When i look at the driver version in device manager it clearly says its tap0901. So i don't see what the problem is |
The listen address issue should be fixed now, reopen otherwise. |
iodined: Bad IPv6 address to listen on: '(null)'
I got this issue when trying to run: iodined -f . It returned the error Bad Ipv6 adress to listen on. While trying to find out why i got this issue, i commented out the if statement that is responsible for returning this error. I got the following error: socket: Address family not supported by protocol.
I' m afraid it might have something to do with the configuration of my VPS, but I have no idea what would cause it. If anyone can help with this, that would be great :)
The text was updated successfully, but these errors were encountered: