I’m seeing some strange behaviour of OSPF on wireless link’s.
I have OSPF running on approx 40 router’s and there is probaly some bug causing that randomly some wireless interface change state to down, If I check wireless registration table link uptime is in days.
There is no message in log.
Temporary solution to this problem is to disable and enable IP address on this down interface.
Have anyone seen this problem?
If so how do you resolve it?
I thought about writing some script that would check ospf interface state and if needed disabled and enabled IP address.
same here, I’m kind of confused with the OSPF setup on wireless interfaces - can please somebody let me know whether there is any difference between running OSPF on regular ethernet interfdace and wireless interface?
for example if there is no client associated to wifi ap the route to that interface looks to be broadcasted as down in ospf network - is that true?
this is probably not exactly what we want - also the interface does not show up in Interfaces part of the OSPF setup even if the network is proprely set up in Networks
On any 802.11 based wireless link (with or without nstream, nv2, airmax, …), it is widely recommended to use ospf network-type=point-to-point or network-type=nbma. Such wireless devices sometimes (often) get multicast packet handling wrong. This is especially true of older software. Point-to-point and NBMA work better in those situations.
NBMA, theoretically, should be more stable as PTP actually uses multicast. In practice, I have no problems with PTP.
You didn’t provide any specifics about your setup, so that’s as far as I can go with an answer.
[EDIT] Didn’t realize someone had resurrected a long dead thread. Sorry.
