Opened 3 years ago

Closed 3 years ago

#11710 closed Bug/Something is broken (fixed)

ipv6 address for keys.mayfirst.org does not seem to be working

Reported by: https://id.mayfirst.org/jamie Owned by: https://id.mayfirst.org/dkg
Priority: Medium Component: Tech
Keywords: keys.mayfirst.org ipv6 zimmermann.mayfirst.org Cc:
Sensitive: no

Description

Ross reported being unable to connect to zimmermann.mayfirst.org and keys.mayfirst.org failed. Running mtr showed that the packets are dropped at 10ge5-1.core1.nyc6.he.net.

However, using zimmerman.mayfirst.org (an alias without an ipv6 address) did work.

So - I've dropped the ipv6 address for keys.mayfirst.org until we can fix ipv6 on zimmermann.

Change History (2)

comment:1 Changed 3 years ago by https://id.mayfirst.org/jamie

  • Owner set to https://id.mayfirst.org/dkg
  • Status changed from new to assigned

dkg - Do you think you could take a look at this and see if you can find a reason? Thanks!

comment:2 Changed 3 years ago by https://id.mayfirst.org/dkg

  • Resolution set to fixed
  • Status changed from assigned to closed

Sorry i missed this when it came in.

it looks like zimmermann wasn't listening on IPv6 at all, and i don't know why.

I looked at /etc/network/interfaces.d/eth0-ipv6 and it said:

# NOT IN PUPPET (yet)
iface eth0 inet6 static
  address 2001:470:1:116::6
  prefix 64
  gateway 2001:470:1:116::1

I changed this to the more compact/concise:

# NOT IN PUPPET (yet)
iface eth0 inet6 static
  address 2001:470:1:116::6/64
  gateway 2001:470:1:116::1

and then did:

ifdown eth0; ifup eth0

and now it is listening on IPv6 again. I don't know whether the change to the configuration made a difference or not, and i don't know how those files were set up in the first place.

I've re-enabled the AAAA record for keys.mayfirst.org, since it seems to be working now.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.