44net

44net@mailman.ampr.org

3194 discussions

Amprnet vpn
by lleachii＠aol.com 17 Feb '17

17 Feb '17

Shawn, I'm lost; but I guess my inquires sum up to: - Are you running a stock installation of Ubuntu, or is it a version offered by the Virtual Machine Provider? - How are you "receiving the route information" and what do you mean by "but that would be it"? Did you receive route information via rip44d and confirm it by typing: ip route show table 44 ? Have you been successful at getting rip44d to run as a service? If the routes are there, this indicates you may have already made great progress. Did you attempt to ping or traceroute any IPs from an interface assigned an AMPR IP? If so, did you receive a reply? In any case, this means you are receiving the packets at the VM. We need to determine if the tunnel interface Up. Please verify by typing: ifconfig If you used startampr, you should see an interface listed as tunl0, it MIGHT say IPIP or UNSPEC, but you will recall you configured it for IPENCAP (this is because the Linux Kernel module for both are the same). Also note the names of your other interfaces, as the names used in the script must also be correct. Since Ubuntu 16.04, the Ethernet interfaces were no longer named: eth0, eth1, etc. Since I used eth0 and eth1 in documentation, you must account for variations in your system configuration. The ifconfig command will be most helpful to that end. You can also assign an IP to tunl0 (a commented-out line in the script allows for that). Lastly, have you ever received a copy of startampr from me? If you're using a script from Internet, that might be your problem (earlier versions contained less documentation). The current copy is only available on AMPR at: http://kb3vwg-010.ampr.org/amprnet_docs/start_ampr_version2/startampr Since that presents a chicken-and-the-egg problem for you at this time, contact me off-forum and we can arranging for you to get a copy. - KB3VWG

1 0

Amprnet vpn
by Shawn Bush 17 Feb '17

17 Feb '17

Thanks for the detailed reasponce. I have work with the 44ripd daemon and I was recieveing the route information but that would be it. In thr startampr script that is show, it tries to setup mode ipip and that is just something that I couldn't figure out how to get a ubuntu vm to run with. In the ubuntu host, the ipip works just fine and there is a module for it. But the module isn't in the VM and I dont see why. But I was told ipensec is what I'm supposed to be using? I have no idea how to route diffrent protocols....

2 1

Re: [44net] AMPR VPN
by lleachii＠aol.com 16 Feb '17

16 Feb '17

Sean, If you are using the AMPR VPN listed on the services wiki site, it uses the allocation given to its operator. You MUST setup an IPENCAP tunnel, or have your subnet routed over the global Internet via BGP. You might be able to have your allocation directed to the VPN operator (callsign - OH7LZB) and then arrange for him to route your IPs to the tunnel connection you have established between him. Please be advised, out of all the options, this one is not regularly supported. In addition, your latency would be extremely poor, since you appear to be in the United States and the VPN endpoint is in Finland. Lastly, from what I observed, the AMPR VPN appears to be a Layer 3 VPN (not Layer 2). This means that more detailed configuration (on part of the operator) may be required to route multiple IPs to your VPN instance - my understanding is that the VPN is maintained on a volunteer basis. What issue(s) are you having getting "[IPENCAP] over to the VM"? I ran my AMPR router as an Ubuntu VM for many years before migrating it to an actual hardware border router running OpenWRT; perhaps I can assist. 73, Lynwood KB3VWG

1 0

AMPR VPN
by Shawn Bush 15 Feb '17

15 Feb '17

I recently setup a AMPR NET VPN with openvpn in a OpenVZ container due to the fact I couldn't figure out how to get IPIP over to the VM. My question is this, I have a weird ip a 44.x.x.x number and I want to be able to use my given IP of 44.102.204.32, can I route my IP over the given one from the VPN? I'm using Ubuntu in the container and the routing for the VPN is working just fine. I want to setup linBPQ32 with this IP and start routing this way if I can. I'm pretty good with Linux, but not so much with routing. I setup a ampr interface and gave it my 44.102.204.32 IP, but from their I am stuck. 73's KD8NCV Shawn Bush

1 0

What ports needed to open for IPIP ?
by R P 15 Feb '17

15 Feb '17

Hi there We got permission to use our local university network for ham radio We plan to connect our DMR repeater to this network (some ports needed to be opened to allow the repeater to connect to the server) In adddiotion i want to place a AmprNET IPIP gateway there The University protected by firewall no outgoing and no incomming packets free flow.. What should I tell the IT person to open in order to allow gateway to run ? Does Firewall have IPIP protocole definition ? if not ... what should they open ? Outbond and inbond and from /to UCSD 44 Net Router ? Please Advice Thanks Forward Regards Ronen - 4Z4ZQ http://www.ronen.org Ronen Pinchooks (4Z4ZQ) WebSite<http://www.ronen.org/> www.ronen.org ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.com

3 3

Re: [44net] 192.168.0.2 gateway
by Rob Janssen 06 Feb '17

06 Feb '17

> 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

2 1

192.168.0.2 gateway
by Brian Kantor 06 Feb '17

06 Feb '17

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

6 6

Re: [44net] was Verifying the identities of IP coordinators
by Steve L 02 Feb '17

02 Feb '17

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.

7 7

PACCOMM TNC-320 Smoke
by vk1kw 31 Jan '17

31 Jan '17

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

4 5

BGP announced gateways and Mikrotik RIPv2 AMPR Gateway Setup Script 3.0
by Marius Petrescu 24 Jan '17

24 Jan '17

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

4 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net