From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Incoming ESP Packets disappear
Date: Mon, 04 May 2020 16:03:13 +0100 [thread overview]
Message-ID: <DF9C2BC1-0F57-4B23-9810-17004E6CA60A@ipfire.org> (raw)
In-Reply-To: <de3b625a-dae3-b5bb-96d3-cf084f911b85@md5collisions.eu>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
Hi Stephan,
What is the output of “ipsec statusall” on both systems?
Best,
-Michael
> On 30 Apr 2020, at 22:28, Stephan Mending <list(a)md5collisions.eu> wrote:
>
> Hello,
>
> I have a situation. ;)
>
> It looks like the following:
>
>
> (SRV-01) ----------- (IPFIRE) -------orange------- (SRV-02)
>
> public-IP 192.168.0.100
>
>
> SRV-01 is hooked up to the ipfire via a roadwarrior IPsec connection. Establishment of the tunnel works as one would expect it.
>
> ping from SRV-02 to SRV-01 works fine and passes through the tunnel. So far, so good.
>
> ping from SRV-01 to SRV-02 does not.
>
>
> Iptables is blocking ? No, I did check that. Nothing.
>
> IPS ? No, neither.
>
>
> So what's the matter ? When watching the interface using tcpdump I can see ESP packets and afterwards its unencrypted icmp echo request content (both on ppp0). That is the end.
>
> And the packet has never been seen any after.
>
> Anyone an idea?
>
>
> (Yes the SRV-02 accepts incoming icmp type 8 and outgoing type 0)
>
>
> Best regards,
>
> Stephan
>
>
next parent reply other threads:[~2020-05-04 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <de3b625a-dae3-b5bb-96d3-cf084f911b85@md5collisions.eu>
2020-05-04 15:03 ` Michael Tremer [this message]
2020-05-13 13:13 ` Stephan Mending
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=DF9C2BC1-0F57-4B23-9810-17004E6CA60A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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