From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: "Matthew G. Marsh" <mgm@paktronix.com>
Cc: kuznet <kuznet@ms2.inr.ac.ru>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to see manually specified proxy arp entries using "ip neigh"
Date: Fri, 19 Oct 2001 15:57:22 -0400 [thread overview]
Message-ID: <3BD085A2.8CE0987B@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0110191340330.17932-100000@netmonster.pakint.net>
"Matthew G. Marsh" wrote:
> > Currently I have been doing this by manually setting proxy arping on the NIC for
> > the IP address assigned to the ethertap device. If this feature is going to be
> > removed, then how should I be doing this?
>
> If an IP address is routed to on the external network then it will be
> available. It does _not_ matter what interface that address is assigned
> to. EX:
>
> ip addr add 10.1.1.1/24 dev dummy0
> ip link set dev dummy0 up
>
> now ping 10.1.1.1 from another machine on eth0 that has an appropriate
> route. I suspect what is really biting you is that your rp_filters are way
> too restrictive on your machine.
Sorry, I guess I explained it wrong. Ethertap has an IP address assigned to the
device in the linux kernel. It is then configured with a point to point route
to another IP address on the other concepual end of the link (ie in userspace).
It is this other IP address that I am proxy arping for.
Thus,
[mtc@10.40.14.70 mtc]$ /sbin/ip add
<stuff removed>
4: tap0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc noqueue
link/ether fe:fd:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 10.40.14.73 peer 10.40.14.74/32 brd 10.40.14.255 scope global tap0
[mtc@10.40.14.70 mtc]$ /sbin/ip ro
10.40.14.74 dev tap0 proto kernel scope link src 10.40.14.73
<stuff removed>
[mtc@10.40.14.70 mtc]$ /sbin/arp
Address HWtype HWaddress Flags Mask Iface
<stuff removed
10.40.14.74 * * MP eth1
Thus, anyone arping for 10.40.14.74 (which is on top of a protocol stack in
userspace) will get the MAC address of eth1 as a response.
I cannot turn on proxy arping for the interface in general as I have eth0 and
eth1 on the same subnet and turning on proxy arping causes bad things to
happen. Thus I have a single manual proxy entry in the arp table.
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2001-10-19 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 19:15 how to see manually specified proxy arp entries using "ip neigh" command? Christopher Friesen
2001-10-18 19:25 ` how to see manually specified proxy arp entries using "ip neigh" kuznet
2001-10-18 20:02 ` Richard B. Johnson
2001-10-18 20:08 ` Christopher Friesen
2001-10-19 16:40 ` kuznet
2001-10-19 18:44 ` Matthew G. Marsh
2001-10-19 19:57 ` Christopher Friesen [this message]
2001-10-19 13:32 ` Andrey Savochkin
2001-10-19 17:13 ` kuznet
2001-10-20 10:55 ` Andrey Savochkin
2001-10-21 17:21 ` kuznet
2001-10-23 10:33 ` Andrey Savochkin
-- strict thread matches above, loose matches on Subject: below --
2001-10-20 19:56 Julian Anastasov
2001-10-21 17:44 ` kuznet
2001-10-23 8:47 ` Andrey Savochkin
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=3BD085A2.8CE0987B@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mgm@paktronix.com \
/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