[Mikrotik Users] on import export loop-protect sends error

2016-12-14 Thread Daniel Biland via Mikrotik-users
anybody tryied to make a clone of a rb with routerOS 6.37.3 ? i did try, but i had to downgrade to bugfix only (worked after like a charm), because i got a bunch of errors with the new loop-protect feature its like it has wrong values in the Vlans (its default and off) i got this error:

Re: [Mikrotik Users] OSPF errors on router

2016-12-14 Thread Robbie Wright via Mikrotik-users
"closed" every vlan not in use? Our vlans are mainly in use for /30's to remote sites which ospf runs over. All of our unused ports are disabled and all of our vlans are in use. Robbie Wright Siuslaw Broadband 541-902-5101 On Wed, Dec 14, 2016 at 9:42 AM, Ethan E.

Re: [Mikrotik Users] OSPF errors on router

2016-12-14 Thread Ethan E. Dee via Mikrotik-users
I saw this a few weeks ago. I went into my 'tik cloud router switches and closed every vlan that the ports weren't actively using. That solved it. On 12/13/2016 11:50 PM, Robbie Wright via Mikrotik-users wrote: I saw this issue pop up again. The duplicate router ID thing caught me. We've

Re: [Mikrotik Users] OSPF errors on router

2016-12-14 Thread Robbie Wright via Mikrotik-users
Yeah, it was a firmware update that made it show up in the logs for us too. In our setup, each OSPF instance is inside its own vlan running a public /30. We've got one CCR with two ports in a bridge, each port going to a 24 port edge switch. The CCR has multiple OSPF peers and all are throwing the

Re: [Mikrotik Users] OSPF errors on router

2016-12-14 Thread Scott Reed via Mikrotik-users
Time synchronization ranks up at the top as well. Doesn't usually cause OPs error, but it is critical. On 12/14/2016 8:51 AM, Kevin Myers via Mikrotik-users wrote: Just wanted to echo and reinforce the comments that Justin Wilson made about every router that participates in OSPF needs to

Re: [Mikrotik Users] OSPF errors on router

2016-12-14 Thread Scott Reed via Mikrotik-users
My experience is that has almost always been a configuration error. Often related to Router ID, but not necessarily the one reporting the errors. One thing MT appears to not like is Router ID of 0.0.0.0. Duplicate IP addresses can cause this message. The packet actually came from somewhere