Hello everyone!
Does anyone have any experience setting up VyOS for use on the AMPR
network? I have the IPIP tunnel to UCSD set up, however, I don't know how
to proceed from there in terms of RIP.
This is what I did so far:
set interfaces tunnel tun0
set interfaces tunnel tun0 local-ip 'wanip'
set interfaces tunnel tun0 remote-ip 169.228.66.251
set interfaces tunnel tun0 encap ipip
set interfaces tunnel tun0 descr "Tunnel to AMPR Gateway"
set interfaces tunnel tun0 multicast enable
set protocols static table 1 interface-route 0.0.0.0/0 next-hop-interface
tun0
set policy route SOURCE_ROUTE rule 10 set table 1
set policy route SOURCE_ROUTE rule 10 source address 44.0.0.0/16
set interfaces ethernet eth1 vif 44 policy route SOURCE_ROUTE
set protocols rip interface eth1.44
set interfaces ethernet eth1 vif 44 ip rip authentication
plaintext-password [therippass]
--
Miguel Rodriguez
12th Grade Student
MIGUELR-DN42 / KM4VYU
miguemely101(a)gmail.com
Tel: *561-758-0631*
*Accredited District Since 2008; Re-certification - January 2013*
Home of Florida's first LEED Gold Certified School
*Disclaimer*: Under Florida law, e-mail addresses are *public records*. If
you do not want your e-mail address released in response to a public
records request, do not send electronic mail to this entity. Instead,
contact this office by phone or in writing.
First I wanted to mention I am glad to read Bjorn's message about
adding some content to the network.
Keeping in contact is key. Be that a coordinator or any host on the
amprnet. Seems every few months on here we are discussing how someone
is sending out random packets, and a straight forward way to get a
hold of people would be helpful.
Some time back it was brought up to have a whois server or something
like that. I bet I can guess the status of that.
As for everyone having an ampr.org email address, perhaps a forwarding
service like the arrl.net addresses? Then there is the possible spam
problem, and the fact that someone would need to set up such a
service.
Overall a lot of good ideas are brought up on this list, so few ever
happen. The only solution I am offering is everyone should help
spread the word and try and get more people involved with moving this
network forward. I wish I had better coding skills.
One of the core problems at least in my country where the ampr/44net
space is not well utilized is the lack of higher speed equipment to
build a network. You really have to be part of a well organized club
with site connections to do anything microwave on any big scale from
what I have seen.
Hello All,
I recently had a power supply problem and it has let the smoke out of my
PacComm TNC-320 packet modem.
While I have the manual, I do not have a circuit diagram and only have a
partial id on one of the cooked ICs U17.
The partial number is MC xxxxx06P (I think) and is on the main board across
the RS-232 D9 connector circuit.
Could you check your circuit diagram, parts list or slide off the cover and
have a look and let me know what the U17 IC is please?
Many Thanks
Rob
VK1KW
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
Is there a good forum to discuss packet, AX.25 and such things? After some 20 years of abstinence from packet I am really interested in getting something going. In my area APRS is alive and well, but packet on VHF or UHF is dead and has been dead for a long time. Lots of equipment is still out there, such as KPC-3 and the like, just not being used.
Although I am very interested in getting packet going again, I have no idea where to start. Got hardware to spare, but where to start? What’s out there for software (OpenBCM, JNOS, BPQ32, what else?)…
I realize that this is probably not the avenue to discuss, but perhaps someone can point me in the right direction of where to start looking, where to ask.
Thanks,
Adi
Hi Chris,
Life at Ofcom has overtaken amateur radio activity almost totally for the
last 3 1/2 years but I'm starting to "emerge" again, I'm sure that you
understand life's nasty way of getting in the way of hobby time.
A number of D-STAR services are still hosted on my servers, including the
central dsync reporting tool ( http://dsync.dstar.info/ is the public
reporting page but there is an extensive admin portal too) and also some
reflectors including REF006 ( http://ref006.dstargateway.org/ ). The
servers are due to be re-homed to an A&A data centre, where a few of the
staff are amateurs. Some of the D-STAR gateway admins have previously asked
about accessing services via ampr.org IP addresses; do you think that this
would be an appropriate use of the resource?
Tentatively I asked A&A if they could BGP advertise a subnet of ampr.org
and they'd be happy to do that, so it's more of a question of whether
D-STAR services for hams would be okay to provide via AMPRNet? Are there
any rules that would prevent the dsync pages being dual homed via public IP
space and ampr.org IP space? Has anyone managed to regularly route digital
voice (UDP) over AMPRNet?
Sorry for all the questions but I know that you will know the answers...
73 de Darren
G7LWT
> With the BGP advertisement my subnet is reachable via internet and can reach anywhere via internet. Other 44 networks can reach my subnet as long as they are also advertised via BGP or have appropriate NAT rules to allow internet access. I can reach any BGP advertised 44 net addresses. However, I should not be able to reach any non-BGP advertised 44 net addresses unless there is a gateway (at USCD?) that allows for access to IPIP only 44 networks from 44 networks.
> I guess I don’t know the network topology of the 44 net or the functions that are provided at the UCSD gateway.
> I assumed that in order to reach IPIP only networks I would have to also establish IPIP tunnelling from each 44 host or gateway using subnets of my BGP advertised subnet.
When the system that handles the traffic that comes in on your BGP advertised route also has a public IP address and is made member of the IPIP mesh for the same subnet it advertises on BGP, you can talk to everyone that is on the IPIP mesh.
They will send traffic for you via the IPIP tunnel that they establish because you are in the list maintained via portal.ampr.org and transmitted using RIP from the gateway at UCSD.
You then only use IPIP for traffic between hosts on the IPIP mesh, not for the remainder of traffic to and from internet.
Rob
Hi,
I received a 44 net allocation and am successfully advertising it to the internet via my ISP.
I have been reading on the AMPRNet Wiki about IPIP tunnelling and Startampr. Are there best practices or anything else I need to be aware of before venturing into building the gateway?
On a related note, I have been using OpenVPN to provide publicly routable /32 IP addresses to individual Windows PC. I don’t see support for IPIP on Windows, are there any other tunnelling methods worth looking at, for Windows7 specifically, or is OpenVPN my best bet?
Thanks,
Adi
VA3ADI
Hi,
I wouldn't normally post here about this, but I see a couple of others
seem to have gotten a response from doing so.
I am new to amatuer radio and while I was getting my license someone
told me about APRMnet, so I decided to join. I put in a network
request back in november and got a response from the coordinator G1FEF
asking for clarification on my request. I responded via the portal,
however that has been the last I have heard.
I sent a follow-up email directly at the beginning of January, however
I haven't had any further response.
What should I do next?
Thanks,
- Mike, M6XCV