All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Confuse, putting packets in wrong mangle table.
Date: Tue, 25 Jan 2005 12:41:31 +0000	[thread overview]
Message-ID: <41F63E7B.30202@dsl.pipex.com> (raw)
In-Reply-To: <200501191657.15767.rio@martin.mu>

Rio Martin. wrote:
> On Wed, 19 Jan 2005 09:19:58 +0100  Tóth Nándor <nug@sch.bme.hu> wrote:
> Rio Martin. wrote:
> 
>>>Folks,
>>>I am a little bit confuse in how to put these packets into correct mangle 
>>>table for traffic shaping.
>>>This is what i ve planned to do:
>>>
>>>- - - - :eth0 [ LINUX-BOX ] eth1: - - - -
>>>
>>>Let say:
>>>eth0: 220.100.1.1
>>>eth1: 192.168.1.1
>>>eth1:1 192.168.1.2
>>>
>>>192.168.1.0/24 get natted into 220.100.1.1 before reaching the internet.
>>>I put every packets coming from internet (eth0) this way:
>>># iptables -t mangle -I PREROUTING -i eth0 .. * * * *
>>>
>>>But what if i would like to do the same way with ip 192.168.1.1 and 
>>>192.168.1.2 ? How to put the packets in correct mangle table?
>>
>>You can only shape traffic leaving your interface. You have to shape the 
>>incoming traffic at interface eth1, the outgoing traffic at interface eth0.
>>This site is great for learning:
>>http://www.knowplace.org/shaper/qdisc.html#egress
>>I found to use iptables+CLASSIFY method the easiest way to classify packets.
>>
>>Your question is a little dizzy...
> 
> 
> Oopss sorry then :))
> 
> Actually, there is squid proxy running in my box, with those two private IPs 
> (192.168.1.1 & 192.168.1.2)
> Both get natted to 220.100.1.1.

Is there only one proxy running?

> 
> I need to shape incoming traffic to both of these ips but i am affraid i have 
> to face that i am not able to shape traffic which is generate from this box 
> unless those two IPs were outside the box.

Maybe true - maybe not you would need to test with imq.
There is also a kernel option to do with nat of local connections.

> 
> If i have one more public IP than i should not so much worry about, cause i 
> can shape it using IMQ.
> 
> So any other ideas maybe? i'm thinkin just in case IMQ would help ..

Possibly - but I don't understand your setup or what you want to shape :-)

> Thanks for the info u gave anyway..
> 
> - Rio.Martin -
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2005-01-25 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 10:05 [LARTC] Re: Confuse, putting packets in wrong mangle table Rio Martin.
2005-01-25 12:41 ` Andy Furniss [this message]
2005-01-26 11:08 ` Rio Martin.
2005-01-27 12:37 ` Andy Furniss
2005-01-28  6:48 ` Rio Martin.
2005-01-29  0:55 ` Andy Furniss
2005-01-29 11:30 ` Rio Martin.
2005-01-31 23:17 ` Andy Furniss
2005-02-01  5:41 ` Rio Martin.
2005-02-05 12:30 ` Andy Furniss

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=41F63E7B.30202@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.