Skip to contentSkip to conversation

mangle

LARTC Eddie 6 participants 8 messages Dec 8, 2003

lore
Share & tools
lore
#1 lore raw

I mark everything on my internal interface. I have classes for incoming websurfing traffic which I use HTB to control the traffic. This is done on my internal NIC.

I also have classes on my external interface which controls my outgoing traffic such as web (port 80) and smtp (port 25). This is done on my external NIC.

Mike Fetherston

Quoted 10 lines

-----Original Message-----
From: Eddie [mailto:[email protected]]
Sent: Monday, December 08, 2003 10:02 AM
To: Mike
Subject: RE: [LARTC] mangle

So you put all rules on your internal interface?

Quoted 1 line · Mike

*This message was transferred with a trial version of

CommuniGate(tm)

Quoted 2 lines

Pro*

Quoted 1 line

In my case eth1 is my internal NIC. I'm giving certain groups of

IP's

Quoted 1 line
Quoted 1 line

certain amounts of bandwidth. If you're trying to give full

bandwidth

Quoted 1 line
Quoted 1 line

to ssh traffic, you could mark on destination port 22 and assign

that

Quoted 1 line
Quoted 1 line

mark to a flowid with full bandwidth. I believe you would still use

the

Quoted 6 lines
Quoted 6 lines

PREROUTING table to mark with.

Why do you want to give SSH traffic full bandwidth?

Mike Fetherston

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: Eddie [mailto:[email protected]]
Sent: Monday, December 08, 2003 9:53 AM
To: Mike
Subject: RE: [LARTC] mangle

ok that is how I have,if eth1 is external,this will shape traffic

for

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

all the lan people,right.
BUT what do I do to give me full bandwidth when I ssh remotely to

work

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

on the box.Will I use OUTPUT??
Thanks,it helped allot:-)realy

On Mon, 2003-12-08 at 16:31, Mike wrote:

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line

*This message was transferred with a trial version of

CommuniGate(tm)

Quoted 2 lines

Pro*

Quoted 1 line

I've been using PREROUTING to mark packets and it's been working

very

Quoted 3 lines
Quoted 3 lines

well.

iptables -t mangle -I PREROUTING -i eth1 -s $IP --j MARK

--set-mark

Quoted 9 lines
Quoted 9 lines

3

Quoted 4 lines
Quoted 4 lines

and if you're using HTB, this command:

tc filter add dev eth0 parent 1:0 protocol ip prio 2 handle 3 fw

flowid

Quoted 3 lines
Quoted 3 lines

1:13

will act on those marked packets. It's the 'handle 3' which

uses

Quoted 19 lines
Quoted 19 lines

the

Quoted 18 lines
Quoted 18 lines

--set-mark 3.

Mike Fetherston

Quoted 9 lines

-----Original Message-----
From: Eddie [mailto:[email protected]]
Sent: Monday, December 08, 2003 8:40 AM
To: lartc
Subject: [LARTC] mangle

Hi all
I have a linux gateway box,eth1 internet and eth0 lan Now I made my qdisk for eth1 but now I want to mark them with

iptables.

Quoted 4 lines

The thing it I dont now wht to use,-A FORWARD or PREROUTING? Please can someone help
thanks

Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

eddie

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:

http://lartc.org/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#2 lore raw
In reply to Eddie
Quoted 4 lines · Eddie

I have a linux gateway box,eth1 internet and eth0 lan
Now I made my qdisk for eth1 but now I want to mark them with iptables. The thing it I dont now wht to use,-A FORWARD or PREROUTING?

Check for the Kernel Packet Traveling Diagram at:
http://www.docum.org/stef.coene/qos/kptd/

You will see very clearly the path of packets traversing your Linux box, and will be able to know the exact place where to mark traffic.

Greetings.

Signature · 5 lines
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.0-test10-mm1)
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#3 lore raw
In reply to Eddie
Quoted 9 lines
Quoted 4 lines · Eddie

I have a linux gateway box,eth1 internet and eth0 lan
Now I made my qdisk for eth1 but now I want to mark them with iptables. The thing it I dont now wht to use,-A FORWARD or PREROUTING?

Check for the Kernel Packet Traveling Diagram at:
http://www.docum.org/stef.coene/qos/kptd/

Please note that this diagram is not valid for iptables.

When using iptables, packets that are "traversing" the linux box (forwarded trafic) do not go thru the INPUT and OUTPUT chains.

You'll find an iptable packet traversal diagram at :
http://www.knowplace.org/netfilter/packet_traversal.gif

Rgds,
Ronnie.

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#4 lore raw
In reply to Eddie

Whoa!! Back up the truck!

: > Check for the Kernel Packet Traveling Diagram at:
: > http://www.docum.org/stef.coene/qos/kptd/
:
: Please note that this diagram is not valid for iptables.

I think I disagree.

: When using iptables, packets that are "traversing" the linux box : (forwarded trafic) do not go thru the INPUT and OUTPUT chains.

The KPTD hosted on docum.org certainly does accurately reflect the traversal of iptables. Please send corrections if you find something wrong with the KPTD. This was a collective effort by Leonardo Balliache, Stef Coene, and some others on this very list.

It doesn't depict the relationship between iptables and bridging, but that is a well-known exception to this diagram.

: You'll find an iptable packet traversal diagram at :
: http://www.knowplace.org/netfilter/packet_traversal.gif

This is a fine picture, too, though, Ron.

-Martin

Signature · 5 lines
Martin A. Brown --- SecurePipe, Inc. --- [email protected]

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#5 lore raw
In reply to Eddie
Quoted 2 lines · Ronnie Garcia

Please note that this diagram is not valid for iptables.

I think you did not interpret the diagram correctly. For "iptables" you will have to focus just on the BLUE boxes with the CAPITAL names, and forget about the lowercase ones, that are for "ipchains".

And each packet entering the box will follow just one path, and this path is determined after the routing stage: any packet going through the box (neither generated nor destined to it) will go the path on the right, though the FORWARD chain of "iptables". From then on the travel is simple to follow.

Hope it helps.

Signature · 5 lines
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.0-test10-mm1)
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#6 lore raw
In reply to Eddie
Quoted 8 lines
Quoted 2 lines · Ronnie Garcia

Please note that this diagram is not valid for iptables.

I think you did not interpret the diagram correctly. For "iptables" you will have to focus just on the BLUE boxes with the CAPITAL names, and forget about the lowercase ones, that are for "ipchains".

My bad, thats right.
The diagram is a bit confusing like this, what about drawing two different diagrams, since ipchains and netfilter behave quite differently ?

I can send diff's if needed =)

Rgds,
Ronnie.

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#7 lore raw
In reply to Eddie

Hi,

i have two question about the diagram.

Quoted 4 lines

The KPTD hosted on docum.org certainly does accurately reflect the traversal of iptables. Please send corrections if you find something wrong with the KPTD. This was a collective effort by Leonardo Balliache, Stef Coene, and some others on this very list.

first: what does PDBB stand for? is this the point where the RPDB is asked?

second: isn't there a hook between the OUTPUT and the POSTROUTING chain, to handle the routing for packets generated by local processes? Descriped in Figure 3.3.2 from
http://www.policyrouting.org/PolicyRoutingBook/ONLINE/CH03.web.html

thx,
Jan Gerritsen
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿË™¨¥Šx%ŠË,S ùšŠYšŸ÷lõ¯ç–m§ÿÿ™¨¥™©ÿvÏZþy™¨¥™©ÿ–+-ŠwèþV«µÁÎY3ÿ†Ûiÿÿåj»\þŠà