Hello. Is there any probel for a few days with yo2loj script? For a few
days I receive such a return in the logs of the mikrotik
"Jun / 06/2017 13:21:00 script, error AMPR: To few RIP entries available"
Regards
SP2GCH
I was wondering if the usual TCP window setting of 840 makes any sense in
our current mesh.
This setting was imposed by the assumption that our IP traffic will pass
over ax.25 connections, with their MTU and ACK limitations, and does not
affect AXIP, AXUDP or other transfer modes.
The question is: Is there anyone forwarding TCP/IP over AX.25 at this moment?
Because if not, we could drop that window setting in the routing daemons
and get a more streamlined data flow.
Marius, YO2LOJ
I'm planning on making some changes to the AMPRNet DNS robot that
will significantly alter the transaction response format. It will
still be human readable, but if you are analyzing the responses
using software of some kind, you'll have some work ahead of you.
How many of you who use the robot are using software to handle
the responses?
- Brian
I have finished documenting and putting up on my website what I call
AmprNAT. For those who attempting to get out via amprgate sourcing as
their lan IPs, this not only will prevent this from occurring but also
it will NAT you out as your gateway's IP... pending you're using a
distro of linux. It requires a static route in your route pointing to
your gateway, and then 3 lines of iptables rules.
You may read about it at:
https://n1uro.ampr.org/linuxconf/44nat.html
I believe Lynwood is adding info on the wiki for this.
--
I was reading a book about the history of glue... I couldn't
put it down. ...think about it...
--------
73 de Brian - N1URO/AFT1BR
email: (see above)
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
http://uronode.sourceforge.nethttp://axmail.sourceforge.net
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, New Jersey, Pennsylvania,
Rhode Island, and Vermont.
Hi,
Since everyone seems to like to use the most unusual script with
"original" settings without trying ever to understand what's happening,
I would remind you that there is a more or less "plug-and-play" solution
called amprd...
Let's assume a system with:
- 44net assignment: 44.128.1.0/24
- WAN on eth0 (let's assume 1.2.3.4)
- LAN on eth0 (192.168.1.1/24)
- AMPR on eth2 (44.128.1.0/24)
- We choose our GW IP to be 44.128.1.1
and that the internet access from the system is already set up, with NAT
and default gateway via WAN.
Now:
1. compile (make) and install (make install) amprd
2. create the following /etc/amprd.cfg:
-----------------------------------------------------------------
[ampr0]
prefix = 44.128.1.1
rip_receive = yes
rip_save = yes
-----------------------------------------------------------------
3. Set address 44.128.1.1/24 to your eth2 interface
4. Start amprd. And basically that's it: a fully functional mesh gateway.
If you want access from the internet to your subnet, too, instead of
just starting amprd, create the following ampr startup script:
-----------------------------------------------------------------
amprd
ip route add default via 169.228.34.84 dev ampr0 onlink table default
ip rule add from 44.128.1.1 table default
ip rule add from 44.128.1.1 to 44.128.1.0/24 table main
-----------------------------------------------------------------
This should do the trick.
Marius, YO2LOJ
All,
Once again, my WAN IP and Subnet changed (about 5 hours ago now).
I did reboot my GW; but my IP has not yet changed in the portal and I
cannot reach other 44subnets or the Internet.
I have logged in the Portal, removed the IP from the GW webform and hit
save (leaving only the DDNS hostname).
- Lynwood
KB3VWG
Hello everyone,
Since experimenting goes one, here a new ampr-ripd version that forces
the sending of call home data to use the tunnel's IP as its source IP
address.
Tnx. Lynwood for pointing out that necessity.
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.
And even if you do, not setting the -L parameter will not send any data,
the result being the same behavior like 2.1.1.
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.3.tgzhttp://yo2tm.ampr.org/hamprojects/ampr-ripd-2.3.tgz
Have fun,
Marius, YO2LOJ
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
