-
Notifications
You must be signed in to change notification settings - Fork 19
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
NEAT does not listen on IPv6 #414
Comments
Two things,
https://github.com/NEAT-project/neat/blob/master/neat_core.c#L4524 I am not sure which is the correct default name to use, I would prefer
https://github.com/NEAT-project/neat/blob/master/neat_core.c#L4551 This should be |
Indeed, listening to ‘::’ allows for IPv4 and IPv6 connections
From: Tom Jones <[email protected]>
Reply-To: NEAT-project/neat <[email protected]>
Date: Tuesday 9 January 2018 at 16:06
To: NEAT-project/neat <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [NEAT-project/neat] NEAT does not listen on IPv6 (#414)
Two things,
1. neat_accept will default to the ipv4 ANYADDR 0.0.0.0
https://github.com/NEAT-project/neat/blob/master/neat_core.c#L4524
I am not sure which is the correct default name to use, I would prefer ::, but I live in the future.
1. the call to the resolver only requests AF_INET
https://github.com/NEAT-project/neat/blob/master/neat_core.c#L4551
This should be AF_UNSPEC according to man pages on Linux, FreeBSD and OS X.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#414 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEW9HyPUyiN40FFb6sUViVRyFqWzV2hzks5tI4BrgaJpZM4RX7Z4>.
|
@evyncke this is what I thought, reading around and it gets less clear. Using |
Unsure whether you need to use AF_UNSPEC though but the ‘::’ is clearly the way to go (possibly with AF_INET6 rather than AF_UNSPEC)
I also see “sysctl net.ipv6.bindv6only” which should be 0 obviously
-éric
From: Tom Jones <[email protected]>
Reply-To: NEAT-project/neat <[email protected]>
Date: Tuesday 9 January 2018 at 16:45
To: NEAT-project/neat <[email protected]>
Cc: Eric Vyncke <[email protected]>, Mention <[email protected]>
Subject: Re: [NEAT-project/neat] NEAT does not listen on IPv6 (#414)
@evyncke<https://github.com/evyncke> this is what I thought, reading around and it gets less clear. Using :: and AF_UNSPEC causes ipv4 to hang as ipv6 did.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#414 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEW9Hy3RM8lukp-FFTwxzX0nc9-r2Y8vks5tI4mQgaJpZM4RX7Z4>.
|
On 9. Jan 2018, at 17:02, Eric Vyncke ***@***.***> wrote:
Unsure whether you need to use AF_UNSPEC though but the ‘::’ is clearly the way to go (possibly with AF_INET6 rather than AF_UNSPEC)
I also see “sysctl net.ipv6.bindv6only” which should be 0 obviously
Don't rely on sysctl variables. Always use the IPV6_V6ONLY socket option
to set the socket in the mode you want.
Best regards
Michael
…
-éric
From: Tom Jones ***@***.***>
Reply-To: NEAT-project/neat ***@***.***>
Date: Tuesday 9 January 2018 at 16:45
To: NEAT-project/neat ***@***.***>
Cc: Eric Vyncke ***@***.***>, Mention ***@***.***>
Subject: Re: [NEAT-project/neat] NEAT does not listen on IPv6 (#414)
@evyncke<https://github.com/evyncke> this is what I thought, reading around and it gets less clear. Using :: and AF_UNSPEC causes ipv4 to hang as ipv6 did.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#414 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEW9Hy3RM8lukp-FFTwxzX0nc9-r2Y8vks5tI4mQgaJpZM4RX7Z4>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The tneat example does not seem to listen on ipv6, when it does listen on ipv4. v6 addresses are listed in the log messages.
tcpdump
shows resets for any requests.To reproduce with
tneat
:Connect with
nc
ipv4tneat side :
The text was updated successfully, but these errors were encountered: