The problem Mr. Pallfreeman was seeing are related to how I was
building the arp-reply based on the sources arp_hrd type. I never
expected to see a token-ring arp arrive over an ethernet interface.
Therefore the arp code was trying to check for and collect the
source route that the arp took on
Okay, that one is just a little too strong. It won't allow
a FreeBSD token-ring station to arp-reply to an ethernet station
on the other side of a broken translational bridge. This one
will.
Larry Lile
l...@stdio.com
On Wed, 14 Apr 1999, Larry Lile wrote:
The problem Mr. Pallfreeman was
My -current trashbox is having some pretty severe problems which seem to
stem from the token ring additions on March 10th. The box in question
wouldn't stay up for more than a few minutes.
``savecore'' isn't working for me right now, but I've managed to delete a
single line of code which lets
Just so Julian doesn't get blamed here, I was the one who wrote
the Olicom oltr driver and made the arp changes. Julian was
just nice enough to commit them.
The only thing I can figure, as I can't tell exactly what caused
it to punt, is that you received a token-ring arp packet that is
somewhat
