11 May
2018
11 May
'18
7:15 a.m.
Hello,
There is a problematic entry in the portal which needs our attention:
44.151.31.6 / 32 via 44.151.31.6, according to the portal allocated to
F1SXO, France, Occitanie, Haute Garonne
The problem is that the RIP entry 44.151.31.6 via 44.151.31.6 is wrong,
ilogical, and creates a routing loop.
On Mikrotik routers, this will sow as a flapping of the ampr-44.151.31.6
interface.
The solution for the moment is to filter that entry in the RIP filters
and delete the 2 routes to it and its associated interface by hand.
I had no time to check the behavior on ampr-ripd and amprd systems but
is basically lead to the flapping of the route.
After correcting this issue in the portal, on these systems, a remove of
the static route 44.151.31.6 via default gw should be necessary (ampr-gw
and amprd do not remove those static routes - known problem).
The final solution is to correct the entry in the portal.
Marius, YO2LOJ
11 May
11 May
7:21 a.m.
Hi again,
I think it would be useful to add a rule in the portal, not to allow a
44net gateway in its own subnet, unless the subnet is BGP announced and
at most a /24 subnet (higher netmasks can not be announced via BGP).
Marius, YO2LOJ
On 11.05.2018 09:15, Marius Petrescu wrote:
Hello,
There is a problematic entry in the portal which needs our attention:
44.151.31.6 / 32 via 44.151.31.6, according to the portal allocated to
F1SXO, France, Occitanie, Haute Garonne
9:51 a.m.
I have deleted that gateway entry from the portal. F1SXO can
re-add his gateway when he has the correct configuration data
to do so.
- Brian
On Fri, May 11, 2018 at 09:15:47AM +0300, Marius Petrescu wrote:
Hello,
There is a problematic entry in the portal which needs our attention:
44.151.31.6 / 32 via 44.151.31.6, according to the portal allocated to
F1SXO, France, Occitanie, Haute Garonne
The problem is that the RIP entry 44.151.31.6 via 44.151.31.6 is wrong,
ilogical, and creates a routing loop.
On Mikrotik routers, this will sow as a flapping of the ampr-44.151.31.6
interface.
The solution for the moment is to filter that entry in the RIP filters
and delete the 2 routes to it and its associated interface by hand.
I had no time to check the behavior on ampr-ripd and amprd systems but
is basically lead to the flapping of the route.
After correcting this issue in the portal, on these systems, a remove of
the static route 44.151.31.6 via default gw should be necessary (ampr-gw
and amprd do not remove those static routes - known problem).
The final solution is to correct the entry in the portal.
Marius, YO2LOJ
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2399
days inactive
2399
days old
2 comments
2 participants
participants (2)
-
Brian Kantor -
Marius Petrescu