You are reading content from Scuttlebutt
@kas %WmZ2ZJ1Tdwl6NSE9EaQcXBuIbu+dblnm7b9P9KtBxsw=.sha256

Why so many connections?

$ sudo netstat -anp | grep node
tcp      0     0 127.0.0.1:8043          0.0.0.0:*               LISTEN      2027/node
tcp      0     0 127.0.0.1:8027          0.0.0.0:*               LISTEN      2027/node
tcp6     0     0 :::8008                 :::*                    LISTEN      2027/node
tcp6     0     0 :::8989                 :::*                    LISTEN      2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac1:8008 fdc8:f93c:a1b9:ac:39550 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:49240 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:37928 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:41388 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:51258 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:55776 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac1:8008 fdc8:f93c:a1b9:ac:39250 ESTABLISHED 2027/node
                          :
            [ 220+ similar lines omitted ]
                          :
tcp6     0     0 fdc8:f93c:a1b9:ac1:8008 fdc8:f93c:a1b9:ac:40808 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:46362 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:51366 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac1:8008 fdc8:f93c:a1b9:ac:36726 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:48920 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:52152 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
tcp6     0     0 fdc8:f93c:a1b9:ac:51734 fdc8:f93c:a1b9:ac1:8008 ESTABLISHED 2027/node
udp      0     0 0.0.0.0:8008            0.0.0.0:*                           2027/node

One would think that a couple of connections would be enough, right? But 220+? What's going on here?

It's impossible to see the actual IP addresses, but there is exactly one IPv6 address on the left hand side (local) and at most two unique IPv6 addresses involved on the right hand side (remote).


  • sbot@12.2.0
  • node@10.11.0
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@kas %xGMbjsC+GvQHcYVe0bOOAgwn8/3iayDKevHVC7Z+LwU=.sha256

@joeyh,

In a way you're correct, but that's not what we were seeing.

My ‘pub’ announces itself as ssb.bornmesh.dk that has two addresses:

  • fc2a:e8f2:3f9c:52e5:5c2f:da95:9213:7bd7 # cjdns
  • 2001:0470:0028:05b5:dacb:8aff:feba:55d7 # IPv6 tunnel

The 200+ IPv6 address lines are all related to TINC connections to two pubs I have running on VPSes elsewhere. That's why I know that there are at most three IPv6 addresses involved in all those lines.

However, my pub will gladly call out to any other node it can reach – also over routable IPv4 – which is why you can sometimes see it in my sidebar, but I never see any incoming IPv4 connections (I configured it this way deliberately because I don't want my syslog spammed with gazillions of lines with tcplog: port 8008 (ssb) connection from $IPv4).

Join Scuttlebutt now