44net July 2014

44net@mailman.ampr.org

29 participants
21 discussions

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

26 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

Re: [44net] (no subject)
by kb9mwr＠gmail.com 12 Jul '14

12 Jul '14

On a PC not connected to the amprnet, when I point a browser to n1uro.ampr.org I get Brians' website with the java warning. On that same PC not connected to the amprnet: http://44.135.85.151/ Nothing http://44.135.85.30/ Nothing On a PC connected to the amprnet http://n1uro.ampr.org Nothing http://44.135.85.30/ - VE3MCH TCP/IP AMATEUR RADIO PACKET GATEWAY http://44.135.85.151/ - VE3MCH TCP/IP AMATEUR RADIO PACKET GATEWAY >From 44.92.21.50 Gateway: 75.87.213.229 --- Quote--- Not that it helps but I get a lovely web page show up when I point my browser at n1uro.ampr.org. Brian's javascript is causing an "Java out of date" error on my machine so something is working.

4 4

Re: [44net] [HamWAN PSDR] Fwd: 44net and internal BGP tests
by Tom Hayward 12 Jul '14

12 Jul '14

On Thu, Jul 10, 2014 at 10:21 AM, K7VE - John <k7ve(a)k7ve.org> wrote: > These are the applications we need to bring to 44-Net We're [HamWAN] doing pretty good so far! Hostnames below... > On Thu, Jul 10, 2014 at 4:56 AM, <lx1duc(a)laru.lu> wrote: >> - 2 DMR repeaters >> - several D-Star HotSpots None yet. >> - DNS resolvers open to 44net (Anycasted), secondary DNS Service available for fellow YLs and OMs HamWAN's recursive DNS is at 44.24.244.1 and 44.24.245.1, anycasted of course. This will work within 44.24.240.0/20 for resolving any domain. Authoritative DNS is a.ns.hamwan.net (44.24.244.2) b.ns.hamwan.net (44.24.245.2) >> - NTP servers (Anycasted) NTP.hamwan.net (44.24.244.4) NTP.hamwan.net (44.24.245.4) Also anycasted. At least one of the members in this anycast pool is GPS-synced statum-1. >> - VoIP (SIP) voip.k7nvh.hamwan.net (44.24.255.5) Ask Nigel for an extension if you want to register your SIP phone. We have three local numbers for dialing in and out, but I believe they lack long distance service and are limited to Seattle, Bellevue, and Olympia (don't quote me on that). We do conference calls semi-regularly. >> - VPN >> - (planned) APRS Server northwest.aprs2.net (on HamWAN's Seattle-SRV1) >> - (planned) connect existing APRS I-GATEs baldi-aprs.kd7lxl.hamwan.net (44.24.240.203) is a dual-channel igate (144.39 @ 1200 baud and 144.35 @ 9600 baud) connected to northwest.aprs2.net >> - (planned) Hosting of HAM webs >> - (planned) Hosting of HAM email services We have postfix configured so that outgoing mail works, but no one has bothered with incoming. Tom KD7LXL

9 10

(no subject)
by kb9mwr＠gmail.com 11 Jul '14

11 Jul '14

I can't reach n1uro.ampr.org either. I don't have any problems with 44.135.85.151 or 44.135.85.30 >From 44.92.21.X If you really want to know what I found reachable on the amprnet: http://www.qsl.net/k/kb9mwr//wapr/tcpip/amrprnet-nmap-2014.txt

3 2

44net and internal BGP tests
by lx1duc＠laru.lu 11 Jul '14

11 Jul '14

Good afternoon, just to let you know, we are testing a new BGP setup between our 44net routers. (This has *nothing* to do with a BGP connection to the internet!!) As the 1023 16-bit ASN numbers are in use mostly in DL and surrounding countries, we were looking for another larger ASN space. The logical alternative is the 32-bit ASN space. The ASNs 42XXXXXXXX are reserved for private use by IANA (except the last ASN!). In order to avoid potential collisions we intend to use the ASNs 42270XXXXX in LX. 270 is the MNC (E.212) for LX (with some inspiration from DMR). We will soon publish the exact ranges in use and I will publish the URL here asap. If anybody of you is already using ASNs from the ranges mentioned above, please let me know. Nothing is written in stone, so we can still rearrange our setup HI :-). If someone of you is interested to setup a BGP session on the existing IPIP tunnel or on a dedicated IPIP, GRE, ... tunnel, please also get in touch with me. We are currently running the following services in our 44net: - 2 DMR repeaters - several D-Star HotSpots - DNS resolvers open to 44net (Anycasted), secondary DNS Service available for fellow YLs and OMs - NTP servers (Anycasted) - VoIP (SIP) and Jabber (XMPP) server - VPN - (planned) APRS Server - (planned) connect existing APRS I-GATEs - (planned) Hosting of HAM webs - (planned) Hosting of HAM email services 73 de Marc, LX1DUC

3 4

IPIP with pfSense Firewalls
by Rod Ekholm 10 Jul '14

10 Jul '14

I have set up a new firewall for my network, and am wanting to use it to also perform either the encap.txt updates, or even a few isolated IPIP tunnels to get my connections back to the 44/8 network. Is anyone else running pfSense to do this? I would be interested in some help in making this work. Screenshots, a write up.. Anything!!! I'll explore it more today for a bit, but I'm still baffled by some of the way pfSense does things and still trying to figure it out. Thanks for any help you can offer! -- Rod Ekholm kc7aad(a)gmail.com

3 3

rip44d seg faults
by Jason R Begley 10 Jul '14

10 Jul '14

I am having an issue running rip44d on Arch after a recent update (perl (5.18.2-2 -> 5.20.0-5) I suspect). Please see the below BT and let me know if you can help. gdb -args perl rip44d GNU gdb (GDB) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from perl...(no debugging symbols found)...done. (gdb) r Starting program: /usr/bin/perl rip44d warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x00007ffff67019ce in boot_IO__Interface () from /usr/lib/perl5/site_perl/auto/IO/Interface/Interface.so (gdb) bt #0 0x00007ffff67019ce in boot_IO__Interface () from /usr/lib/perl5/site_perl/auto/IO/Interface/Interface.so #1 0x00007ffff7aeb93b in Perl_pp_entersub () from /usr/lib/perl5/core_perl/CORE/libperl.so #2 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #3 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #4 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #5 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #6 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #7 0x00007ffff7a6a630 in Perl_utilize () from /usr/lib/perl5/core_perl/CORE/libperl.so #8 0x00007ffff7a9d0b9 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #9 0x00007ffff7b1d942 in S_doeval () from /usr/lib/perl5/core_perl/CORE/libperl.so #10 0x00007ffff7b2a72c in Perl_pp_entereval () from /usr/lib/perl5/core_perl/CORE/libperl.so #11 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #12 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #13 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #14 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #15 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #16 0x00007ffff7a9d781 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #17 0x00007ffff7b1d942 in S_doeval () from /usr/lib/perl5/core_perl/CORE/libperl.so #18 0x00007ffff7b29510 in Perl_pp_require () from /usr/lib/perl5/core_perl/CORE/libperl.so #19 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #20 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #21 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #22 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #23 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #24 0x00007ffff7a6a630 in Perl_utilize () from /usr/lib/perl5/core_perl/CORE/libperl.so #25 0x00007ffff7a9d0b9 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #26 0x00007ffff7a74215 in perl_parse () from /usr/lib/perl5/core_perl/CORE/libperl.so #27 0x0000000000400d9b in main () (gdb)

3 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net July 2014