Marius et al.
Presently my server employs ampr-ripd-2.3
Did not observed any issues so far.
encap.txt file at the very beginning contains two entries:
#
# encap.txt file - saved by ampr-ripd (UTC) Mon Jun 5 03:20:34 2017
#
route addprivate 44.0.0.1/32 encap 169.228.34.84
route addprivate 44.0.0.2/32 encap 169.228.66.251
RIP broadcast are coming through as before.
Best regards.
Tom - SP2L
Hello everyone,
To be in line with the latest ampr-ripd & co, here a new amprd version
that forces the sending of call home data to use the tunnel's IP as its
source IP address.
Also, it supports multiple call home info's, one for each tunnel configured.
Interactive map which is available at
http://yo2tm.ampr.org/ampr-map/
For those that do not want to participate, there is no need to upgrade.
Download:
http://www.yo2loj.ro/hamprojects/amprd-2.1.tgzhttp://yo2tm.ampr.org/hamprojects/amprd-2.1.tgz
Have fun,
Marius, YO2LOJ
Hello,
For those using amprd (like myself), here a small update:
- added map notification every 5 min. There is a new config file
parameter for it, check the example config
- modified the default ampr gw address to the new IP. This has actually
no effect until the RIP broadcasts for 44.0.0.1 will change to the new
IP (44.0.0.1 still uses the old GW address).
Older versions, like 1.5 and 1.6 will switch gateways automatically if
presented with a new gw for 44.0.0.1 in the RIP data, so unless you want
to be on the map with a blue dot, there is no urge to update (live map
is at http://yo2tm.ampr.org/ampr-map/)
As always:
http://www.yo2loj.ro/hamprojects/http://yo2tm.ampr.org/hamprojects/
Marius, YO2LOJ
Hello,
With the changes taking place I have been monitoring both the " old "
and the " new " addresses. I'm receiving rip broadcasts from both and
additionally similar broadcasts to the two lines below on the " old "
address only.
amprgw.sysnet.ucsd.edu > 172.16.1.4: IP (tos 0x0, ttl 111, id 14685,
offset 0, flags [none], proto UDP (17), length 90)
218-228-138-51f1.osk3.eonet.ne.jp.25465 > mb7njd.ampr.org.3544: [udp
sum ok] UDP, length 62
I have little knowledge of the meaning of this and would appreciate
someone explaining it to me.
Thanks in advance.
( Monitored from eth0 at 172.16.1.4 which is in DMZ )
Regards,
Ian..
> Recently some important changes were
> performed pertaining whole [44net] community.
> Today I made few test in order to check
> accessibility of [44net] hosts.
Currently IPIP routing via the old amprgw is broken for our network.
This is the result of several changes in the local config and at UCSD.
I am not going to fix it, it should all be OK again after the change on monday.
(it should not affect BGP routing of our network and traffic from other gateways)
Rob
Hi 44net,
I just signed up AMPRNet but wasn't able to find my country [China] in
the list. So I tried to register a new region, am I doing it correct?
Thanks.
--
Regards,
Quan Zhou
E271C0D1BD90012B8D8EECF6F822BC9F8E1C35C8
quanzhou822(a)gmail.com
https://keybase.io/qzhou
I put in a request on 2017-05-18 for a netblock since I've moved to
Nevada, but I haven't gotten the allocation. I can't seem to find a
direct contact for the administrator.
For those who want to join the map test with mikrotik routers:
- create a new script containing a single line (replace the call and
locator, of course):
/tool fetch mode=http
url="http://44.182.21.1:59001/mikrotik?id=yo2loj@kn05os" keep-result=no
- in the scheduler get it to run every 5 minutes.
That's it.
ampr-ripd clients appear as green dots, MT routers as reddish ones.
http://44.182.21.1/ampr-map/
Marius, YO2LOJ
