Nope. That generally means your router is sending out an ospf ‘hello!’ packet, and is getting it back. I.e. bridge loop.
From: Af [mailto:[email protected]] On Behalf Of That One Guy /sarcasm Sent: Friday, June 5, 2015 4:04 PM To: [email protected] Subject: Re: [AFMUG] OSPF doesnt repopulate if link drops In the log I see this. I was told unless you know what youre looking at that OSPF logging is confusing. Is this normal to be seeing? On Fri, Jun 5, 2015 at 3:01 PM, That One Guy /sarcasm <[email protected]> wrote: How do I know what order theyre in? Im currently in winbox and thats just sorted. So what Im not understanding is why it initially works, but if a switch (or backhaul) in between drops, it shows the neighbor relationship, but never populates routes? Im not questioning the advice, just trying to understand the underlying mechanics to avoid a similar fate in the future On Fri, Jun 5, 2015 at 2:33 PM, Bill Prince <[email protected]> wrote: That will do it. You want the routing subnet (the /30) to be first on the list. The other local subnets will get in the way. I've not had one with that many local subnets, usually just one or sometimes two. But if you delete and re-add the local subnets, it will put the /30 first, and you should be good to go. bp <part15sbs{at}gmail{dot}com> On 6/5/2015 12:30 PM, That One Guy /sarcasm wrote: yes there are. Eth3 for example has 36 local subnets that are customer facing on the network. 2 local /30 for the two remote OSPF routers beyond this interface, 12 /30 subnets for the backhaul access (each radio will be on a /30 with its connected router interface, this is just in prep, as the sites are isolated the subnets will move) and one local subnet to act as a gateway for a catch all DHCP relay On Fri, Jun 5, 2015 at 2:23 PM, Bill Prince <[email protected]> wrote: Is there more than one subnet on your interfaces? I've found that if you have other non-route type subnets on an interface, that they can mess with the routed subnets. So you can remove/re-add those subnets that aren't used for routing, and the routes will populate the way you need. bp <part15sbs{at}gmail{dot}com> On 6/5/2015 11:53 AM, That One Guy /sarcasm wrote: So, I assume its a configuration issue, but the routers Im seeing this on also have an old milan switch in front of them, that could be coming into play, though I dont know how. If I reboot a switch between my mikrotik and my fortigates or Imagestreams, the mikrotik shows it come back as a neighbor, but never updates routes. The remote routers are acting like a woman, all nice until you dont come home one night and the next day they make sure you see them, wear little sexy outfits, but withhold the goods. I can powercycle the remote routers and everythign comes back up all snazzy. I also can remove that network from the OSPF networks tab in the mikrotik. It is configured using /30 between routers. The network type is set to broadcast, someone told me it should be point to point, but I couldnt easily get point to point option on the Fortigate OSPF configuration, so this is the interim that worked until the network is all mikrotik, we have 5 more of them that were supposed to be here wednesday. I configuered the ALL interface with the authentication key, then just add the OSPF link networks in. I waited 5 minutes on one just to see if it was a dead interval type of thing. I assume the problem here is a very simple misconfiguration on my part, but my incompetence contract specifically states I can do stupid shit on a whim. On another note, the authentication key is sent out over the network in plain text? how viewable is this if its type broadcast? like can a customer stick wireshark on his bridged subscriber and see it if theyre not on the backbone of the network since I have all interfaces in this? -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team. -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team. -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team. -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
