All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Traceroute looks good, but packets destined for wrong
Date: Tue, 29 May 2001 21:42:11 +0000	[thread overview]
Message-ID: <marc-lartc-99117271424129@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99117093317802@msgid-missing>


Please forgive my crass self-reply, I just noticed my problem:

On Tue, 29 May 2001, Jeffrey W. Baker wrote:

> Hello,
>
> I am a newbie at routing configuration and I hope you can help me
> understand why something is happening, and how I can reconfigure my
> machine to work correctly.  Here is my network setup:
>
> [DSL Router]          [T1 Router]
>      |                     |65.198.37.65
> [NAT/firewall]             |
>      |192.168.168.1        |
>      +-----------+---------+
>                  |
>              [switch]
>                  |
>                  |
>                  +-------[Linux box]
>                          192.168.168.200/eth0
>                          65.198.37.66/eth0

[snip]

> root@windmill:/home/jwb# ip ru list
> 0:	from all lookup local
> 32764:	from 65.198.37.66 lookup 200
> 32765:	from 192.168.168.1 lookup 100

Of course, 192.168.168.1 is not a local IP.  Changing this rule to from
192.168.168.200 lookup 200 may have fixed the problem.  Please let me know
if you spotted any other goofs.

Ashamedly yours,
Jeffrey Baker


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-05-29 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 21:12 [LARTC] Traceroute looks good, but packets destined for wrong MAC Jeffrey W. Baker
2001-05-29 21:42 ` Jeffrey W. Baker [this message]
2001-05-29 23:20 ` Guy Van Den Bergh
2001-05-29 23:24 ` Guy Van Den Bergh

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-99117271424129@msgid-missing \
    --to=jwbaker@acm.org \
    --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.