From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing NDAS ?
Date: Fri, 22 Jun 2007 23:16:00 +0000 [thread overview]
Message-ID: <467C5830.6000606@riverviewtech.net> (raw)
In-Reply-To: <1741FFAACCEC074AA16B4B57DA95500E01F084@jos-ex1.josims.local>
On 6/22/2007 5:22 PM, Andrew Lyon wrote:
> Are you saying that there is something wrong with proxy arp? So far
> it works fine for us, we have 5 segments and approx 150 nodes.
Is there something wrong with driving a stake in to the ground with a
rock verses a sledge hammer, no.
I personally see no reason to ever use proxy arp when you can bridge. I
also see much finer grained control over bridging than I do of proxy
arp. Not to mention that with bridging, devices see the real MAC
address verses the MAC of the device doing the proxy arp.
That being said, proxy arp has been around for more decades than
bridging has. I'm sure that there are situations where proxy arp is the
better situation. However personally I would have to have a situation
where bridging would not work and proxy arp would for me to use proxy
arp over bridging. I guess some of this could be attributed to the fact
that I have come in to networking with in the last 10 years and to me
proxy arp is the old holdover about like NetBEUI is for some networks.
(That is not to say that proxy arp has as many problems as NetBEUI does
or vice versa.)
> Ndas devices don't work with proxy arp, bridge would, but at the
> moment we are a 24/7 operation and making the necessary config
> changes for bridge would be disruptive.
Do you have another system that you can put in to production that would
connect to both broadcast domains and have it bridge just NDAS traffic
and let your existing routers do what they are doing? I can understand
and appreciate the inability (technical / political / chronological) to
be able to replace work on production systems. That does not mean that
you can not accomplish what is needed another way.
> I will probably end up doing it, but I would like to know if there is
> any alternative..
Will adding a system just to bridge NDAS traffic work?
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-06-22 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 21:31 [LARTC] Routing NDAS ? Andrew Lyon
2007-06-22 21:44 ` Grant Taylor
2007-06-22 22:22 ` Andrew Lyon
2007-06-22 23:16 ` Grant Taylor [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=467C5830.6000606@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.