From: Martin Cheatle <marche@systems-pro.net>
To: netfilter@lists.netfilter.org
Subject: ipsec connection problems though netfilter.
Date: Sun, 10 Jun 2007 14:05:41 +0100 [thread overview]
Message-ID: <466BF725.3010000@systems-pro.net> (raw)
My Network
internet
|
+----------------------+
| |
eth2 |
| |
Firewall-eth1-----netB----ISA
|
eth0
|
netA
Firewall Rules
iptables -t nat -A POSTROUTING -o eth2 -j SNAT --to-source 'external ip
address'
iptables -A FORWARD -i eth0 -o eth2 -m state --state
NEW,RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i eth2 -o eth0 -m state --state RELATED,ESTABLISHED
-j ACCEPT
iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
MS/ISA Server listening for ipsec/l2tp on both adapters
My Problem
If I connect a MS/XP client to the MS/ISA server via ipsec/l2tp directly
from netB or the internet every thing works fine.
If I try to connect from netA through to netB the client fails to connect.
If try to connect from netA to the MS/ISA server via the internet
address all works ok.
The only difference in my rules is that the traffic gets NAT'ed on the
way out to the internet.
I have tried NATing the traffic leaving the firewall on eth1 but this
did not resolve the issue.
I have added -m state rules from eth0 to eth1 and back, this did not help.
The only difference I have seen in the traffic between the connections
through the firewall is a ip-fragment between netA and netB during the
isakmp stage of the connection both then procced to start ESP traffic.
Has anyone seen this type of problem before?
Eventually I do want to remove the ISA server of the internet and route
the ipsec/l2tp traffic through the firewall but I can't do that until i
can get this bit working.
Thanks in advance
Martin
next reply other threads:[~2007-06-10 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 13:05 Martin Cheatle [this message]
2007-06-12 15:42 ` ipsec connection problems though netfilter Jorge Davila
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=466BF725.3010000@systems-pro.net \
--to=marche@systems-pro.net \
--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