From: Mark C. <ma...@go...> - 2000-10-28 01:41:46
|
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/26/00, 11:33:20 PM, "CK Ng" <ck...@cs...> wrote regarding Problem routing ATM Linux using Zebra .sdm: > My problem is: > 1. Initial IP for R2 (b) is 10.39.11.17/16, but ospf <most of the time> > cannot get the neighbor R1, why is that consider that multicast is enable > and both are in the same subnet? Is ospf unstable in zebra? Are you sure that you have zebra setup correctly? It's a real pain to configure - in my opinion. i.e. Don't the areas need to be specified!?! > 2. If with (c) disabled (no ethernet connection) R1 or R2 won't discover > each other, is multicast not supported under ATM, but BUS should work right? > And I keep getting "neighbor table overflow" message with occasionally "NET: > x message suppressed". I remember getting these "neighbor table overflow" messages but I can't remember why. I'll ask at the office to see if someone there remembers. > 3. I've try modifying clip.c patch by Mark Clayton > (http://marc.theaimsgroup.com/?t=95374410100001&w=2&r=1). But I couldn't > find the correspondent 'read_lock_bh' and 'read_unlock_bh' functions in > version 0.59, anyone could give a pointer?? Errr, um... I posted this patch a little premature. We wanted to run zebra without LANE. We achieved it with the patch, but it is really just a hack. Besides, this patch was intended for kernel version 2.3.42 and linux atm 0.67. It was reported to me that zebra runs over lane just fine. (But I never understood how it could, but that's my confusion) I hope this helps |