From: asko askeltaja <klups@luukku.com>
To: lartc@vger.kernel.org
Subject: [LARTC] two nic's and iproute2
Date: Fri, 14 Feb 2003 19:38:25 +0000 [thread overview]
Message-ID: <marc-lartc-104525158803607@msgid-missing> (raw)
My previous message was confusing, so i try again..i want manage outgoing traffic with linuxpc/iproute2/HTB, but i am newbie with routing. Below is my "drawing", hope it helps :) So i want to put linuxpc between fw and LAN.
internet-------eth0[fw/NAT]eth1-------eth0[linuxpc]eth1-----LAN (10.2.0/20)
fw/NAT: eth1 10.2.0.1/20
linuxpc: eth0 10.2.0.2 and eth1 10.2.0.3
Linuxpc has kernel 2.4.20 and new tc, so i should be able to use HTB.
How should i route traffic from linuxpc eth1 to eth0, if i want to use qdisc's? What should i do before creating qdisc? Thank you for helping me.
regards,
Asko
............................................................
Maksuton sähköposti aina käytössä http://luukku.com
Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-02-14 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-104525158803607@msgid-missing \
--to=klups@luukku.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.