From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Proxy-ARP
Date: Mon, 18 Nov 2002 07:42:52 +0000 [thread overview]
Message-ID: <marc-lartc-103760482418898@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103759486813907@msgid-missing>
-----Original Message-----
From: Martin A. Brown
<snip>
Let me note a few things. First, you need only send a mail to the list,
not the individual subscribers.
</snip>
Eager beaver. My apologies if I transgressed.
<snip>
This means that you are assigning the same IP to two different ethernet
interfaces on the same media segment. That's not strictly forbidden, but
unless you take some other steps, the machines on the ethernet will get
one MAC address for 10.0.1.4 one some ARP requests, and the other MAC
address for other requests. That's not quite deterministic, so your
networking will break.
</snip>
True. This is my intent. My LAN will get the MAC address of eth1 for
10.0.1.4 while my router will get the MAC address of eth1 for the same IP.
This is how it is physically arranged.
<snip>
If you are intending to break the network into two pieces, you have not
done so here. You should make routes for the IPs which are reachable on
each ethernet. For example:
# ip route del 10.0.1.0/24 dev eth1
# ip route add 10.0.1.1 dev eth0
# ip route add default via 10.0.1.1
: #ip ro del 10.0.1.0/24 via 10.0.1.4 dev eth0
: RTNETLINK answers: No such process
That's because there is no such route....hence the answer is "RTNETLINK
answers: No such process" I'd suggest re-reading the iproute2 command
reference to understand the use of the keyword "via". You are not using
the right keyword, or not understanding what you are asking of the kernel,
here.
: #ip ro add 10.0.1.1/24 via 10.0.1.4 dev eth0
</snip>
I got my answer. Thanks. I guess I should have used "ip ro del 10.0.1.0/24
dev eth0". I used via as the scope link src was there. I wanted to get rid
of the generic route for 10.0.1.0/24 via eth0 and replace it with a route
for just 1 ip 10.0.1.1 (my router's ip) via eth0. Thus all packets meant for
my LAN will go thro' eth1 while those meant for the router will go thro'
eth0. I think I need to do a few more runs of the iproute2 doc to understand
syntax pretty well.
I was trying this so that I could use iptables for firewalling and
tc/cbq/htb for bandwidth shaping out of my LAN without reconfiguring and
gateway IPs on nodes. I was given to understand that a pure bridge will work
with iptables. Further reading has enlightened me on that too. Looks like
the bridging code now interfaces with iptables.
Thanks for the help.
Mohan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-11-18 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 14:11 [LARTC] Proxy-ARP S Mohan
2002-11-18 5:49 ` Martin A. Brown
2002-11-18 7:42 ` S Mohan [this message]
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-103760482418898@msgid-missing \
--to=smohan@vsnl.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 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.