From: Ramin Alidousti <ramin@cannon.eng.us.uu.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem in advanced routing with FTP
Date: Thu, 21 Nov 2002 15:28:35 +0000 [thread overview]
Message-ID: <marc-lartc-103789269626693@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103789115124699@msgid-missing>
I believe you can use the "helper" module:
http://www.iptables.org/documentation/pomlist/pom-submitted.html#helper
and mark the related packets like so:
iptables -t mangle -A PREROUTING -m helper --helper ftp -j MARK --set-mark 2
This is just an idea and I have not tested this solution personally.
Ramin
On Thu, Nov 21, 2002 at 03:07:54PM +0000, Nuno Miguel Pais Fernandes wrote:
> I have a router with 2 isp's connected.
>
> My default route is by isp1, and i mark packets to port 80 and port 21
> with mark 2.
>
> with: ip rule ls
>
> 0: from all lookup local
> 32765: from all fwmark 2 lookup 200
> 32766: from all lookup main
> 32767: from all lookup 253
>
> and in table 200 i have the route by isp2.
>
> My http traffic goes well, but ftp doesn't.
> Using Passive mode all works well, but with active it doest work,
> because the ftp server callsback with port 20.
> Please note that isp2 is masqueraded and i have ip_conntrack_ftp in the
> kernel.
>
> Thanks for any advice.
>
> Nuno Fernandes
>
>
> --
> Nuno Miguel Pais Fernandes <npf@eurotux.com>
> Eurotux S.A.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-21 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 15:07 [LARTC] Problem in advanced routing with FTP Nuno Miguel Pais Fernandes
2002-11-21 15:28 ` Ramin Alidousti [this message]
2002-11-21 19:06 ` Stef Coene
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=marc-lartc-103789269626693@msgid-missing \
--to=ramin@cannon.eng.us.uu.net \
--cc=lartc@vger.kernel.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