From: Wouter Vanwalleghem <wouter@belnet.be>
To: netfilter@lists.netfilter.org
Subject: Unable to stop tunnel from being "connection-tracked"
Date: 02 Oct 2003 13:10:09 +0200 [thread overview]
Message-ID: <1065093009.24289.193.camel@wouter.fw.belnet.be> (raw)
hi all,
I have setup a 6-in-4 tunnel which is giving me head-aches.
FYI, I use kernel 2.4.21 and iptables 1.2.8.
As soon as I start using the tunnel the output of "cat
/proc/net/ip_conntrack" shows a protocol 41 connection between my
firewall and the IPv4 PoP of the tunnelbroker.
OK so far.
But if I then stop using the tunnel, above-mentioned connection
disappears from the connection tracking table after 600 seconds.
Normal behaviour.
Thing is that the tunnel "dies" as soon as the connection has
disappeared from the connection tracking table.
After some research I followed a suggestion to keep the tunnel from
being connection tracked.
However, the following iptables rules do not prevent the tunnel from
popping up in the connection tracking table:
#####------------ IPv6 tunnel to SixXS-----
iptables -A INPUT -p 41 -s tunnelserver.concepts-ict.net -j ACCEPT
iptables -A OUTPUT -p 41 -d tunnelserver.concepts-ict.net -j ACCEPT
iptables -A INPUT -p icmp --icmp-type echo-request -s
tunnelserver.concepts-ict.net -j ACCEPT
iptables -t nat -A POSTROUTING --protocol ! 41 -s 192.168.100.0/24 -o
ppp0 -j MASQUERADE
The ip6tables tables are all empty and all policies are set to ACCEPT.
I cannot do without the MASQUERADE'ing rule because I still want my LAN
to have connectivity.
Anybody have a clue?
TIA
kind regards,
Wouter
next reply other threads:[~2003-10-02 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 11:10 Wouter Vanwalleghem [this message]
2003-10-02 13:52 ` Unable to stop tunnel from being "connection-tracked" Ramin Dousti
2003-10-02 19:35 ` Wouter Vanwalleghem
2003-10-03 10:16 ` Harald Welte
2003-10-03 19:43 ` Ramin Dousti
2003-10-03 20:02 ` Wouter Vanwalleghem
2003-10-03 10:15 ` Harald Welte
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=1065093009.24289.193.camel@wouter.fw.belnet.be \
--to=wouter@belnet.be \
--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