From: Henrik Johansson - GlobeCom <hj@globecom.se>
To: lartc@vger.kernel.org
Subject: [LARTC] Bad performance using source routing
Date: Sun, 27 Oct 2002 15:11:14 +0000 [thread overview]
Message-ID: <marc-lartc-103573155923254@msgid-missing> (raw)
Hi,
I have a performance problem when using source routing, following the
instructions in the Adv Linux Routing HOW-TO. I have a box with 3 NICs,
all connected to 3 different ip networks. The box look like this:
733MHz P3 CPU
256MB RAM
Mandrake Linux 9.0
3 3C905B NIC
_________
1.2.3.93/29 ETH2 -| |- ETH0 2.2.3.44/26
---------
|
ETH 1
10.7.7.3/24
ETH2 gw 1.2.3.89
ETH1 is a "point-to-point" link to an NFS-server
ETH0 gw 2.2.3.6/26
I want traffic comming in on ETH2 and ETH0 to be routed back via their
respective default gw. This is not a problem, routing wise, it works just
as it should, but the problem is that when uploading to the box, it is
realllly slow. If I try and FTP to it, I get between 7-10MB/s download,
but only around 1-2MB/s upload. This is if I use source routing. As a
small problem fix, I use the following script, only applying source
routing to ETH2, and letting the "normal def gw"-rule apply for ETH0, that
way up- and download to ETH0 is basically 100Mbit.
The script I run is this:
# add instructions for eth2
/sbin/ip route add 1.2.3.88/29 dev eth2 src 1.2.3.93 table nic3
/sbin/ip route add default via 1.2.3.89 table nic3
/sbin/ip rule add from 1.2.3.93 table nic3
/sbin/ip route flush cache
I also had a similar script for ETH0, but as I said, the performance was
really bad. At least now, performace for ETH0 is okey both upstream and
downstream.
Anyone know where I should start looking?
Regards
Henrik Johansson
GlobeCom Network
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-10-27 15:11 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-103573155923254@msgid-missing \
--to=hj@globecom.se \
--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.