44net

44net@mailman.ampr.org

3179 discussions

by Rob Janssen

> Subject: > Re: [44net] 192.168.0.2 gateway > From: > Mark Phillips <g7ltt(a)g7ltt.com> > Date: > 02/06/2017 02:34 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > I would say "no". > > Y'see, we don't know what kind of network things are riding over. the > network in question could be (for example) a mesh install configured > similar to that of the local cable company. The users get real addresses > but the infrastructure does not. I think precisely this is the reason why such addresses should be rejected: The user may have the wrong assumption that the address to be entered here is the address of the system terminating the tunnel, while in reality it has to be the internet-visible address that supposedly is NATted to the tunnel gateway. So, what happens in the local infrastructure does not matter. Rob

8 years, 5 months

192.168.0.2 gateway

by Brian Kantor

I just spotted this entry in the latest encap file: route addprivate 44.74.0.128/28 encap 192.168.0.2 Unless you're doing something highly unusual, setting your gateway address in the portal to 192.168.0.2 probably is a mistake since it's not reachable from the Internet. - Brian

8 years, 5 months

Re: [44net] was Verifying the identities of IP coordinators

by Steve L

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.

8 years, 5 months

PACCOMM TNC-320 Smoke

by vk1kw

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

8 years, 5 months

BGP announced gateways and Mikrotik RIPv2 AMPR Gateway Setup Script 3.0

by Marius Petrescu

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

8 years, 5 months

Re: [44net] Forum for Packet, AX.25

by Steve L

In addition to what has already been posted: the TAPR nos-bbs list http://www.tapr.org/mailman/listinfo/nos-bbs

8 years, 5 months

Forum for Packet, AX.25

by Adi Linden

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

8 years, 5 months

44net IP Block for D-STAR Hosting Use

by Storer, Darren

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

8 years, 5 months

Re: [44net] BGPed Gateway

by Rob Janssen

> 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

8 years, 5 months

BGPed Gateway

by Adi Linden

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

8 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net