All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tóth Nándor" <nug@sch.bme.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] simple questions about imq
Date: Mon, 31 Jan 2005 16:59:24 +0000	[thread overview]
Message-ID: <41FE63EC.4090806@sch.bme.hu> (raw)
In-Reply-To: <41FD1304.1080305@sch.bme.hu>

Hi!

Andre Correa wrote:
> 
> Cool Toth, please let us know if you make it work. Just take care to 
> hook IMQ in the right place if you are doing NAT. You can choose to hook 
> it after or before NAT.

Where can i set it?
Can you answer my questions below?

I will document these things, if i managed to do it.

-- 
Udv,
   Nandor

> Tóth Nándor wrote:
> 
>> Hi!
>>
>> I have read all informations i could find, but some things are still 
>> not clear.
>>
>> My setup is:
>>  ---INTERNET1(eth0)-\  /- Local net1 (eth2)
>>                      GW
>>  ---INTERNET2(eth1)-/  \- Local net2 (eth3)
>>
>> I have NAT and a working setup using HTB,SFQ, classifying with the 
>> iptables -j CLASSIFY way. I shape only the traffic coming from the 
>> internet heading to the intranet.
>>
>> I would like to have a configuration like this:
>>  ---INTERNET1(eth0)-\        /- Local net1 (eth2)
>>                      GW--imq0
>>  ---INTERNET2(eth1)-/        \- Local net2 (eth3)
>>
>> I think it can be done this way:
>> iptables -t mangle -A PREROUTING -i eth0 -j IMQ --todev 0
>> iptables -t mangle -A PREROUTING -i eth1 -j IMQ --todev 0
>>
>> But it would include traffic heading to the gateway directly, wouldn't 
>> it? Can i put these rules to the POSTROUTING chain?
>>
>> And i can still have my CLASSIFY targets in the POSTROUTING chain, 
>> because IMQ queing will happen after it according to 
>> http://lartc.org/howto/lartc.imq.html.
>> So for example:
>> $IPTABLES -t mangle -A POSTROUTING -o $eth2 ... -j CLASSIFY 
>> --set-class 1:30
>> $IPTABLES -t mangle -A POSTROUTING -o $eth3 ... -j CLASSIFY 
>> --set-class 1:30
>> $IPTABLES -t mangle -A POSTROUTING -o $eth2 ... -j RETURN
>> $IPTABLES -t mangle -A POSTROUTING -o $eth3 ... -j RETURN
>>
>> If i managed to do this, i promise, i will document it to the imq wiki.
>>
>> Any advice/help is appreciated!
>>
> 


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

  parent reply	other threads:[~2005-01-31 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 16:58 [LARTC] simple questions about imq Tóth Nándor
2005-01-31 13:55 ` Andre Correa
2005-01-31 16:59 ` Tóth Nándor [this message]
2005-01-31 17:10 ` Andre Correa
2005-01-31 23:39 ` Andy Furniss
2005-02-01  5:44 ` Tóth Nándor

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=41FE63EC.4090806@sch.bme.hu \
    --to=nug@sch.bme.hu \
    --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.