wrstuden@nas.nasa.gov (Bill Studenmund) writes:

>> > 	34060-34063 == 0x850c - 0x850f  mask 0xfffc
>> > 	34064-34067 == 0x8510 - 0x8513  mask 0xfffc
>> > 	34068-34069 == 0x8514 - 0x8515  mask 0xfffe

>As I understand it, that's how our routing table works. It uses a binary
>tre method, so needs this. :-)

Our routing table code is perfectly able to handle the first two
entries with a single routing table entry.  At least for the IP case,
but I don't see why Atalk should be different in this case.

-- 
Christoph Badura					www.netbsd.org

	Anything that can be done in O(N) can be done in O(N^2).
	-- Ralf Schuettau (after looking at a particular piece of code)