From: Grant Taylor <gtaylor@tnetconsulting.net>
To: Linux Advanced Routing & Traffic Control <lartc@vger.kernel.org>
Subject: Re: Ping over IPv6 IP6IP6 tunnels not working
Date: Wed, 27 Mar 2024 22:36:46 -0500 [thread overview]
Message-ID: <6a920308-9b3c-45cb-b0ca-587a378f6705@tnetconsulting.net> (raw)
In-Reply-To: <f7ae26b3-4a90-47ee-8d73-99be66651346@mmeacs.de>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On 3/22/24 05:57, Martin Maurer wrote:
> Hello,
Hi,
> I am using 2 Raspberry Pis and trying to establish tunnels: 2 for IPv4
> and 2 for IPv6. I used separate ones, so in sum 4 tunnels.
I'm not sure why you're using two tunnels, but I seriously doubt that's
causing any problems for you.
> I have done the following changes/calls:
I've quickly skimmed your commands and don't see anything that stands
out as obviously wrong.
> $ sudo ping -6 -I mytunnel1ipv6 2001:4860:4860::8888
> ping: connect: Network is unreachable
> $ sudo ping -6 -I mytunnel2ipv6 2001:4860:4860::8888
> ping: connect: Network is unreachable
> $
I think "Network is unreachable" means that the kernel doesn't think it
has a viable route to the network.
> I can also ping the "outer" (real) addresses:
Can you ping the inner IP address on the far side of the IP-IP tunnel?
If you can't ping the IP that you're trying to use as a gateway to get
to the 2001::/4 network, the kernel would think that it doesn't have a
functioning route.
> I know the 2001::/4 in "route add" is not useable for all Internet IPv6
> addresses, but at least for these test pings that shall be enough?
Agreed.
> Someone an idea, what could be wrong/missing?
Start with basics, can you ping the far inside IP of the tunnel(s).
> Many thanks!
:-)
--
Grant. . . .
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4033 bytes --]
next prev parent reply other threads:[~2024-03-28 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 10:57 Ping over IPv6 IP6IP6 tunnels not working Martin Maurer
2024-03-28 3:36 ` Grant Taylor [this message]
2024-03-28 10:29 ` Erik Auerswald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a920308-9b3c-45cb-b0ca-587a378f6705@tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).