OSPF issues with Activate Settings

[lonnie]

A number of people have been reporting an issue with activations in that OSPF will lose track of devices and generally do bad things to the network.

We have identified a new way to activate that might make this less of an issue. Our current activation is the way it is because of PCMCIA devices which are totally dynamic. We had to rip the network down and rebuild it as the only way to ensure PCMCIA devices were properly configured. Unfortunately this seems to be bad for OSPF and RIP which like to be left alone and running.

We are testing a new activate method that will not affect routes or IP's unless you change a route or IP. All quagga programs are no longer restarted which will mean they will not be making any down/up announcements. I cannot say if this will affect anything later on, but it should help with the problem as identified.

Expect a new beta by the end of this week.

[Equis]

Cool, Thanks :-)

[oscarBravo]

That's good news. I never understood why activating changes tore everything down; now it's clearer.

Looking forward to the new approach.

That said, 2.11.0 is still unusable for us because of the WPA-PSK issue, so if the new beta is built incrementally on it, we won't even be in a position to test it unless that's fixed.

[bminish]

Originally Posted by oscarBravo

we won't even be in a position to test it unless that's fixed.

On client facing AP nodes, that is. Few of these run OSPF

.brendan

[tony]

Originally Posted by oscarBravo

That's good news. I never understood why activating changes tore everything down; now it's clearer.

Looking forward to the new approach.

That said, 2.11.0 is still unusable for us because of the WPA-PSK issue, so if the new beta is built incrementally on it, we won't even be in a position to test it unless that's fixed.

Can you PM me your WPA-PSK settings, including the last known version that it worked? All my tests with WPA-PSK seem to work well, so would like to try and duplicate your setup as close as possible.

Thanks!

[lonnie]

The v2 release will be delayed until next week. We still have to deal with PCMCIA because it is supported and people use it. Doing the new activate sequence with V3 was easy and was released yesterday but v2 will take more time.

[tony]

This will also give us time to look into the WPA-PSK issue closer as well.

[Beebe]

I think maybe you are barking up the wrong tree? My OSPF problems often occur when I'm not messing with anything, routes just disappear and part of the network drops offline, often it's an activate changes that fixes it, not breaks it... And when it breaks in this way, I can log into the interface on my side of the radio with the downed link, and then ssh into the next radio so the link is actually working, but for some reason OSPF is not passing on it's routes.

I have noticed how sometimes when this happens, I can ping through the network to my side of a radio, but I can not ping the IP on another interface on that same radio. OSPF seems to loose all knowledge of a subnet on it's own radio.

Anyone concurr that this is the problem?

Thanks,
Roger

[lonnie]

What version are you using? What are the radio cards?

Originally Posted by Beebe

I think maybe you are barking up the wrong tree? My OSPF problems often occur when I'm not messing with anything, routes just disappear and part of the network drops offline, often it's an activate changes that fixes it, not breaks it... And when it breaks in this way, I can log into the interface on my side of the radio with the downed link, and then ssh into the next radio so the link is actually working, but for some reason OSPF is not passing on it's routes.

I have noticed how sometimes when this happens, I can ping through the network to my side of a radio, but I can not ping the IP on another interface on that same radio. OSPF seems to loose all knowledge of a subnet on it's own radio.

Anyone concurr that this is the problem?

Thanks,
Roger

[bradg]

Originally Posted by Beebe

Anyone concurr that this is the problem?

I can confirm this behaviour and resolution as well - again. I think I've posted this several times over the last 6-9 months. Using 2.10.1b5 on every OSPF enabled WRAP, CM9's for every radio link.