From: VladSun <vladsun@relef.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 classifier
Date: Sat, 02 Jun 2007 11:46:38 +0000 [thread overview]
Message-ID: <4661589E.8070100@relef.net> (raw)
In-Reply-To: <marc-lartc-105818475719019@msgid-missing>
terraja-based написа:
> Hi folks...!!!
> I´ve a problem that i did not solve it.
> i want to limit the DOWNLOAD to my hosts (upstream traffic for the
> firewall) using IMQ,
> If i classify by PORT (source or destination) all seems to be fine,
> but...BUT...if i want to restrict by IP addresss (internal IP address)
> i can´t do it, because my hosts go to Internet toward the firewall
> using NAT, so after NAT my IP address in Internet is not my internal
> address, because the NAT acction change my source and internal IP
> address.
> So...so...so...how can i limit the traffic by IP address using TC,
> IMQ, U32..etc...?????
> Can i modify some field in the TCP header with u32 filter?, i did read
> the TCP RFC and nothing, i can´t guess how can solve it...
> Please, HELPPPPPPP ME...!!!
>
>
> --
> terraja-based
> ------------------------------------------------------------------------
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
Use iptables MARK, and TC fw.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-02 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 12:11 [LARTC] u32 classifier Andreani Luca
2007-06-02 9:19 ` terraja-based
2007-06-02 10:31 ` Afshin Tajvidi
2007-06-02 11:46 ` VladSun [this message]
2007-06-06 13:19 ` Catalin Bucur
2007-06-06 13:50 ` VladSun
2007-06-06 14:00 ` Catalin Bucur
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=4661589E.8070100@relef.net \
--to=vladsun@relef.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.