From: Antony Lesuisse <lartc-list@udev.org>
To: lartc@vger.kernel.org
Subject: [LARTC] simpler version, How to bypass the local routing table?
Date: Fri, 12 Dec 2003 15:18:34 +0000 [thread overview]
Message-ID: <marc-lartc-107124395129803@msgid-missing> (raw)
imagine the folowing simpler configuration
Hub | Linux
+----- eth0 192.168.1.1/24
| |
+----- eth1 192.168.1.2/24
|
I would like that the packets of ping -I eth0 192.168.1.2, go on wire via the
eth0 interface to the hub, that the hub broadcast them to eth1, and the kernel
receive them from eth1 and process it and the send the ICMP replies back to the
wire via eth1, and eth0 and ping recieve it.
For that the kernel HAS to NOT recognize the dest ip (192.168.1.2) as local,
when packets comes from processes, so that the packet will be sent over the
interface even if there is an other interface eth2 configurated with the
destination ip (192.168.1.2) on the same kernel.
So the problem is how to bypass the lookup in the table shown by:
ip route show table local
Or how to change the priority of the rule 0: shown by:
ip rule
One dirty solution might be altering the dest ip of outgoingpackets that comes
from processes (OUTPUT ROUTING), using ip&(1<<8), to fool the kernel. Then
having the HUB (i can program the hub) to remove that bit. (but that forbids
using with that bit set).
References:
Guide to IP Layer Network Administration
http://linux-ip.net/
Kernel Packet Traveling Diagram
http://www.docum.org/stef.coene/qos/kptd/
--
Antony Lesuisse http://antony.lesuisse.com
GPG EA2CCD66: 4B7F 6061 3DF5 F07A ACFF F127 6487 54F7 EA2C CD66
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-12-12 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 15:18 Antony Lesuisse [this message]
2003-12-12 16:24 ` [LARTC] simpler version, How to bypass the local routing table? Darryl Miles
2003-12-12 16:41 ` Julian Anastasov
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-107124395129803@msgid-missing \
--to=lartc-list@udev.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.