@ingber:

Are Linode.com VPSs considered a "pool" of some kind when using the RIPE database?
Yes. Linode mainly allocates IPs from one /64 per data center. Given how easy it is for an abusive user to get hold of a /64 – or more -- to churn through, it's unfortunately common for large blocks to be banned with little excuse.

RIPE has done this before. You can pop off an email to the address at the link RIPE gave you, or file a ticket and Linode could do the same. It should be resolved quickly.

Unless, of course, you actually are abusing them somehow.

Edit: Consider requesting your own /64 from Linode. It will help prevent you from getting caught in abuse-related crossfire.

Matt:

Thanks for the advice. Linode support was helpful as usual.

Lester

Matt:

Getting an added full IPv6 block didn't work, as my primary IPv6 address is still taking precedence, e.g.,

% whois IPv4_lookup

% This is the RIPE Database query service.

% The objects are in RPSL format.

%

% The RIPE Database is subject to Terms and Conditions.

% See http://www.ripe.net/db/support/db-terms-conditions.pdf

%ERROR:201: access denied for myPrimaryIPv6

%

% Sorry, access from your host has been permanently

% denied because of a repeated excessive querying.

% For more information, see

% http://www.ripe.net/data-tools/db/faq/f … ess-denied">http://www.ripe.net/data-tools/db/faq/faq-db/why-did-you-receive-the-error-201-access-denied

% This query was served by the RIPE Database Query Service version 1.68.1 (WHOIS2)

Linode Support said to use one of the fixes you cited in another message, https://forum.linode.com/viewtopic.php?t=8525 , using preferred_lft 0. When this didn't work, Support gave up and told me to post my info here. My /etc/network/interfaces file is now a product of input from several Support people, e.g., putting everything under static, adding my primary IPv6 address, etc.

cat /etc/network/interfaces

The loopback interface

The loopback interface

auto lo

iface lo inet loopback

Configuration for eth0 and aliases

This line ensures that the interface will be brought up during boot.

auto eth0

eth0 - This is the main IP address that will be used for most outbound connections.

The address, netmask and gateway are all necessary.

iface eth0 inet static

address my_IPv4

netmask 255.255.255.0

gateway myIPv4gateway

up /sbin/ip -6 addr add mynewIPv6_block/64 dev eth0

down /sbin/ip -6 addr del mynewIPv6_block/64 dev eth0

up /sbin/ip -6 addr add myPrimaryIPv63/64 dev eth0 preferred_lft 0

down /sbin/ip -6 addr del myPrimaryIPv63/64 dev eth0

dns-nameservers 8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844

changed order of ip -6 line and dns-nameservers to add ipv6's, but in opposite order from resolv.conf (link using resolvconf program) to be on safe side. Added preferred_lft 0 to primary IPv6 to not use it as default.

I tried with and without the "down" lines, rebooting each time.

I looked at https://tools.bitfolk.com/wiki/IPv6 and changed the ordering of the ipv6 addresses. This works, at least for now.

I assume you are using the "down" lines to avoid problems when shutting down a host with multiple IP's?

Also, do you bother to register additional IPv6 addresses in your DNS. E.g., Linode has set up my new block to link to the old one, as seen under my Remote Access:

Public IP Pools mynewIPv6block/64 routed to myPrimary_IPv6

Lester