From: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
To: kmurari@embeddedinfotech.com
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT Issue
Date: Fri, 20 Apr 2007 21:21:24 +0900 (JST) [thread overview]
Message-ID: <200704201221.l3KCLO2c014678@toshiba.co.jp> (raw)
In-Reply-To: <4628AD71.7060101@embeddedinfotech.com>
From: Kiran Murari <kmurari@embeddedinfotech.com>
Date: Fri, 20 Apr 2007 17:39:21 +0530
> Yasuyuki KOZAKAI wrote:
> > From: Kiran Murari <kmurari@embeddedinfotech.com>
> > Date: Fri, 20 Apr 2007 16:38:32 +0530
> >
> >
> >> After little bit of experimenting, I could see that if I flush all the conntrack entries,
> >> as soon as my WAN is enabled, the PING session continued.
> >>
> >> But flushing all the conntrack entries, doesn't look like a feasible one.
> >>
> >> Is there a way to flush the conntrack entries that have been created during a specific interval.
> >>
> >> Any thoughts.
> >>
> >
> > Why don't you flush table with tool 'conntrack' just after bringing up your
> > WAN ?
> >
> > http://www.netfilter.org/projects/conntrack/index.html
> >
> > -- Yasuyuki Kozakai
> >
> Yeah I have seen the 'conntrack'.
> But this requires linnetfilter_conntrack and libnfnetlink support.
> I am running a 2.6.14 on an Xscale processor.
>
> So is there a means to flush the entries, other than porting the
> 'conntrack' to Xscale.
There is no way. Other solution in my mind is to set a filter rule
to drop all forwarded packets, just before bringing down WAN interface.
-- Yasuyuki Kozakai
next prev parent reply other threads:[~2007-04-20 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 11:08 NAT Issue Kiran Murari
2007-04-20 11:25 ` Yasuyuki KOZAKAI
[not found] ` <200704201125.l3KBPGSw018412@toshiba.co.jp>
2007-04-20 12:09 ` Kiran Murari
2007-04-20 12:21 ` Yasuyuki KOZAKAI [this message]
2007-04-20 20:54 ` Nagy Zoltan
-- strict thread matches above, loose matches on Subject: below --
2007-04-19 10:09 Kiran Murari
2007-04-19 22:24 ` Pascal Hambourg
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=200704201221.l3KCLO2c014678@toshiba.co.jp \
--to=yasuyuki.kozakai@toshiba.co.jp \
--cc=kmurari@embeddedinfotech.com \
--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