ARP differences in *BSD

Hello,

I happened to bump into an article on daemonnews from a while back on changes that took place to the NetBSD ARP/ethernet system: http://www.daemonnews.org/199809/underhood.html

I then noticed that FreeBSD is very similar also (e.g. struct ifnet as 1st argument to arp_ifinit() vs. struct arpcom like OpenBSD)..

Is OpenBSD going to sync to this to minimize diffs etc, or are we planning to keep things the way they are?

I am just curious as to why some of these differences remain, not suggesting which one is better or should be implemented..

If OpenBSD is sticking with the current setup, what are the reasons for it? (better/faster/more compat/other way sucks/ etc)

My reason for searching was looking at the implementation of the SIOCSIFLLADDR ioctl in FreeBSD and how to get it over to OpenBSD (since wwwgnats if offline, I cannot lookup the text of PRs 2117 and 2118, which appear to be previous attempts to port this ioctl).

I have a mostly working example (MAC addr changes in memory according to ifconfig, but does not appear to change when the host talks on the wire). So I started looking at the arp_ifinit() functional areas..

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

Thanks, and happy holidays..

p.s. - I know that SIOCSIFLLADDR and the ability to change your MAC addr has been talked about before, but I need it for my situation, so no flames on that please :)

cheers,

---
jason