I have scoured the internet for days, but I cannot find a coherent
guide that is understandable to me for configuring a static ipv6
address on debian 11/bullseye.

I have been given the following from my datacenter:

Assigned IP range: 2604:xxxx:xxxx:xxxx::2/64 - 2604:xxxx:xxxx:xxxx:ffff:ffff:ffff:ffff
Subnet Mask: /64
Gateway Address: 2604:xxxx:xxxx:xxxx::1/64

I have read countless guides but it is still not clear to me how to
get ipv6 working, because no matter what I try I get "network
unreachable" when I try to ping6.

IPv4 works on eno1. All I want is to just assign 2604:blahblah:2 to
eno1, but so far have been unable.

The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6:
connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren <nathan.vany@gmail.com> wrote:

The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6: connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

Hi Nathan,

I think the first important step is to ensure that the gateway pingable
at its 2604:xxxx:xxxx:xxxx::1 address, both from your computer and from the internet.

Regards,
Andika

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren &lt;<a href="mailto:nathan.vany@gmail.com">nathan.vany@gmail.com</a>&gt; wrote:<br></div><blockquote
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The relevant portion of /etc/network/interfaces is:<br>

iface eno1 inet6 static<br>
        address 2604:xxxx:xxxx:xxxx::2/64<br>
        gateway 2604:xxxx:xxxx:xxxx::1<br>

As far as I can tell from reading the debian wiki and whatever else,<br>
it should work like this, but even ping6&#39;ing the gateway gives &quot;ping6:<br>
connect: Network is unreachable&quot;.  I can ping the gateway on its<br> link-local (fe80) address, but that&#39;s all I can do.<br>

Please help!<br>
<br></blockquote><div><br></div><div>Hi Nathan,</div><div><br></div><div>I think the first important step is to ensure that the gateway pingable</div><div>at its <span style="font-family:Arial,Helvetica,sans-serif">2604:xxxx:xxxx:xxxx::1</span><span
style="font-family:Arial,Helvetica,sans-serif"> </span><span style="font-family:Arial,Helvetica,sans-serif">address, both from your computer and from the internet.</span></div><div><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><

Regards,</div><div>Andika</div><div><br></div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Andika,

Thanks for your reply. I can ping the v6 gateway from my laptop at home/outside the datacenter, but I cannot ping it from the server.

On Wed, Feb 23, 2022 at 8:24 PM Andika Triwidada <andika@gmail.com> wrote:

On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren <nathan.vany@gmail.com> wrote:

The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6:
connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

Hi Nathan,

I think the first important step is to ensure that the gateway pingable
at its 2604:xxxx:xxxx:xxxx::1 address, both from your computer and from the internet.

Regards,
Andika

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, Feb 23, 2022 at 8:24 PM Andika Triwidada <andika@gmail.com> wrote:

On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren <nathan.vany@gmail.com> wrote:

The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6:
connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

Hi Nathan,

I think the first important step is to ensure that the gateway pingable
at its 2604:xxxx:xxxx:xxxx::1 address, both from your computer and from the internet.

Regards,
Andika

Sigh.

It seems that the missing piece of the puzzle was this: You can't
just add a default route (apparently). You have to first add the
route to a specific interface. It's not clear to me if this is
universally true, or just a consequence of something specific to my
setup (the server in question has multiple NICs).

The tl;dr is that it's necessary for me to do the following in order:

# ip -6 route add blah:blah::1 dev eno1
# ip -6 route add default via blah:blah::1

where blah:blah::1/64 is the address my datacenter gave me for the v6
gateway router.

I wish this had been more clearly laid out in the umpteen different
wikis and tutorials I've tried to follow.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Feb 23, 2022, at 21:40, Nathan Van Ymeren <nathan.vany@gmail.com> wrote:

On Wed, Feb 23, 2022 at 8:24 PM Andika Triwidada <andika@gmail.com> wrote:

On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren <nathan.vany@gmail.com> wrote:


The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6:
connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

Hi Nathan,

I think the first important step is to ensure that the gateway pingable
at its 2604:xxxx:xxxx:xxxx::1 address, both from your computer and from the internet.

Regards,
Andika

Sigh.

It seems that the missing piece of the puzzle was this: You can't
just add a default route (apparently). You have to first add the
route to a specific interface. It's not clear to me if this is
universally true, or just a consequence of something specific to my
setup (the server in question has multiple NICs).

The tl;dr is that it's necessary for me to do the following in order:

# ip -6 route add blah:blah::1 dev eno1
# ip -6 route add default via blah:blah::1

where blah:blah::1/64 is the address my datacenter gave me for the v6
gateway router.

I wish this had been more clearly laid out in the umpteen different
wikis and tutorials I've tried to follow.

That’s not documented because it’s not normal to have to add such a route. The kernel automatically adds that route. There is something wrong with your configuration. If you don’t obfuscate the information, we might be able to tell what’s wrong.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Feb 23, 2022, at 23:41, Kenyon Ralph <kenyon@kenyonralph.com> wrote:

On Feb 23, 2022, at 21:40, Nathan Van Ymeren <nathan.vany@gmail.com> wrote: >>
On Wed, Feb 23, 2022 at 8:24 PM Andika Triwidada <andika@gmail.com> wrote:

On Thu, Feb 24, 2022 at 10:58 AM Nathan Van Ymeren <nathan.vany@gmail.com> wrote:


The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else,
it should work like this, but even ping6'ing the gateway gives "ping6: >>>> connect: Network is unreachable". I can ping the gateway on its
link-local (fe80) address, but that's all I can do.

Please help!

Hi Nathan,

I think the first important step is to ensure that the gateway pingable
at its 2604:xxxx:xxxx:xxxx::1 address, both from your computer and from the internet.

Regards,
Andika

Sigh.

It seems that the missing piece of the puzzle was this: You can't
just add a default route (apparently). You have to first add the
route to a specific interface. It's not clear to me if this is
universally true, or just a consequence of something specific to my
setup (the server in question has multiple NICs).

The tl;dr is that it's necessary for me to do the following in order:

# ip -6 route add blah:blah::1 dev eno1
# ip -6 route add default via blah:blah::1

where blah:blah::1/64 is the address my datacenter gave me for the v6
gateway router.

I wish this had been more clearly laid out in the umpteen different
wikis and tutorials I've tried to follow.

That’s not documented because it’s not normal to have to add such a route. The kernel automatically adds that route. There is something wrong with your configuration. If you don’t obfuscate the information, we might be able to tell what’s wrong.

I suppose v6 addresses aren’t really private. The server is on 2604:5800:0:1f::2 and the gateway I was given is 2604:5800:0:1f::1

# route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If localhost/128 [::] U 256 2 0 lo 2604:5800:0:1f::1/128 [::] U 1024 1 0 eno1
2604:5800:0:1f::2/128 [::] U 256 2 0 eno1 fe80::/64 [::] U 256 1 0 eno1 [::]/0 2604:5800:0:1f::1 UG 1024 21 0 eno1
localhost/128 [::] Un 0 27 0 lo 2604:5800:0:1f::2/128 [::] Un 0 10 0 eno1
fe80::/128 [::] Un 0 3 0 eno1 fe80::28c:faff:fe0e:b01c/128 [::] Un 0 7 0 eno1 ff00::/8 [::] U 256 5 0 eno1 [::]/0 [::] !n -1 1 0 lo root@mars:/etc/postfix#

N

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 24/02/2022 à 08:45, Nathan Van Ymeren a écrit :

The relevant portion of /etc/network/interfaces is:

iface eno1 inet6 static
address 2604:xxxx:xxxx:xxxx::2/64
gateway 2604:xxxx:xxxx:xxxx::1

As far as I can tell from reading the debian wiki and whatever else, >>>>> it should work like this

Yes.

but even ping6'ing the gateway gives "ping6:
connect: Network is unreachable".

It seems that the missing piece of the puzzle was this: You can't
just add a default route (apparently).

You can as long as the router's address is in the interface prefix.

You have to first add the
route to a specific interface. It's not clear to me if this is
universally true,

It is not.

or just a consequence of something specific to my
setup (the server in question has multiple NICs).

I see only one interface eno1 in the routing table below.

# ip -6 route add blah:blah::1 dev eno1
# ip -6 route add default via blah:blah::1

where blah:blah::1/64 is the address my datacenter gave me for the v6
gateway router.

That should not be necessary.

I suppose v6 addresses aren’t really private. The server is on 2604:5800:0:1f::2 and the gateway I was given is 2604:5800:0:1f::1

# route -A inet6

The output of "ip -6 route" is more compact and readable.

Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If localhost/128 [::] U 256 2 0 lo 2604:5800:0:1f::1/128 [::] U 1024 1 0 eno1
2604:5800:0:1f::2/128 [::] U 256 2 0 eno1
fe80::/64 [::] U 256 1 0 eno1
[::]/0 2604:5800:0:1f::1 UG 1024 21 0 eno1
localhost/128 [::] Un 0 27 0 lo
2604:5800:0:1f::2/128 [::] Un 0 10 0 eno1
fe80::/128 [::] Un 0 3 0 eno1
fe80::28c:faff:fe0e:b01c/128 [::] Un 0 7 0 eno1
ff00::/8 [::] U 256 5 0 eno1
[::]/0 [::] !n -1 1 0 lo

The direct route for 2604:5800:0:1f::/64 which shoud have been created
by the quoted portion of /etc/network/interfaces is missing.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

(Whoops, replied off-list by accident, sorry Pascal for the dupe)

---

On Feb 24, 2022, at 13:01, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:

That should not be necessary.

Okay, well, it’s the only way I’ve been able to get it working.

The direct route for 2604:5800:0:1f::/64 which shoud have been created by the quoted portion of /etc/network/interfaces is missing.

I believe you, but I’m no closer to understanding why that’s the case, nor how to rectify the situation.

N

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)