-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
ipv6 address used as extip results in 127.0.0.1
being used
#29495
Comments
Please provide the command line options used for starting geth |
I just tried removing |
The We can't see what it resolves to, since |
Yes, it seems something doesn't quite work when using an ext ipv6 address:
|
The // IP returns the IP address of the node. This prefers IPv4 addresses.
func (n *Node) IP() net.IP {
var (
ip4 enr.IPv4
ip6 enr.IPv6
)
if n.Load(&ip4) == nil {
return net.IP(ip4)
}
if n.Load(&ip6) == nil {
return net.IP(ip6)
}
return nil
} However, we also always set a fallback ipv4 ip to
So, an explicit |
127.0.0.1
being used
This should be fixed by #29801 |
System information
Geth version:
1.13.14
CL client & version: e.g. nimbus@v24.3.0
OS & Version: Linux
Expected behaviour
Sync mainnet state and chaindata after startup.
Actual behaviour
Not syncing state and chain data, even after nimbus has synced and backfilled itself.
One line in the log says "forced head needed for startup".
Steps to reproduce the behaviour
Sync a nimbus CL using checkpoint with
--backfill=false
, then launch both geth and nimbus.The text was updated successfully, but these errors were encountered: