netdev
[Top] [All Lists]

Fw: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem

To: netdev@xxxxxxxxxxx
Subject: Fw: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem
From: Andrew Morton <akpm@xxxxxxxx>
Date: Wed, 6 Apr 2005 02:35:15 -0700
Cc: yoann.allain@xxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx

Begin forwarded message:

Date: Wed, 6 Apr 2005 02:28:56 -0700
From: bugme-daemon@xxxxxxxx
To: bugme-new@xxxxxxxxxxxxxx
Subject: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem


http://bugme.osdl.org/show_bug.cgi?id=4449

           Summary: IPSec tunnel forwarding problem
    Kernel Version: 2.6.11-uml
            Status: NEW
          Severity: blocking
             Owner: shemminger@xxxxxxxx
         Submitter: yoann.allain@xxxxxxxxxxx


Distribution: Debian sarge 
Hardware Environment: x86
Software Environment: ipsec-tools-0.5
Problem Description:  IP packets that should be forwarded after being decrypted
out of a IPSec tunnel are not forwarded.

Steps to reproduce: Lets take three hosts A B and C:
B is the gateway between A and C.

A<------->B<------->C

First check that ping from A to C are working. If not check forwarding options 
in B.

Then create an Ipsec tunnel between two hosts A and B.

A<========>B<------->C

Once the IPSec tunnel established, and iptables configured on B to print logs
(for hooks Input Forward and Pre-Routing), try again to ping C from A.

You should see that packets arrives to B in ESP format and goes to:

hook

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

<Prev in Thread] Current Thread [Next in Thread>
  • Fw: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem, Andrew Morton <=