daemon chokes on ip4 and ip6 on same port

[hackergrrl]

given my go-ipfs generated config:

  "Addresses": {
    "Swarm": [
      "/ip4/0.0.0.0/tcp/4001",
      "/ip6/::/tcp/4001"
    ],
    "API": "/ip4/127.0.0.1/tcp/5001",
    "Gateway": "/ip4/127.0.0.1/tcp/8080"
  },

running the js-ipfs daemon will die with

Initializing daemon...
Starting at /home/noffle/.ipfs
Finished loading
error   listen EADDRINUSE :::4001

Works fine if I remove the /ip6 address.

What if you remove the /ip4? :::4001 doesn't look right

[daviddias]

It is true because we start a listener per multiaddr. Node.js TCP implementation starts a listener automatically on an IPV6 addr and IPV4, so the second time you listen, you are trying to listen on the same port.

Possible solution: Do addr matching and avoid trying to listen on equivalent addresses.
Workaround: We've been removing the ipv6 addr since we don't need it. It would be good to not have to worry about it though.

[dignifiedquire]

can we stop/disable node from auto listening on ip6? I think that would be the best solution

[daviddias]

@dignifiedquire not that I know or managed to find somewhere how to do it.

There are unix socket options for that, I don't recall the exact name (SOL_SOMETHING) or how to set socket options in nodejs.

[shamb0t]

@noffle is this issue still happening for you? I have the same config but the js-ipfs daemon isn't choking

[hackergrrl]

@shamb0t yup, still happening

[deltab]

It's the IPv6 socket binding to IPv4:

IPV6_V6ONLY (since Linux 2.4.21 and 2.6)

If this flag is set to true (non-zero), then the socket is restricted to sending and receiving IPv6 packets only. In this case, an IPv4 and an IPv6 application can bind to a single port at the same time.

If this flag is set to false (zero), then the socket can be used to send and receive packets to and from an IPv6 address or an IPv4-mapped IPv6 address.

Using it in Node seems to require the use of ffi or a compiled extension.

[daviddias]

@shamb0t here is more input: You are not seeing the error now cause I removed the IPV6 port from the default config to avoid new users getting hit by that -> e98368e#diff-ce4bf744aff5c27c180e317f04bedab0L5

What @noffle is seeing, is that if you do an ipfs init with go-ipfs and then use that repo with js-ipfs, it will choke.

We still need a fix for this on the js-libp2p-tcp transport where we filter the 'equivalent' IP addrs. Note that IPV6 has a bunch of possible combinations that result to the one of listening in any interface (0.0.0.0)

[shamb0t]

@diasdavid config file is generated from (go)ipfs init and the jsipfs daemon isn't choking. I added the line you removed from the default-config and still no choking. Should it choke if I regenerate the config with jsipfs init? Seems to be working fine for me...Im on osx 10.10