MT is saying it is not a problem of OSPF. Packet is sent back to the router by some device. Loop, switch is between is leaking vlan packets from other vlans, etc, etc… OSPF is just processing packets that it receives.
We get the same problem on our CHR’s (I’m most certainly not excluding a loop though, but it doesn’t seem like our switches are overloaded at all)
/routing ospf network
add area=backbone network=192.168.10.0/24
[diadmin@somegw] > /routing ospf interface print
Flags: X - disabled, I - inactive, D - dynamic, P - passive
# INTERFACE COST PRIORITY NETWORK-TYPE AUTHENTICATION AUTHENTICATION-KEY
0 D ether2 10 1 broadcast none
I confirm existence of a problem on firmwares on 6.45.2, the configuration is checked - there are no loops. For bigger confidence, decided to collect traffic to look at what incoming packet which was allegedly generated by the router to it it is not pleasant, and so I did not see such packet in a sniffer. But saw defragmentation of incoming packets which coincide with error time in the log. How can fragmentation of a packet cause this error?
Do you have connection tracking enabled?
Hello, I discovered this issue on our routers and solution was really disable conntrack for ospf. No looped ospf packet found by sniffer. Very strange.
/ip firewall filter
add action=accept chain=input protocol=ospf
/ip firewall raw
add action=notrack chain=prerouting protocol=ospf
add action=notrack chain=output protocol=ospf
I’m experiencing the same error for no reason other than having upgraded from an earlier v6 version to 6.44.6.
Immediately after upgrading, on a PTP link, no switches involved, ‘nothing complicated’, just a mikrotik through a wireless PTP bridge (UBNT) to this other mikrotik. I have tried the below fix, but this does not remedy the issue and the error message persists. Also, it’s only witnessed on one mikrotik, however both are on 6.44.6. One is an RB3011UiAS, the other is a Hex S. The Hex S is the one producing the errors
ospf,error Discarding packet: locally originated usually means that there is an IP conflict on your network. You could be trying to use the same IP address on more than one device and OSPF is picking up this conflict. I would try using another IP address on your router where you are trying to set up OSPF than the one being reported in your logs.