14 Jul
2014
14 Jul
'14
7:01 p.m.
Good evening,
I have the following routes concerning 44.140.0.1 on my system:
[lx1duc(a)LX044-17.ampr.org] > ip route print detail where 44.140.0.1 in
dst-address
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
0 ADb dst-address=0.0.0.0/0 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=20
scope=40 target-scope=10 bgp-as-path="60391" bgp-origin=igp
received-from=AS60391_v4
2 A S dst-address=44.140.0.0/16 gateway=ampr-44.140.0.1
gateway-status=ampr-44.140.0.1 reachable distance=210 scope=30
target-scope=10
3 Db dst-address=44.140.0.0/16 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=250
scope=40 target-scope=10
bgp-as-path="60391,51405,24611,3549,1299,1299,1299,2603,1653,2839,
8973"
bgp-atomic-aggregate=yes bgp-origin=igp
bgp-communities=3549:2682,3549:31528,51405:352,51405:1100,51405:2003,
51405:10010,51405:10012
received-from=AS60391_v4
(I deleted rule #1 as it is disabled).
When I do a traceroute to 44.140.128.7 from a system behind that
router, I can see that the packets come in via ethernet and they are
forwarded to the IPIP tunnel interface for 44.140.0.1, however the
Mikrotik router never sends any IPIP packets out via my upstream
ethernet connection.
When I add the following route:
4 A S dst-address=44.140.0.1/32 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=1
scope=30 target-scope=10
are actually sent out of the ethernet to the upstream. However there
is no response from 44.140.0.1 in any case.
(There is a possible work around by using different routing tables,
but depending on the type of rules, this could still have the same
effect.)
I'm not very sure how this can be solved, eventually by announcing
44.140.0.0/24 via commercial BGP.
Any ideas are welcome.
73 de Marc, LX1DUC