From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Traceroute looks good, but packets destined for wrong MAC
Date: Tue, 29 May 2001 21:12:28 +0000 [thread overview]
Message-ID: <marc-lartc-99117093317802@msgid-missing> (raw)
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
You can see, I have two IPs of different nets bound to the single
interface in the machine. My goal is to route connections over both the
DSL and the (fractional) T1, preferring the DSL with a 6:1 ratio.
Here is my configuration so far, which mostly works:
root@windmill:/home/jwb# ip route list
65.198.37.64/29 dev eth0 proto kernel scope link src 65.198.37.66
192.168.168.0/24 dev eth0 proto kernel scope link src 192.168.168.200
127.0.0.0/8 dev lo scope link
default
nexthop via 192.168.168.1 dev eth0 weight 6
nexthop via 65.198.37.65 dev eth0 weight 1
root@windmill:/home/jwb# ip route list table 100
192.168.168.0/24 dev eth0 scope link
default via 192.168.168.1 dev eth0
root@windmill:/home/jwb# ip route list table 200
65.198.37.64/29 dev eth0 scope link
default via 65.198.37.65 dev eth0
root@windmill:/home/jwb# ip addr list
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:d0:b7:88:23:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.168.200/24 brd 192.168.168.255 scope global eth0
inet 65.198.37.66/29 scope global eth0:t1
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
32766: from all lookup main
32767: from all lookup 253
This mostly works fine, except that a lot of packets are going out over
one link or the other, with the wrong source address. Also traceroute
shows packets going out over the DSL, which actual TCP SYN packets go out
over the T1 with the wrong address. Here is an example:
traceroute to appwatch.zdnet.com (216.65.128.201), 30 hops max, 40 byte
packets
1 w145.z064001233.sjc-ca.dsl.cnc.net (64.1.233.145)
2 w001.z064001104.sjc-ca.dsl.cnc.net (64.1.104.1)
So the packets should be going out over the DSL. However, ethereal shows
that when I try to initiate a TCP connection, the packets are headed for
the MAC address of corresponding to the T1 router (65.198.37.65). Why
would this discrepancy happen?
Regards and thanks in advance for any assistance,
Jeffrey Baker
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-05-29 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 21:12 Jeffrey W. Baker [this message]
2001-05-29 21:42 ` [LARTC] Traceroute looks good, but packets destined for wrong Jeffrey W. Baker
2001-05-29 23:20 ` [LARTC] Traceroute looks good, but packets destined for wrong MAC 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-99117093317802@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.