* Fw: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem
@ 2005-04-06 9:35 Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2005-04-06 9:35 UTC (permalink / raw)
To: netdev; +Cc: yoann.allain
Begin forwarded message:
Date: Wed, 6 Apr 2005 02:28:56 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
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@osdl.org
Submitter: yoann.allain@thomson.net
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-04-06 9:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-06 9:35 Fw: [Bugme-new] [Bug 4449] New: IPSec tunnel forwarding problem Andrew Morton
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 NNTP newsgroup(s).