From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why dont packets go where i want?
Date: Thu, 17 Oct 2002 13:25:21 +0000 [thread overview]
Message-ID: <marc-lartc-103486132610927@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103484229426470@msgid-missing>
Kertész Viktor wrote:
>I think we are out of sync about what outgoing traffic means. :) (and i am
>sure i am wrong) When traffic goes through the gw, outgoing traffic means to
>the gw that packets leave it's eth1 nic, isn't it? From wondershaper i just
>took examples. Of course wondershaper shapes outgoing traffic with htb. Once
>more, i download on the client machine, not on the gw. Thanks for replies!
>:)
>
>
Outgoing traffic to _any_ machine is the traffic that is /leaving/ _any_
of its network interfaces.
--
Michael T. Babcock
C.T.O., FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-17 13:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 8:09 [LARTC] why dont packets go where i want? Kertész Viktor
2002-10-17 8:36 ` Francois Dessart
2002-10-17 8:38 ` Francois Dessart
2002-10-17 9:01 ` Kertész Viktor
2002-10-17 9:09 ` Walter Haidinger
2002-10-17 9:29 ` Kertész Viktor
2002-10-17 9:44 ` Francois Dessart
2002-10-17 10:02 ` Walter Haidinger
2002-10-17 10:26 ` Kertész Viktor
2002-10-17 10:44 ` Stef Coene
2002-10-17 11:01 ` Walter Haidinger
2002-10-17 12:16 ` Kertész Viktor
2002-10-17 13:20 ` Walter Haidinger
2002-10-17 13:25 ` Michael T. Babcock [this message]
2002-10-17 16:00 ` James Sneeringer
2002-10-17 20:04 ` Walter Haidinger
2002-10-18 6:21 ` Francois Dessart
2002-10-18 6:41 ` Stef Coene
2002-10-18 17:42 ` James Sneeringer
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-103486132610927@msgid-missing \
--to=mbabcock@fibrespeed.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.