Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Philip Mak <pmak@animeglobe.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Route works, but ping time is 1000 ms
Date: Thu, 14 Feb 2002 21:06:19 +0000	[thread overview]
Message-ID: <marc-lartc-101372075921754@msgid-missing> (raw)

I have a server that has two ethernet cards, eth0 (64.94.46.199) and
eth1 (66.28.98.52).

eth0's ISP has expensive, high quality bandwidth.
eth1's ISP has cheap, low quality bandwidth.

I have the route set so that by default, all packets will go out
through eth1:

default via 66.28.98.34 dev eth1

However, I'd like to make it so that when I ssh to 64.94.46.199 (eth0,
the expensive high quality ISP), the return traffic will go out
through eth0. So, I typed this:

$ echo "200 pnap" >> /etc/iproute2/rt_tables
$ ip rule add from 64.94.46.199 lookup pnap
$ ip route add default via 64.94.47.253 dev eth0 table pnap

This correctly makes it route outgoing packets with source IP of
64.94.46.199 through eth0.

However, the ping time suddenly goes up a lot on the last hop (you can
traceroute 64.94.46.199 and see for yourself).

Any idea what I did wrong? I have a hunch that my ISP's router doesn't
like some settings in the packets I sent to it and is giving me low
priority as a result, but I wouldn't know how to tell if that was the
case... (I e-mailed my ISP for help on Tuesday; still waiting.)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

             reply	other threads:[~2002-02-14 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 21:06 Philip Mak [this message]
2002-02-15 16:16 ` [LARTC] Route works, but ping time is 1000 ms bert hubert
2002-02-15 18:11 ` Philip Mak
2002-02-15 18:39 ` Philip Mak

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-101372075921754@msgid-missing \
    --to=pmak@animeglobe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox