Good news and bad news.
First the good news:
The bridge is answering ARP requests for its own hardware address
on the internal (rl0) interface now.
I rebooted my bridge (from work, via the DSL line) just now, with
a new kernel incorporating Julian's patch from earlier today.
I then deleted the permanent ARP entry for the bridge on my desk-
top (after setting up a delayed background command as a "dead
man's switch" to restore the ARP entry if needed in case I got
locked out -- remember, I was doing all this remotely).
My desktop got an ARP reply from the bridge as soon as I deleted
the permanent entry. I confirmed this by running "tcpdump -i rl0
arp" on the desktop.
Now the bad news:
ARP replies from the bridge to the DSL modem (via the external
i/f) are still getting sent to the desktop (via the internal i/f),
and the desktop is using them to change its idea of the bridge's
hardware address. This causes a log message like the following:
/kernel: arp: 171.66.188.114 moved from 00:e0:29:68:64:3e
to 00:60:97:05:32:cd on rl0
The desktop can contact the bridge using either of the bridge's
hardware addresses, of course -- but I still think the bridge
ought to send out its ARP replies =only= on the interface from
which the query came that the bridge is replying to.
FWIW, the desktop is still running 4.2-RELEASE.
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
