On Mon, Jun 04, 2012 at 08:28:29AM +0200, Claudio Jeker wrote: > On Sun, Jun 03, 2012 at 03:02:36PM -0700, Paul B. Henson wrote: > > On Sun, Jun 03, 2012 at 05:12:19PM +0200, Claudio Jeker wrote: > > > > > Is this after a reload of the config or does this also happen when you > > > restart ospfd? > > > > It was after a config reload, after following Stuart's suggestion to > > restart ospfd everything's working great :). Maybe it would be worth a > > note in the ospfctl man page that sometimes a reload isn't sufficient, > > and ospfd might need to be completely restarted for an interface that's > > created after it's already running? > > > > I put it on my list of things to look at. Maybe there is an important > route message missing to tell ospfd that the trunk(4) is now UP and > running. >
Tested this today while sitting in public transport. I started ospfd with only a lo1 interface in ospfd.conf. Created the trunk (ifconfig trunk0 trunkport em0) Added IP to trunk (ifconfig trunk0 192.168.1.1 netmask 255.255.255.0) Reloaded ospfd config (ospfctl reload) Added wireless to trunk so I could get a link up (ifconfig trunk0 trunkport iwn0) and ospfd found the interface and tracked its link state correctly. So I'm not sure where your problem was but I could not reproduce it on -current. -- :wq Claudio
