Alan wrote:
> On Wed, Oct 24, 2001 at 11:14:54AM -0200, Daniel C. Sobral wrote:
>
>>After a long time looking into this, I have finally understood what's
>>the problem. RTM_NEWADDR is generated sometimes yes, sometimes no. I
>>have absolutely no idea what makes the difference, particularly because
>>I have absolutely no idea where the relevant code portions is located.
>>
>>As for my environment, my test base is all vlan, and I run a routing
>>daemon (zebra). Attached are two logs. The first is a list of commands
>>running in background manipulating the interfaces. The second is the
>>output of route -n monitor at the same time.
>>
>>If anyone can point me in the right direction to debug this problem, I
>>would appreciate immensily. This problem is being a hell on us.
>>
>>
> I don't see RTM_NEWADDR's in the logs, only RTM_NEWMADDR's.
Well, that's the whole point. It should.
--
Daniel C. Sobral (8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
There is nothing more silly than a silly laugh.
-- Gaius Valerius Catullus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
