Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #257083

Re: ICMP router advertisement (ipv4)

From Anssi Saari <as@sci.fi>
Newsgroups linux.debian.user
Subject Re: ICMP router advertisement (ipv4)
Date 2023-04-12 08:50 +0200
Message-ID <GjCsO-1tXb-3@gated-at.bofh.it> (permalink)
References (6 earlier) <Gj8l4-1b0V-7@gated-at.bofh.it> <Gjdb3-1dTk-9@gated-at.bofh.it> <Gjdup-1eeX-9@gated-at.bofh.it> <Gjkmd-1ixD-3@gated-at.bofh.it> <GjmxH-1jRO-5@gated-at.bofh.it>
Organization An impatient and LOUD arachnid

Show all headers | View raw

Dan Ritter <dsr@randomstring.org> writes:

> Tunnelbroker.net can use a dynamic update feature so that the
> static IPv6 address is only momentarily interrupted when the
> underlying v4 address is changed out. This is quite reliable if
> you hook it to the the DHCP client's post-up function.

I don't understand the relevance. Does tunnelbroker.net offer some other
kind of tunnels than 6to4 which, AFAICT, don't work without a public
IPv4 address? Which the OP does not have due to his IPv4-in-IPv6
connection. Same goes for 6in4 tunnels. I can't seem to find out what
Hurricane Electric offers without sigining up though but at least
https://forums.he.net/index.php?topic=4195.0 from last year seems to
indicate WireGuard tunnels are not supported.

If "public IPv4 address" is not understood by you it can also be
formulated as "the OP has an RFC1918 IPv4 address which is not routable
on the public internet and hence a 6to4 tunnel can't work for him."

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-09 09:40 +0200
  Re: ICMP router advertisement (ipv4) Michel Verdier <mv524@free.fr> - 2023-04-09 10:40 +0200
    Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-09 17:30 +0200
      Re: ICMP router advertisement (ipv4) Michel Verdier <mv524@free.fr> - 2023-04-09 21:40 +0200
        Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 05:10 +0200
          Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-10 05:20 +0200
            Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 06:50 +0200
              Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-10 07:00 +0200
                Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 20:30 +0200
                Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-11 00:40 +0200
                Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-11 05:50 +0200
                Re: ICMP router advertisement (ipv4) Jeremy Ardley <jeremy@ardley.org> - 2023-04-11 06:10 +0200
                Re: ICMP router advertisement (ipv4) debian-user@howorth.org.uk - 2023-04-11 10:30 +0200
                Re: ICMP router advertisement (ipv4) Anssi Saari <as@sci.fi> - 2023-04-11 13:30 +0200
                Re: ICMP router advertisement (ipv4) Dan Ritter <dsr@randomstring.org> - 2023-04-11 15:50 +0200
                Re: ICMP router advertisement (ipv4) Anssi Saari <as@sci.fi> - 2023-04-12 08:50 +0200
                Re: ICMP router advertisement (ipv4) Dan Ritter <dsr@randomstring.org> - 2023-04-12 12:40 +0200
              Re: ICMP router advertisement (ipv4) Tim Woodall <debianuser@woodall.me.uk> - 2023-04-10 07:00 +0200

csiph-web