* tony sarendal <[EMAIL PROTECTED]> [2006-04-08 00:51]:
> It looks like bgpd has a problem with validating nexthop on new interfaces
> when they are created.
> A flap of the interface or restarting bgpd makes nexthop validate.
> I have only tested with vlan interfaces.
bizarre. I was able to see - let's call it "something odd" when I tried
to reproduce that from home earlier this morning. Now I am completly
unable to reproduce - it works just like it should. the RTM_IFANNOUNCE
message that tells us about the new interface is directly followed by a
RTM_IFINFO one giving us linkstate and the like and thus everything
gets set allright.
please:
-run bgpd -d while doing this, and show output
-run 'route monitor' as well
while playing with this I noticed vlan does not correctly inherit
baudrate from the parent interface tho :)
Index: if_vlan.c
===================================================================
RCS file: /cvs/src/sys/net/if_vlan.c,v
retrieving revision 1.65
diff -u -p -r1.65 if_vlan.c
--- if_vlan.c 25 Mar 2006 22:41:48 -0000 1.65
+++ if_vlan.c 10 Apr 2006 13:41:16 -0000
@@ -474,6 +474,7 @@ vlan_vlandev_state(void *v)
return;
ifv->ifv_if.if_link_state = ifv->ifv_p->if_link_state;
+ ifv->ifv_if.if_baudrate = ifv->if_baudrate;
if_link_state_change(&ifv->ifv_if);
}
--
BS Web Services, http://www.bsws.de/
OpenBSD-based Webhosting, Mail Services, Managed Servers, ...
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
