44net

44net@mailman.ampr.org

3196 discussions

ampr.org hostname resolves to non 44/8 ip - what's up here?
by Eric Fort 02 Aug '14

02 Aug '14

doing some testing here this morning and went to login to af6hf.ampr.org and saw the following: debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21... just curious what's going on here. can we now assign any ip addresses to our delegated domain namespace? I had always thought that foo.ampr.org would be placed in 44/8 ip space. Eric AF6EP

5 9

Co-ordinate ??
by gm4upx＠gb7jd.co.uk 29 Jul '14

29 Jul '14

Hello, Anyone else experiencing this ?? When I click on the [ Co-ordinators ] part I should be directed to [ https://portal.ampr.org/coord_index.php ] but I am re-directed to [ https://portal.ampr.org/index.php ] Regards, Ian..

4 4

Re: [44net] 44Net Digest, Vol 3, Issue 119
by Rob Janssen 28 Jul '14

28 Jul '14

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] VPN or Gatwaying without control of NAT router WAS: 44Net Digest, Vol 3, Issue 118 > From: > Eric Fort <eric.fort(a)gmail.com> > Date: > 07/28/2014 06:16 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > thanks geoff. I did login and look it up, then sent it on. looks > like this subnet will finally be coming online..... even if packets > need to route via romania on their way here! those in the us, really > ought pitch in and find some isp willing to bgp announce for us in > exchange for a moderate fee for hosting a vpn concentrator for the > announced subnets. with the low expected traffic usage it "shouldn't" > be that costly to do. anyone know a friendly us based isp? Please note that there is no relation whatsoever between announcing via BGP and offering an OpenVPN or other VPN access instead of IPIP tunnels. Those are two completely ortogonal subjects. It is possible to setup an OpenVPN or other VPN access on a gateway that is connected to others via IPIP tunnels, that is what I have now. And it is possible to have a BGP announced gateway that does not offer OpenVPN. And it is possible to combine the two. You can setup an OpenVPN access system that operates as a normal IPIP gateway on any of the low-cost virtual servers that you can get everywhere today. No need for ISP cooperation or BGP routing. Just get a Linux virtual server, install a couple of packages, configure them, and there you go. Rob

2 1

Re: [44net] 44Net Digest, Vol 3, Issue 118
by Rob Janssen 28 Jul '14

28 Jul '14

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] 44Net Digest, Vol 3, Issue 117 > From: > Eric Fort <eric.fort(a)gmail.com> > Date: > 07/27/2014 06:49 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > Rob, > > for the specific situation I'm in we ought chat. I do eventually want > to set up my own 44net vpn hub.... but for the moment it would work > just fine to have an ip out of finland or elsewhere. now if someone > wanted to setup a vpn server host for various yet to be routed subnets > that would be even cooler..... but yes, let's chat. a vpn connection > to you would be most welcome. > > Thanks, > > Eric Eric, My VPN server is only configured for Dutch IP adresses, as I have configured it in such a way that it can use existing allocated net-44 addresses, for which I am the coordinator for 44.137.0.0/16, and I am setting up a server for this network to be announced on BGP. That is not finished (waiting for permission from the ISP and then from ARDC), but it already operates as a gateway. On that machine I installed the OpenVPN server. So it only works for existing adresses in the 44.137.0.0/16 network, that are not within a subnet registered at the portal. However, others have taken a different approach, they allocate new addresses from a special subnet. I think the Finnish server does this as well. Best would be if someone nearer to you provides this service, as this yields much better performance. Rob

4 6

Re: [44net] 44Net Digest, Vol 3, Issue 118
by Ernest.Tse＠Pacswitch 28 Jul '14

28 Jul '14

An embedded and charset-unspecified text was scrubbed... Name: not available URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20140728/71d2ac1…>

1 0

Re: [44net] 44Net Digest, Vol 3, Issue 117
by Rob Janssen 27 Jul '14

27 Jul '14

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] getting a debian wheezy host connected to 44net > From: > Eric Fort <eric.fort(a)gmail.com> > Date: > 07/26/2014 06:42 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > ok it seems everyone is missing the point of the question here. see > my threaded comments below: > > On Sat, Jul 26, 2014 at 3:41 AM, Marius Petrescu<marius(a)yo2loj.ro> wrote: >> >(Please trim inclusions from previous messages) >> >_______________________________________________ >> >Eric, >> > >> >Actually you can use any stateful VPN tunnel: OpenVPN, PPtP, L2TP, SSTP etc. >> >OpenVPN is kind of complicated to set up (certifcates and other details). >> > >> >The idea is to initiate the connection from the dynamic IP to a static IP, >> >and reconnect on IP change from the new dynamc IP. >> > >> >I personally favor PPtP or L2TP (optional with MPPE encryption), since this >> >protocol is supported by almost any OS (Windows, Mac, Linux) and is light on >> >the processor. >> > > yes I get that the tunnel type is mostly irrelevant and I'm pretty > agnostic as to it's type as hey I could tunnel over dns, http, or even > icmp if I had to. The question is tunnel to where? If I had a box > somewhere with a static endpoint / static ip address a big part of > this question would not be being asked and yes, I'd use it as a vpn > server - problem solved. at present, I do not have that luxury. > > is there no possible way to connect hosts to amprnet that are behind a > nat firewall router that has a dynamic public ip without the use of a > (my own) vpn server with a static ip placed elsewhere? > > Eric > It depends on where you are and what kind of address you want to have. Here in the Netherlands I have just setup an OpenVPN server that can be used for this for addresses within 44.137.0.0/16. Anyone with such an address can just mail me and I'll send them a certificate and example config file. I plan to enable PPTP, L2TP/IPsec and IPsec as well as demand arises. There is an OpenVPN service in Finland as well, see http://wiki.ampr.org/index.php/AMPRNet_VPN I think they are open for registration from anywhere (not just Finland). Of course best is when you start a server in your own area. Rob

2 1

getting a debian wheezy host connected to 44net
by Eric Fort 27 Jul '14

27 Jul '14

I have a group of hosts that at present must sit behind a home router with a dynamic public IP which I have not access to the settings of that acts as a nat firewall. how can I get these boxen joined to amprnet where they can be accessed by amprnet and the internet at large? vpn anyone? Thanks, Eric

6 12

TAPR DCC 2014?
by Brian Kantor 25 Jul '14

25 Jul '14

The annual TAPR Digital Communications Conference is September 5-7 this year in Austin Texas USA. https://www.tapr.org/dcc.html Are any of you folks planning to attend? - Brian

4 3

Re: [44net] dcc
by f6cnb＠hutin.org 23 Jul '14

23 Jul '14

I'll attend the DCC 73 Remi W5/F6CNB Sent from my android device.

1 0

44.140.0.0/16 via 44.140.0.1 unreachable on mikrotik
by lx1duc＠laru.lu 14 Jul '14

14 Jul '14

Good evening, I have the following routes concerning 44.140.0.1 on my system: [lx1duc(a)LX044-17.ampr.org] > ip route print detail where 44.140.0.1 in dst-address Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 ADb dst-address=0.0.0.0/0 gateway=46.29.182.225 gateway-status=46.29.182.225 reachable via ether10 distance=20 scope=40 target-scope=10 bgp-as-path="60391" bgp-origin=igp received-from=AS60391_v4 2 A S dst-address=44.140.0.0/16 gateway=ampr-44.140.0.1 gateway-status=ampr-44.140.0.1 reachable distance=210 scope=30 target-scope=10 3 Db dst-address=44.140.0.0/16 gateway=46.29.182.225 gateway-status=46.29.182.225 reachable via ether10 distance=250 scope=40 target-scope=10 bgp-as-path="60391,51405,24611,3549,1299,1299,1299,2603,1653,2839, 8973" bgp-atomic-aggregate=yes bgp-origin=igp bgp-communities=3549:2682,3549:31528,51405:352,51405:1100,51405:2003, 51405:10010,51405:10012 received-from=AS60391_v4 (I deleted rule #1 as it is disabled). When I do a traceroute to 44.140.128.7 from a system behind that router, I can see that the packets come in via ethernet and they are forwarded to the IPIP tunnel interface for 44.140.0.1, however the Mikrotik router never sends any IPIP packets out via my upstream ethernet connection. When I add the following route: 4 A S dst-address=44.140.0.1/32 gateway=46.29.182.225 gateway-status=46.29.182.225 reachable via ether10 distance=1 scope=30 target-scope=10 are actually sent out of the ethernet to the upstream. However there is no response from 44.140.0.1 in any case. (There is a possible work around by using different routing tables, but depending on the type of rules, this could still have the same effect.) I'm not very sure how this can be solved, eventually by announcing 44.140.0.0/24 via commercial BGP. Any ideas are welcome. 73 de Marc, LX1DUC

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net