Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Fernando Montenegro <fsmontenegro@yahoo.ca>
To: netfilter@lists.netfilter.org
Subject: Help needed with ESP and DNAT on Debian 2.4.26 / iptables 1.2.9-10
Date: Sat, 28 Aug 2004 12:37:48 -0400	[thread overview]
Message-ID: <4130B4DC.30504@yahoo.ca> (raw)

Hi there!

I need help getting DNAT to work with ESP packets on a Debian box
('testing/sarge' release, 2.4.26 kernel, iptables 1.2.9-10). This used 
to work fine on a RH90...

This is used to suport a laptop running XP Pro logging in to a corporate
VPN with the Nortel VPN client. Company policy and authentication
requirements prevent me from changing anything in that setup (so I can't
change the VPN to terminate AT the Linux box for example).

My problem is: incoming ESP packets are not being DNATed as I wanted
them to. The rule I use is:
-A PREROUTING -p esp -s <VPN server> -j DNAT --to-destination <laptop>

The rule does get hit into (I have a mirror rule with -j LOG), but the
translation does NOT happen.

Like I said, it used to work fine when the server was a RH90.

How do I begin troubleshooting this? Some things I tried so far are:
- try to DNAT ALL traffic (not just -p esp)
- force ipt_esp to load (modprobe ipt_esp and yes, it is under
/lib/modules/<kernel>/kernel/ipv4/netfilter)
- tried doing an SNAT on the preceding UDP/500 connection to maybe trick
netfilter into understanding the ESP part later

Naturally, I have tcpdump logs, syslogs, etc... for further analysis,
but I'm weak when it comes to netfilter troubleshooting...

Help!

Thanks in advance.

Cheers,
Fernando
-- 
Fernando Montenegro, CISSP  -  fsmontenegro@yahoo.ca
Markham, Ontario, Canada




             reply	other threads:[~2004-08-28 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28 16:37 Fernando Montenegro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28 18:19 Help needed with ESP and DNAT on Debian 2.4.26 / iptables 1.2.9-10 Jason Opperisano
2004-08-30  0:22 ` Alexander Samad

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=4130B4DC.30504@yahoo.ca \
    --to=fsmontenegro@yahoo.ca \
    --cc=netfilter@lists.netfilter.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