Monero seems to have an IPv4-only problem.

[86dd]

• My IPv6-only monerod node can't seem to find any IPv6 peers. It only wastes it's time on IPv4 nodes.
• The seed nodes seem to only be IPv4. Adding some IPv6 seed nodes would be important.
• When I told it to use IPv6 only (p2p-ignore-ipv4=1, rpc-ignore-ipv4=1), it still tries and binds IPv4. It would be great to be able to fully turn off IPv4.
• You must explicitly enable IPv6 (p2p-use-ipv6=1, rpc-use-ipv6=1). Ideally, IPv6 should be enabled by default.
• Node websites I've visited are either .onion or IPv4 only. I'm aware this has nothing to do with this repository, but including it in this discussion may get them to support IPv6.

I'd love to contribute to the source code, but unfortunately I don't feel comfortable in C++ (yet), so maybe starting this discussion will help getting the "IPv6 ball rolling" for Monero.

[poiuty]

Why is ipv6 disabled by default?

--p2p-use-ipv6 | Enable IPv6 for p2p (disabled by default).

https://monerodocs.org/interacting/monerod-reference/

[rnhmjoj]

If not enabled by default IPv6 support is quite useless in a p2p application.
Probably the only users that will go through the docs, find the cli option and enable it are those on an IPv6-only network, but then it won't matter because there's nobody else to peer: dual stacked users will only ever use IPv4.

[kkarhan]

Why is ipv6 disabled by default?

--p2p-use-ipv6 | Enable IPv6 for p2p (disabled by default).

https://monerodocs.org/interacting/monerod-reference/

I'm convinced this is done amidst the fears of [pseudo-]static IPv6 assignments?
A lot of people think that NAT is a security feature and the lack of said NAT + the use of EUI48 aka. MAC-Adresses to create the Interface Indentifier unless Privacy Extensions are being enabled [which basically all Desktop & mobile OSes do by default!] is seen as a privacy infringement.

Still, I think that Monero should support proper dual-stack and not care whether or not someone uses IPv4, IPv6 nor VPNs or even Tor and thus default to proper dual stack, with the option to prefer and/or disable IPv4 [or even IPv6 if there would be any legit reason to do so]...

[boldsuck]

• My IPv6-only monerod node can't seem to find any IPv6 peers. It only wastes it's time on IPv4 nodes.

• The seed nodes seem to only be IPv4. Adding some IPv6 seed nodes would be important.

You can use mine for seed-node= | add-priority-node= | add-peer= if you want. RPC & P2P is dual stacked + .onion.

xmr-de.boldsuck.org | xmr-in-berlin.boldsuck.org
185.220.101.63:18080
2a0b:f4c2:2::63:18080
2i3jrsezgjyqgmrqk4t3dxoixihv3aa6zzmrxlz7qr6n3l2bhilxwxyd.onion:18083 <- p2p
i4jsfwmw22yjzzmzkoc7aahiaqlyhnykn5wxel43u3o5ibz2k4275jqd.onion:18081 <- RPC

xmr-de-2.boldsuck.org | xmr-in-berlin-2.boldsuck.org
185.220.101.223:18080
2a0b:f4c2:2:1::223:18080
sqzrokz36lgkng2i2nlzgzns2ugcxqosflygsxbkybb4xn6gq3ouugqd.onion:18083 <- p2p
6dsdenp6vjkvqzy4wzsnzn6wixkdzihx3khiumyzieauxuxslmcaeiad.onion:18081 <- RPC

For blockchain sync use the top two. They are connected with 2x10G, the others only have 1G NIC.

xmr-de-1.boldsuck.org | crypto-01.boldsuck.org
217.79.184.72:18080
2001:4ba0:ffff:c4::2:18080
k6eefejth3zgej4xr7zzxlw457akgswg5bapfn4ragc2yxtvi3j7cxid.onion:18083 <- p2p
ip4zpbps7unk6xhlanqtw24f75akfbl3upeckfjqjks7ftfnk4i73oid.onion:18081 <- RPC

Stagenet node:
xmr-lux.boldsuck.org
104.244.75.217:38080
2605:6400:30:f91d::2:38080
rsdfcp3c7v7shamu5quyuw72takrlxgqbg3x5tyvts2d4whtstf35iyd.onion:38083 <- p2p
ct36dsbe3oubpbebpxmiqz4uqk6zb6nhmkhoekileo4fts23rvuse2qd.onion:38081 <- RPC

[86dd]

I've tried them but as mentioned before monero unfortunately keeps trying IPv4.
I'll look into writing patches - if I have the time - to enable IPv6 by default, an "algorythm" to test for connectivity and add an option to restrict it to a network - like with bitcoinds --onlynet=ipv6|ipv4|onion.

[rnhmjoj]

@juliaszone: If you want an algorithm for choosing between IPv4/IPv6 RFC 8305 may be worth a look. Also, RFC 8880 for detecting an IPv6-only network with NAT64 available.

[boldsuck]

I've tried them but as mentioned before monero unfortunately keeps trying IPv4.

@juliaszone Have you tried the following options in your monerod.conf?

~$ monerod --help

p2p-bind-ipv6-address[::] 
p2p-use-ipv6=1                     Enable IPv6 for p2p
p2p-ignore-ipv4=1                  Ignore unsuccessful IPv4 bind for p2p
rpc-bind-ipv6-address=[::1]
rpc-restricted-bind-ipv6-address=[::]
rpc-use-ipv6=1                     Allow IPv6 for RPC
rpc-ignore-ipv4=1                  Ignore unsuccessful IPv4 bind for RPC

[86dd]

@boldsuck Yes:

(it's supposed to be a public node fy)

[ivanka2012]

@boldsuck All 3 of your IPv6 mainnet nodes are resetting p2p connections being made to port 18080

[boldsuck]

I looked at the peer lists on all my nodes, only IP and .onion, there isn't a single IPv6 address among thousands :-(

marco@boldsuck2:~$ monerod --rpc-bind-port=8081 print_pl_stats
2023-05-07 15:16:55.073 I Monero 'Fluorine Fermi' (v0.18.2.2-release)
White list size: 1532/1000 (153.2%)
Gray list size: 5613/5000 (112.26%)

This is how my own nodes look in the list:

white      2d7f80e8053574e2          185.220.101.192:18080     18081 -     0    d0.h1.m31.s3
white      2d7f80e8053574e2          185.220.101.223:18080     18081 -     0    d0.h0.m1.s15
gray       1cac1e4b919c97a8          185.220.101.32:18080      18081 -     184  never
gray       1cac1e4b919c97a8          185.220.101.33:18080      18081 -     0    never
gray       1cac1e4b919c97a8          ::ffff:185.220.101.32:18080 18081 -     0    never
gray       392ffba366eb11a3          ::ffff:185.220.101.33:18080 18081 -     0    never
gray       1cac1e4b919c97a8          ::ffff:185.220.101.39:18080 18081 -     0    never
gray       1cac1e4b919c97a8          ::ffff:185.220.101.63:18080 18081 -     0    never
gray       2d7f80e8053574e2          ::ffff:185.220.101.192:18080 18081 -     0    never

ditatompel's node doesn't see IPv6 either.

All my monerod nodes are not listening on the IPv6 P2P port even though it is configured:

# P2P full node
p2p-bind-ip=0.0.0.0            # Bind default to all interfaces (0.0.0.0)
p2p-bind-port=18080            # Bind to default port 18080, 28080 if 'testnet', 38080 if 'stagenet'
p2p-bind-ipv6-address=[::]     # Bind default to all interfaces (::)
p2p-bind-port-ipv6=18080      # (default same as ipv4 port for given nettype)
p2p-use-ipv6=1                 # Enable IPv6 for p2p (default false)

root@boldsuck:~# ss -lt src :18080
State                       Recv-Q                      Send-Q                                           Local Address:Port                                             Peer Address:Port                      Process
LISTEN                      0                           128                                                    0.0.0.0:18080                                                 0.0.0.0:*
root@boldsuck:~# ss -lt src :18081
State                       Recv-Q                      Send-Q                                           Local Address:Port                                             Peer Address:Port                      Process
LISTEN                      0                           128                                                    0.0.0.0:18081                                                 0.0.0.0:*
LISTEN                      0                           128                                                       [::]:18081                                                    [::]:*

¯_(ツ)_/¯

[boldsuck]

Uhh I got it. The brackets at p2p-bind-ipv6-address=[::] interfere.
Weird rpc-bind-ipv6-address=[::1] and rpc-restricted-bind-ipv6-address=[::] can be specified with brackets.
Now with p2p-bind-ipv6-address=:: all nodes are listening dual again:

root@boldsuck:~# ss -lt src :18080
State                       Recv-Q                      Send-Q                                           Local Address:Port                                             Peer Address:Port                      Process
LISTEN                      0                           128                                                    0.0.0.0:18080                                                 0.0.0.0:*
LISTEN                      0                           128                                                       [::]:18080                                                    [::]:*
root@boldsuck2:~# ss -lt src :18080
State                       Recv-Q                      Send-Q                                           Local Address:Port                                             Peer Address:Port                      Process
LISTEN                      0                           128                                                    0.0.0.0:18080                                                 0.0.0.0:*
LISTEN                      0                           128                                                       [::]:18080                                                    [::]:*
root@crypto-01:~# ss -lt src :18080
State                       Recv-Q                      Send-Q                                           Local Address:Port                                             Peer Address:Port                      Process
LISTEN                      0                           128                                                    0.0.0.0:18080                                                 0.0.0.0:*
LISTEN                      0                           128                                                       [::]:18080                                                    [::]:*

And now there are also IPv6 addresses in my peer list:

white      40da54d17d341a75          2001:4ba0:ffff:c4::2:18080 18081 -     0    d0.h0.m1.s1
white      9e2447f269b04293          2a0b:f4c2:2:1::223:18080  18081 -     0    d0.h0.m1.s1

Is this a bug or a new feature?
Previously, IPv6 addresses had to be specified as "[xx:xx:xx::xx:xx]:port" in the configuration file, except in the cases of the cli arguments for the bind address. For these, the square brackets can be omitted.

[cyboerg42]

add-priority-node=[2001:41d0:801:2000::5811]:18080
add-priority-node=[2a03:3b40:100::1:513]:18080
add-priority-node=[2602:ff16:1:0:1:138:0:1]:18080
add-priority-node=[2001:470:de5a::ec]:18080
add-priority-node=[2a01:4f9:3051:17a1::2]:18080
add-priority-node=[2604:4300:a:358::146]:18080
add-priority-node=[2a0b:f4c2:2::63]:18080
add-priority-node=[2a0b:f4c2:2:1::223]:18080
add-priority-node=[2001:4ba0:ffff:c4::2]:18080
add-priority-node=[2001:678:7f8::b00b]:18080
add-priority-node=[2a01:190:1337::206]:18080

Some of the nodes I've found while scanning public nodes for AAAA DNS entries.

[boldsuck]

add-priority-node=[2001:4ba0:ffff:c4::2]:18080

Will be offline in a few weeks, new server is up & monerod synced:
add-priority-node=[2001:4ba0:ffff:4a::2]:18080

[imcdona]

I've been running an IPv6 enabled node for several weeks and haven't had a single incoming IPv6 connection. Is there a config option that must be specified to advertise the IPv6 node port?

Here's my IPv6 enabled node for anyone needing an IPv6 enabled peer:

add-priority-node=[2602:41:642e:a610::251]:18080

[X3KT0]

I've read the entire thread.
So nobody will find my IPv6 address by regular P2P node address advertising procedure, am I right?