21 Jan
2017
21 Jan
'17
5:14 p.m.
Hello all,
If you may have noticed, there is a recent IPIP tunnel with a 44net
gateway (which you may have seen flapping on your Mikrotik routers -
44.130.120.0/24 via 44.130.120.65).
This is a experimental setup to allow tunneling via BGP announced 44net
gateways, with no real hosts there yet.
Ampr-ripd newer than 1.13 will ignore this RIP broadcast (an update will
be available soon).
Our first step to make it run on Mikrotik routers (this will stop the
route flapping):
Announcing the Mikrotik RIPv2 AMPR Gateway Setup Script 3.0 (21.Jan.2017)
- Added support for tunnels with BGP announced 44net endpoints
If you already use v.2.x, only update ampr_gw and from the archive file
and add manually the new parameter "AmprDefaultGw" to your config file
(see the example file in the archive).
"AmprDefaultGw" can be set to your gateway WAN interface name or the
correct gateway IP for your router.
Download as usual:
RSC file: http://www.yo2loj.ro/hamprojects/ampr-gw-3.0.rsc
ZIP archive: http://www.yo2loj.ro/hamprojects/ampr-gw-3.0.zip
Greetings,
Marius, YO2LOJ
21 Jan
21 Jan
5:34 p.m.
On Sat, Jan 21, 2017 at 9:14 AM, Marius Petrescu <marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hello all,
If you may have noticed, there is a recent IPIP tunnel with a 44net
gateway (which you may have seen flapping on your Mikrotik routers -
44.130.120.0/24 via 44.130.120.65).
This is a experimental setup to allow tunneling via BGP announced 44net
gateways, with no real hosts there yet.
Marius,
If it's helpful for your test data, we successfully used 44.24.221.1
as a gateway for 44.24.240.0/20 about three years ago. This worked
fine for encap users that did not have an extra 44.0.0.0/8 route in
their table (for some reason this configuration is popular, despite
breaking things). We used this gateway until it was blocked in a
portal update.
Of course this is different than your test because our gateway was not
contained within the advertised network.
Tom KD7LXL
6:16 p.m.
On 1/21/2017 12:14 PM, Marius Petrescu wrote:
Our first step to make it run on Mikrotik routers
(this will stop the
route flapping):
Announcing the Mikrotik RIPv2 AMPR Gateway Setup Script 3.0 (21.Jan.2017)
- Added support for tunnels with BGP announced 44net endpoints
If you already use v.2.x, only update ampr_gw and from the archive file
and add manually the new parameter "AmprDefaultGw" to your config file
(see the example file in the archive).
"AmprDefaultGw" can be set to your gateway WAN interface name or the
correct gateway IP for your router.
Hi Marius...added new script and still flaps here.
ampr_config:
#
# RIPv2 based AMPR Tunnel setup script for RouterOS v2.2
#
# by YO2LOJ, Marius <marius(a)yo2loj.ro>
#
# This script holds the runtime parameter definitions
#
# --------------------------------------------------------------
# Setup parameters (change as needed)
#
# These parameters are used by
# the "ampr_gw" script which is
# called by the scheduled "update_ampr"
# wrapper script.
# --------------------------------------------------------------
# Your gateway interface
:global AmprPublicIp "24.115.112.147" ;
# router local AMPR IP
:global AmprMyIp "44.56.53.1" ;
# routing distance for AMPR routes
:global AmprRoutingDistance 50 ;
# global delay between steps
:global AmprDelay "10ms" ;
#gateway IP
global AmprDefaultGw "24.115.112.147" ;
6:22 p.m.
On 1/21/2017 1:16 PM, Leon Zetekoff wrote:
(
# Your gateway interface
:global AmprPublicIp "24.115.112.147" ;
# router local AMPR IP
:global AmprMyIp "44.56.53.1" ;
# routing distance for AMPR routes
:global AmprRoutingDistance 50 ;
# global delay between steps
:global AmprDelay "10ms" ;
#gateway IP
global AmprDefaultGw "24.115.112.147" ;
made this change and still
flaps:
# gateway Interface
global AmprDefaultGw "SECV Cable 100m" ;
7:07 p.m.
Hi Leon,
You are missing the double colon in front of "global":
:global AmprDefaultGw "24.115.112.147" ;
On 2017-01-21 20:22, Leon Zetekoff wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 1/21/2017 1:16 PM, Leon Zetekoff wrote:
(
# Your gateway interface
:global AmprPublicIp "24.115.112.147" ;
# router local AMPR IP
:global AmprMyIp "44.56.53.1" ;
# routing distance for AMPR routes
:global AmprRoutingDistance 50 ;
# global delay between steps
:global AmprDelay "10ms" ;
#gateway IP
global AmprDefaultGw "24.115.112.147" ;
made this change and still
flaps:
# gateway Interface
global AmprDefaultGw "SECV Cable 100m" ;
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
7:11 p.m.
On 1/21/2017 2:07 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Leon,
You are missing the double colon in front of "global":
:global AmprDefaultGw "24.115.112.147" ;
Marius...I saw that after I posted and corrected it and still doesnt work
ldz
7:23 p.m.
Leon,
Do you have 2 routes in your routing table?
44.130.120.0/24 ampr-44.130.120.65 reachable
44.130.120.65 <Your Interface> reachable
On 2017-01-21 21:11, Leon Zetekoff wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 1/21/2017 2:07 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Leon,
You are missing the double colon in front of "global":
:global AmprDefaultGw "24.115.112.147" ;
Marius...I saw that after I posted and corrected it and still doesnt work
ldz
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
7:29 p.m.
Ok. I know what's wrong.
The route is created only at tunnel creation.
So you need to delete the ampr-44.130.120.65 tunnel interface.
On first run it will be recreated and it will be ok.
Also there probably will be an invalid route to 44.130.120.0/24 which
has to be cleared by hand.
Marius, YO2LOJ
24 Jan
24 Jan
3:20 p.m.
On 21/01/2017 19:29, Marius Petrescu wrote:
Ok. I know what's wrong.
The route is created only at tunnel creation.
So you need to delete the ampr-44.130.120.65 tunnel interface.
On first run it will be recreated and it will be ok.
Also there probably will be an invalid route to 44.130.120.0/24 which
has to be cleared by hand.
Hi Marius,
Thanks for the update. I've experienced the same flapping of
ampr-44.130.120.6. Deleting the tunnel and associated route fixed it for me.
73 Nick
2657
days inactive
2660
days old
8 comments
4 participants
participants (4)
-
Leon Zetekoff -
Marius Petrescu -
Nick G4IRX -
Tom Hayward