From: "Mike" <mike@superiorholidayadventures.ca>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] mangle
Date: Mon, 08 Dec 2003 15:00:46 +0000 [thread overview]
Message-ID: <marc-lartc-107089579123011@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107089337719633@msgid-missing>
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
> -----Original Message-----
> From: Eddie [mailto:eddieknows@ananzi.co.za]
> Sent: Monday, December 08, 2003 10:02 AM
> To: Mike
> Subject: RE: [LARTC] mangle
>
> So you put all rules on your internal interface?
>
> On Mon, 2003-12-08 at 16:43, Mike wrote:
> > *This message was transferred with a trial version of
CommuniGate(tm)
> Pro*
> > In my case eth1 is my internal NIC. I'm giving certain groups of
IP's
> > certain amounts of bandwidth. If you're trying to give full
bandwidth
> > to ssh traffic, you could mark on destination port 22 and assign
that
> > mark to a flowid with full bandwidth. I believe you would still use
the
> > PREROUTING table to mark with.
> >
> > Why do you want to give SSH traffic full bandwidth?
> >
> > Mike Fetherston
> >
> > > -----Original Message-----
> > > From: Eddie [mailto:eddieknows@ananzi.co.za]
> > > 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
> > > all the lan people,right.
> > > BUT what do I do to give me full bandwidth when I ssh remotely to
work
> > > on the box.Will I use OUTPUT??
> > > Thanks,it helped allot:-)realy
> > >
> > >
> > > On Mon, 2003-12-08 at 16:31, Mike wrote:
> > > > *This message was transferred with a trial version of
> > CommuniGate(tm)
> > > Pro*
> > > > I've been using PREROUTING to mark packets and it's been working
> > very
> > > > well.
> > > >
> > > > iptables -t mangle -I PREROUTING -i eth1 -s $IP --j MARK
--set-mark
> > 3
> > > >
> > > > and if you're using HTB, this command:
> > > >
> > > > tc filter add dev eth0 parent 1:0 protocol ip prio 2 handle 3 fw
> > flowid
> > > > 1:13
> > > >
> > > > will act on those marked packets. It's the 'handle 3' which
uses
> > the
> > > > --set-mark 3.
> > > >
> > > > Mike Fetherston
> > > >
> > > > > -----Original Message-----
> > > > > From: Eddie [mailto:eddieknows@ananzi.co.za]
> > > > > 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.
> > > > > The thing it I dont now wht to use,-A FORWARD or PREROUTING?
> > > > > Please can someone help
> > > > > thanks
> > > > >
> > > > > eddie
> > > > >
> > > > > _______________________________________________
> > > > > 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/
next prev parent reply other threads:[~2003-12-08 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 13:39 [LARTC] mangle Eddie
2003-12-08 15:00 ` Mike [this message]
2003-12-08 15:07 ` Jose Luis Domingo Lopez
2003-12-08 16:18 ` Ronnie Garcia
2003-12-08 17:45 ` Martin A. Brown
2003-12-08 18:25 ` Jose Luis Domingo Lopez
2003-12-08 19:15 ` Ronnie Garcia
2003-12-08 20:06 ` AW: " Jan Gerritsen
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-107089579123011@msgid-missing \
--to=mike@superiorholidayadventures.ca \
--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.