Route ospf error discarding packet locally originated

Discarding packet locally originated микротик

Wed Apr 27, 2022 11:17 am

I’ve manually added all VLAN interfaces for neighbourship in OSPF with network type as point to point and that’s it. The OSPF costs are set pretty much in the best possible way that I could think of in my head and it is running very smoothly apart from the fact that I’m getting bombarded with these errors.

One very strange thing about this, is that, MKTs with only 1 neighbour will not have ANY of these errors appear, ever. If I add one more neighbour, the error will appear in both interfaces.

Any clue on why’s this happening?

P.S. I’ve checked all IP addresses and made sure they are correctly set so no other MKT has the same one with another one or any link in regards to that.

Re: OSPF Error — Discarding packet locally originated [SOLVED]

Wed Apr 27, 2022 11:51 am

Error is because the router receives a message containing its own router-id.
Two more things to check:
* make sure all neighbors have unique router-ids
* if you have connection tracking enabled, then try to set up raw rules in prerouting and output chains for OSPF traffic with action=»no-track»

If that does not help, then you have an actual L2 loop in your network.

Re: OSPF Error — Discarding packet locally originated

Wed Apr 27, 2022 1:39 pm

Error is because the router receives a message containing its own router-id.
Two more things to check:
* make sure all neighbors have unique router-ids
* if you have connection tracking enabled, then try to set up raw rules in prerouting and output chains for OSPF traffic with action=»no-track»

If that does not help, then you have an actual L2 loop in your network.

Источник

Discarding packet locally originated микротик

Sat Feb 06, 2010 6:23 am

Quick overview — wheel and spoke network with IPSec over IPIP tunnel and OSPF running on the IPIP interfaces (based on this article http://wiki.mikrotik.com/wiki/IPSec_VPN . _and_Cisco but using OSPF instead of RIP and both routers are Mikrotiks). I am only getting these errors on the IPIP tunnel addresses on the central router that the rest dial in to. All routers recently upgraded to ROS_4.5 and that is when I started to notice the errors in my log files. example error below —

20:14:25 route,ospf,error Discarding packet: locally originated
20:14:25 route,ospf,error src address=10.0.1.117 awsmith

Re: route ospf error -> Discarding packet: locally originated

Tue Mar 02, 2010 3:43 am

Quick overview — wheel and spoke network with IPSec over IPIP tunnel and OSPF running on the IPIP interfaces (based on this article http://wiki.mikrotik.com/wiki/IPSec_VPN . _and_Cisco but using OSPF instead of RIP and both routers are Mikrotiks). I am only getting these errors on the IPIP tunnel addresses on the central router that the rest dial in to. All routers recently upgraded to ROS_4.5 and that is when I started to notice the errors in my log files. example error below —

20:14:25 route,ospf,error Discarding packet: locally originated
20:14:25 route,ospf,error src address=10.0.1.117 he1ium

Re: route ospf error -> Discarding packet: locally originated

Sat Mar 13, 2010 12:22 am

Re: route ospf error -> Discarding packet: locally originated

Sat Mar 13, 2010 12:29 am

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 8:35 am

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 6:55 pm

Hello — we have a thread started a few days before yours, and we are having the same problem. Dropping OSPF routes, usually the same couple, but it is very often. One of the routes it drops is even an ethernet link, Odd thing is which router drops the route:

Border Router -ethernet> RB433AH (4.6) -Bonded link to> RB600 (4.6) -ethernet> rb433ah(4.6)

This RB433AH (4.6) drops the route to the wireless interface of This rb433ah(4.6)

Very odd, and extreamly frustratin as this seems to happen more during peak times, and is on some of our core routers. Any help would be extreamly helpful, Mikrotik.

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 8:32 pm

This is what I got from Mikrotik and it didn’t work (see below). By setting interfaces to passive (on one side, other side, both sides), the tunnel addresses appears to be up but the remote LAN networks were not distributed —

Yes it is possible.
Lets say we have setup 10.1.1.1/24 on ether1 and you want to run ospf on
10.1.1.0/24 network only.

Setup as follows
/routing ospf network add network=10.1.1.0/24
/routing ospf interface
add interface=ether1
add interface=all passive=yes

Nothing complicated. Chupaka

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 12:29 am

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 7:18 am

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 9:45 am

Re: route ospf error -> Discarding packet: locally originated

Fri Mar 19, 2010 7:11 am

Re: route ospf error -> Discarding packet: locally originate

Fri Jan 27, 2012 12:42 am

Re: route ospf error -> Discarding packet: locally originate

Wed Apr 10, 2013 8:36 am

Re: route ospf error -> Discarding packet: locally originate

Sun Sep 01, 2013 10:26 am

Re: route ospf error -> Discarding packet: locally originate

Sun Sep 01, 2013 6:07 pm

Have you attempted to change the ospf network type or set static ospf neighbors? Setting a static neighbor will remove multicast from the mix and changing from broadcast to ptp will remove DR/BDR elections.

I would be curious to see what RIP or BGP do over the same physical topology — might help you sort out whether you have an ospf specific issue or a physical and/or logical topology issue.

Re: route ospf error -> Discarding packet: locally originate

Mon Mar 31, 2014 5:25 pm

I’m struggling with that in our network for about a year.
We have changed most of devices to nmba mode — but route propagation was taking too long.

We can observe that issue on CCR’s working versions 6.7,6.10, 1100AHx2 ver 6.7 and almost on all other devices with OSPF.
We where thinking the issue is with radio link, but it is happening with all radio links that we have (ubnt, MikroTik, Ceragon, SAF). We can find it also when two devices are connected on cable.

My current status — I put few firewall rules to block packets with source IP the same as device.
Error disappear.

> /ip address print where interface=ether1
Flags: X — disabled, I — invalid, D — dynamic
# ADDRESS NETWORK INTERFACE
1 10.240.14.254/24 10.240.14.0 ether1

> /ip firewall filter print
Flags: X — disabled, I — invalid, D — dynamic
0 chain=input action=drop protocol=ospf src-address=10.240.14.254

I was trying to track them on device that is connected to that one, but without luck — packets are not coming from outside.

When I enabled packets logging, my results:
15:00:48 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1764
15:01:01 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1752
15:02:31 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1764
15:02:56 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1752

Hope that will give some kind of directions.
RB1100AHx2 RoS v6.7

Источник

Discarding packet locally originated микротик

Thu Dec 03, 2015 3:57 pm

Hoping to get some help and insite as to what is going on. I believe I understand what is happening and why the error is happening but I don’t know how to resolve the issue.

Was looking at my logs recently and saw this error happening a bunch.

07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1

I believe it is due to when I am creating my PPP Secrets I am using the same local address. Everything that I have read online for help on creating a PPTP tunnel seems to say to make the local address the same. Everything works the way that I want it to work, but my logs are getting flooded by this error. I think that if I were to make the local address unique for each one I will be able to resolve the error.

This is a small portion of my PPTP server file.

# dec/03/2015 07:31:36 by RouterOS 6.33.2
# software > #
/interface ethernet
set [ find default-name=ether2 ] master-port=ether1
set [ find default-name=ether3 ] master-port=ether1
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-128-cbc
add enc-algorithms=3des name=SbocaCalltek pfs-group=none
/ip pool
add name=pool1 ranges=10.255.252.3-10.255.255.254
/ip dhcp-server
add address-pool=pool1 disabled=no interface=ether1 name=server1
/ppp profile
set *FFFFFFFE dns-server=8.8.8.8
/routing ospf area
add area-id=10.0.0.0 name=VPN

/routing ospf instance
set [ find default=yes ] router-id=10.255.0.1
/tool user-manager customer
set admin access=
own-routers,own-users,own-profiles,own-limits,config-payment-gw
/interface l2tp-server server
set enabled=yes
/interface pptp-server server
set enabled=yes
/interface sstp-server server
set enabled=yes
/ip address
add address=
add address=10.255.0.1/16 disabled=yes interface=ether1 network=10.255.0.0
add address=172.17.0.1/16 interface=ether1 network=172.17.0.0
/ip dhcp-server network
add address=10.255.0.0/16 dns-server=10.255.0.1 gateway=10.255.0.1
/ip dns
set allow-remote-requests=yes servers=75.75.75.75,75.75.76.76
/ip firewall filter
add chain=input protocol=icmp
add chain=input dst-port=8291 protocol=tcp
add chain=input dst-port=8010 protocol=tcp
add chain=input dst-port=8728 protocol=tcp
add chain=input dst-port=443 protocol=tcp
add chain=input dst-port=1723 protocol=tcp
add chain=input dst-port=500 protocol=udp
add chain=input connection-state=established,related
add action=drop chain=input in-interface=ether8
add chain=forward connection-state=established,related
add action=drop chain=forward connection-state=invalid in-interface=ether8
add chain=input disabled=yes dst-port=500 protocol=udp
add chain=input disabled=yes dst-port=1701 protocol=udp
add action=log chain=input disabled=yes log-prefix=OSPF-IN-LinkLocal
protocol=ospf src-address=172.17.0.1
add action=drop chain=input disabled=yes protocol=ospf src-address=172.17.0.1
/ip firewall nat
add chain=srcnat dst-address=192.168.150.0/24 src-address=172.17.0.0/16
add action=masquerade chain=srcnat out-interface=ether8
add action=masquerade chain=srcnat out-interface=ether8 src-address=
172.17.0.0/16
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www port=8010
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/ppp secret
add local-address=172.17.0.1 name=Site1
password= profile=default-encryption remote-address=172.17.0.4
service=sstp
add local-address=172.17.0.1 name=Site2
password= profile=default-encryption remote-address=172.17.0.5
service=sstp
add local-address=172.17.0.1 name=Site3 password=
profile=default-encryption remote-address=172.17.0.7 service=sstp
add local-address=172.17.0.1 name=Site4 password=
profile=default-encryption remote-address=172.17.0.6 service=sstp

/routing ospf network
add area=VPN network=172.17.0.0/16
add area=VPN network=10.0.0.0/8
/system clock
set time-zone-name=America/Chicago
/system identity
set name=»VPN Host»
/system routerboard settings
set cpu-frequency=1200MHz memory-frequency=1066DDR
/tool romon port
add
/tool user-manager database
set db-path=user-manager

My goal is to have access to my site LAN’s and my Sites remote addresses.
My LAN side addresses are as follows:
Site1 = 10.0.4.1/24
Site2 = 10.0.5.1/24
Site3 = 10.0.7.1/24
Site4 = 10.0.6.1/24
VPN Server = 10.255.0.1/16 (I have tried this recently)

When I changed the local address from 172.17.0.1 to a unique ip address in my vpn server example would be 10.255.0.4 or 10.255.0.5 and I have the sites reconnect I am able to ping and get access to the site via the new 10.255.0.4 IP address, but the remote address of 172.17.0.4 is no longer active.

Suggestions or ideas would be helpful on my issue.

Источник

Здравствуйте.
Прошу помощи
Есть CCR-1016-12G, с последней стабильной версией прошивки. Внутренняя сеть на бридже и 2 провайдера на двух соседних портах.
Несколько дней назад Провайдер 1 отключил мой порт у себя с формулировкой: От вас идет кольцо. Стали разбираться вместе с технарями провайдера, в чем дело, вот что удалось выяснить:

Мои подключения
Провайдер 1: eth1-wan1 (со стороны провайдера cisco 6509) — Вот у этого провайдера кольцо выскочило.
Провайдер 2: eth2-wan2 (со стороны провайдера cisco 6509)
Причем- это одна и та же циска Т.е оба провайдера приезжают В ОДНУ. Это офисное здание и какие там договоренности между провайдерами и владельцами здания, я не знаю, но несколько месяцев всё было хорошо, всё работало, пока в помещении, где проходит кабель(медь) от провайдера 1, строители не обрезали наш линк. Кабель, со слов провайдера 1 восстановили, но вот такие чудеса теперь имеют место быть:

Отключил я порт eth1-wan1 и стали мы с админом провайдера 1 смотреть что будет при подключении. На его циске, после того, как я включил порт 1 (xxxx.xxxx.xxxx — МАС моего eth1-wan1 :
>sh mac-address-table address xxxx.xxxx.xxxx
Legend: * — primary entry
age — seconds since last seen
n/a — not available

vlan mac address type learn age ports
——+—————-+———+——+———-+—————————
Module 8[FE 1]:
* 45 xxxx.xxxx.xxxx dynamic Yes 10 Gi8/43
Module 8[FE 2]:
* 45 xxxx.xxxx.xxxx dynamic Yes 5 Gi8/43

FE1 и FE2, по словам провайдера, сквозная нумерация записей в таблице МАК-адресов.

У себя я включил на всех WAN портах loopback protect с отключением порта на 1 минуту и вот что вижу за 3 дня:
(XX:XX:XX:XX:XX:45 и XX:XX:XX:XX:XX:46 MACи eth1 и eth2)

Mar/15/2019 13:42:04 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/15/2019 17:44:22 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/16/2019 15:25:35 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/16/2019 22:27:12 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/17/2019 14:14:36 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/18/2019 07:31:05 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/18/2019 09:12:46 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/18/2019 15:44:35 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/18/2019 18:33:47 interface,warning eth2-wan2 received loop protect packet originated from XX:XX:XX:XX:XX:46 (eth2-wan2)
Mar/19/2019 16:47:47 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)
Mar/20/2019 08:59:14 interface,warning eth1-wan1 received loop protect packet originated from XX:XX:XX:XX:XX:45 (eth1-wan1)

Т.е. каждый раз интерфейс ловит кольцо от самого себя. И из всех случаев, событие один раз произошло на 2-м интерфейсе.
Подскажите, в какую сторону копать ? Провайдер уверяет, что у них «всё хорошо, попробуйте поменять роутер». Совет хороший, но для меня в данный момент невыполнимый.

Mikrotik discarding packet locally originated

Wed Apr 27, 2022 11:17 am

I’ve manually added all VLAN interfaces for neighbourship in OSPF with network type as point to point and that’s it. The OSPF costs are set pretty much in the best possible way that I could think of in my head and it is running very smoothly apart from the fact that I’m getting bombarded with these errors.

One very strange thing about this, is that, MKTs with only 1 neighbour will not have ANY of these errors appear, ever. If I add one more neighbour, the error will appear in both interfaces.

Any clue on why’s this happening?

P.S. I’ve checked all IP addresses and made sure they are correctly set so no other MKT has the same one with another one or any link in regards to that.

Re: OSPF Error — Discarding packet locally originated [SOLVED]

Wed Apr 27, 2022 11:51 am

Error is because the router receives a message containing its own router-id.
Two more things to check:
* make sure all neighbors have unique router-ids
* if you have connection tracking enabled, then try to set up raw rules in prerouting and output chains for OSPF traffic with action=»no-track»

If that does not help, then you have an actual L2 loop in your network.

Re: OSPF Error — Discarding packet locally originated

Wed Apr 27, 2022 1:39 pm

Error is because the router receives a message containing its own router-id.
Two more things to check:
* make sure all neighbors have unique router-ids
* if you have connection tracking enabled, then try to set up raw rules in prerouting and output chains for OSPF traffic with action=»no-track»

If that does not help, then you have an actual L2 loop in your network.

Источник

Mikrotik discarding packet locally originated

Mon Jan 16, 2012 11:55 pm

I don’t know why i seeing ip address of router itself in log.

22:41:48 route,ospf,error src address=fe80::20c:42ff:febf:91c1
22:41:58 route,ospf,error Discarding packet: locally originated
22:41:58 route,ospf,error src address=fe80::20c:42ff:febf:91c1
22:42:08 route,ospf,error Discarding packet: locally originated
22:42:08 route,ospf,error src address=fe80::20c:42ff:febf:91c1
22:42:18 route,ospf,error Discarding packet: locally originated
22:42:18 route,ospf,error src address=fe80::20c:42ff:febf:91c1
22:42:28 route,ospf,error Discarding packet: locally originated
22:42:28 route,ospf,error src address=fe80::20c:42ff:febf:91c1

This problem shows even if i set all passive and active only one interface.

[majkls@xxx] > /routing ospf-v3 export
# jan/16/2012 22:53:12 by RouterOS 5.11
#
/routing ospf-v3 instance
set default disabled=no distribute-default=never metric-bgp=auto metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20 metric-static=20 name=default
redistribute-bgp=no redistribute-connected=as-type-1 redistribute-other-ospf=no redistribute-rip=no redistribute-static=no router-id=xxxx
/routing ospf-v3 area
set backbone area-id=0.0.0.0 disabled=no instance=default name=backbone type=default
/routing ospf-v3 interface
add area=backbone cost=5 dead-interval=40s disabled=no hello-interval=10s instance-id=0 interface=ether3 network-type=default passive=no priority=1 retransmit-interval=5s
transmit-delay=1s use-bfd=no

Источник

Mikrotik discarding packet locally originated

Thu Dec 03, 2015 3:57 pm

Hoping to get some help and insite as to what is going on. I believe I understand what is happening and why the error is happening but I don’t know how to resolve the issue.

Was looking at my logs recently and saw this error happening a bunch.

07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1
07:45:27 route,ospf,error Discarding packet: locally originated
07:45:27 route,ospf,error src address=172.17.0.1

I believe it is due to when I am creating my PPP Secrets I am using the same local address. Everything that I have read online for help on creating a PPTP tunnel seems to say to make the local address the same. Everything works the way that I want it to work, but my logs are getting flooded by this error. I think that if I were to make the local address unique for each one I will be able to resolve the error.

This is a small portion of my PPTP server file.

# dec/03/2015 07:31:36 by RouterOS 6.33.2
# software > #
/interface ethernet
set [ find default-name=ether2 ] master-port=ether1
set [ find default-name=ether3 ] master-port=ether1
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-128-cbc
add enc-algorithms=3des name=SbocaCalltek pfs-group=none
/ip pool
add name=pool1 ranges=10.255.252.3-10.255.255.254
/ip dhcp-server
add address-pool=pool1 disabled=no interface=ether1 name=server1
/ppp profile
set *FFFFFFFE dns-server=8.8.8.8
/routing ospf area
add area-id=10.0.0.0 name=VPN

/routing ospf instance
set [ find default=yes ] router-id=10.255.0.1
/tool user-manager customer
set admin access=
own-routers,own-users,own-profiles,own-limits,config-payment-gw
/interface l2tp-server server
set enabled=yes
/interface pptp-server server
set enabled=yes
/interface sstp-server server
set enabled=yes
/ip address
add address=
add address=10.255.0.1/16 disabled=yes interface=ether1 network=10.255.0.0
add address=172.17.0.1/16 interface=ether1 network=172.17.0.0
/ip dhcp-server network
add address=10.255.0.0/16 dns-server=10.255.0.1 gateway=10.255.0.1
/ip dns
set allow-remote-requests=yes servers=75.75.75.75,75.75.76.76
/ip firewall filter
add chain=input protocol=icmp
add chain=input dst-port=8291 protocol=tcp
add chain=input dst-port=8010 protocol=tcp
add chain=input dst-port=8728 protocol=tcp
add chain=input dst-port=443 protocol=tcp
add chain=input dst-port=1723 protocol=tcp
add chain=input dst-port=500 protocol=udp
add chain=input connection-state=established,related
add action=drop chain=input in-interface=ether8
add chain=forward connection-state=established,related
add action=drop chain=forward connection-state=invalid in-interface=ether8
add chain=input disabled=yes dst-port=500 protocol=udp
add chain=input disabled=yes dst-port=1701 protocol=udp
add action=log chain=input disabled=yes log-prefix=OSPF-IN-LinkLocal
protocol=ospf src-address=172.17.0.1
add action=drop chain=input disabled=yes protocol=ospf src-address=172.17.0.1
/ip firewall nat
add chain=srcnat dst-address=192.168.150.0/24 src-address=172.17.0.0/16
add action=masquerade chain=srcnat out-interface=ether8
add action=masquerade chain=srcnat out-interface=ether8 src-address=
172.17.0.0/16
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www port=8010
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/ppp secret
add local-address=172.17.0.1 name=Site1
password= profile=default-encryption remote-address=172.17.0.4
service=sstp
add local-address=172.17.0.1 name=Site2
password= profile=default-encryption remote-address=172.17.0.5
service=sstp
add local-address=172.17.0.1 name=Site3 password=
profile=default-encryption remote-address=172.17.0.7 service=sstp
add local-address=172.17.0.1 name=Site4 password=
profile=default-encryption remote-address=172.17.0.6 service=sstp

/routing ospf network
add area=VPN network=172.17.0.0/16
add area=VPN network=10.0.0.0/8
/system clock
set time-zone-name=America/Chicago
/system identity
set name=»VPN Host»
/system routerboard settings
set cpu-frequency=1200MHz memory-frequency=1066DDR
/tool romon port
add
/tool user-manager database
set db-path=user-manager

My goal is to have access to my site LAN’s and my Sites remote addresses.
My LAN side addresses are as follows:
Site1 = 10.0.4.1/24
Site2 = 10.0.5.1/24
Site3 = 10.0.7.1/24
Site4 = 10.0.6.1/24
VPN Server = 10.255.0.1/16 (I have tried this recently)

When I changed the local address from 172.17.0.1 to a unique ip address in my vpn server example would be 10.255.0.4 or 10.255.0.5 and I have the sites reconnect I am able to ping and get access to the site via the new 10.255.0.4 IP address, but the remote address of 172.17.0.4 is no longer active.

Suggestions or ideas would be helpful on my issue.

Источник

Mikrotik discarding packet locally originated

Sat Feb 06, 2010 6:23 am

Quick overview — wheel and spoke network with IPSec over IPIP tunnel and OSPF running on the IPIP interfaces (based on this article http://wiki.mikrotik.com/wiki/IPSec_VPN . _and_Cisco but using OSPF instead of RIP and both routers are Mikrotiks). I am only getting these errors on the IPIP tunnel addresses on the central router that the rest dial in to. All routers recently upgraded to ROS_4.5 and that is when I started to notice the errors in my log files. example error below —

20:14:25 route,ospf,error Discarding packet: locally originated
20:14:25 route,ospf,error src address=10.0.1.117 awsmith

Re: route ospf error -> Discarding packet: locally originated

Tue Mar 02, 2010 3:43 am

Quick overview — wheel and spoke network with IPSec over IPIP tunnel and OSPF running on the IPIP interfaces (based on this article http://wiki.mikrotik.com/wiki/IPSec_VPN . _and_Cisco but using OSPF instead of RIP and both routers are Mikrotiks). I am only getting these errors on the IPIP tunnel addresses on the central router that the rest dial in to. All routers recently upgraded to ROS_4.5 and that is when I started to notice the errors in my log files. example error below —

20:14:25 route,ospf,error Discarding packet: locally originated
20:14:25 route,ospf,error src address=10.0.1.117 he1ium

Re: route ospf error -> Discarding packet: locally originated

Sat Mar 13, 2010 12:22 am

Re: route ospf error -> Discarding packet: locally originated

Sat Mar 13, 2010 12:29 am

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 8:35 am

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 6:55 pm

Hello — we have a thread started a few days before yours, and we are having the same problem. Dropping OSPF routes, usually the same couple, but it is very often. One of the routes it drops is even an ethernet link, Odd thing is which router drops the route:

Border Router -ethernet> RB433AH (4.6) -Bonded link to> RB600 (4.6) -ethernet> rb433ah(4.6)

This RB433AH (4.6) drops the route to the wireless interface of This rb433ah(4.6)

Very odd, and extreamly frustratin as this seems to happen more during peak times, and is on some of our core routers. Any help would be extreamly helpful, Mikrotik.

Re: route ospf error -> Discarding packet: locally originated

Wed Mar 17, 2010 8:32 pm

This is what I got from Mikrotik and it didn’t work (see below). By setting interfaces to passive (on one side, other side, both sides), the tunnel addresses appears to be up but the remote LAN networks were not distributed —

Yes it is possible.
Lets say we have setup 10.1.1.1/24 on ether1 and you want to run ospf on
10.1.1.0/24 network only.

Setup as follows
/routing ospf network add network=10.1.1.0/24
/routing ospf interface
add interface=ether1
add interface=all passive=yes

Nothing complicated. Chupaka

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 12:29 am

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 7:18 am

Re: route ospf error -> Discarding packet: locally originated

Thu Mar 18, 2010 9:45 am

Re: route ospf error -> Discarding packet: locally originated

Fri Mar 19, 2010 7:11 am

Re: route ospf error -> Discarding packet: locally originate

Fri Jan 27, 2012 12:42 am

Re: route ospf error -> Discarding packet: locally originate

Wed Apr 10, 2013 8:36 am

Re: route ospf error -> Discarding packet: locally originate

Sun Sep 01, 2013 10:26 am

Re: route ospf error -> Discarding packet: locally originate

Sun Sep 01, 2013 6:07 pm

Have you attempted to change the ospf network type or set static ospf neighbors? Setting a static neighbor will remove multicast from the mix and changing from broadcast to ptp will remove DR/BDR elections.

I would be curious to see what RIP or BGP do over the same physical topology — might help you sort out whether you have an ospf specific issue or a physical and/or logical topology issue.

Re: route ospf error -> Discarding packet: locally originate

Mon Mar 31, 2014 5:25 pm

I’m struggling with that in our network for about a year.
We have changed most of devices to nmba mode — but route propagation was taking too long.

We can observe that issue on CCR’s working versions 6.7,6.10, 1100AHx2 ver 6.7 and almost on all other devices with OSPF.
We where thinking the issue is with radio link, but it is happening with all radio links that we have (ubnt, MikroTik, Ceragon, SAF). We can find it also when two devices are connected on cable.

My current status — I put few firewall rules to block packets with source IP the same as device.
Error disappear.

> /ip address print where interface=ether1
Flags: X — disabled, I — invalid, D — dynamic
# ADDRESS NETWORK INTERFACE
1 10.240.14.254/24 10.240.14.0 ether1

> /ip firewall filter print
Flags: X — disabled, I — invalid, D — dynamic
0 chain=input action=drop protocol=ospf src-address=10.240.14.254

I was trying to track them on device that is connected to that one, but without luck — packets are not coming from outside.

When I enabled packets logging, my results:
15:00:48 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1764
15:01:01 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1752
15:02:31 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1764
15:02:56 firewall,info input: in:ether1 out:(none), proto 89, 10.240.14.254->224.0.0.5, len 1752

Hope that will give some kind of directions.
RB1100AHx2 RoS v6.7

Источник