[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-date: 31 Aug 2005 11:41:25 -0600 -->
- <!--x-from-r13: wxancxn ng xarheb.arg (Xbr Yancxn) -->
- <!--x-message-id: [email protected] -->
- <!--x-subject: [ale] OT: Are devices allowed to update their ARP caches from non-ARP packets? -->
- <li><em>date</em>: 31 Aug 2005 11:41:25 -0600</li>
- <li><em>from</em>: jknapka at kneuro.net (Joe Knapka)</li>
- <li><em>subject</em>: [ale] OT: Are devices allowed to update their ARP caches from non-ARP packets?</li>
I have encountered a situation where a network device is updating its
ARP cache in response to an application message which is not an ARP
packet. What I need to know is, is this allowed behavior according to
the relevant standards and RFCs? I read RFCs 826 (ARP) and 894
(IP-over-Ethernet), and they seem to have nothing to say about this
particular issue. Can anyone point me to a document that explicitly
condones or prohibits this behavior?
Thanks,
-- Joe Knapka
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00534.html">[ale] HOW2 search for text in a "PDF" file ?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00535.html">[ale] Ale Digest, Vol 58, Issue 6</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00532.html">[ale] Job Oppurtunity in Gainesville Georgia</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00535.html">[ale] Ale Digest, Vol 58, Issue 6</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00531"><strong>Date</strong></a></li>
<li><a href="threads.html#00531"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>