44net

44net@mailman.ampr.org

3179 discussions

Re: [44net] known good routers that pass rip/44-net friendly in uk?

by Rob Janssen

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] known good routers that pass rip/44-net friendly in uk? > From: > ve1jot <ve1jot(a)eastlink.ca> > Date: > 01/08/2014 09:43 AM > > To: > 44net(a)hamradio.ucsd.edu > > > Anyone know of a list of routers that pass ripv2? A ham in EU is trying > to set up ripv2 with our help but ripv2 gateway announcements don't seem to be coming through the router...yes, the pi is in the DMZ, hi hi! He's on virginmedia, any issues with their modems known? You mean the ipip tunneling is working with static routing but you cannot get RIP to work? Or is the situation merely "it does not work" and the diagnosis "there are no RIP announcements"? I set up a Pi some time ago and I had a strange problem with RIP that I finally resolved, and submitted a patch to ampr-ripd that makes it work problemfree. I don't know if the other ripd was similarly modified, for sure it had the same issue. The problem was that although RIP announcements made it all the way to the Pi, they were not properly received on the UDP socket the daemon created. Rob

11 years, 3 months

Re: [44net] known good routers that pass rip/44-net friendly in uk?

by lleachii＠aol.com

- Any iptables-based device (e.g. Linux kernel/OS, DD-WRT, OpenWRT, RaspberyPi) - DLink devices that allow selecting of "Other" protocol, DLink provides Web GUI simulators for most router models **On D-Link 1.) Browse to Network Settings > Advanced > Virtual Server 2.) Add name and IP address of 44GW, or select IP from the list and click the "<<" button 3.) Change Protocol to "Other" and enter "4" in the box under Protocol 4.) Click "Save Settings" **Command for Static IP (tested on DD-WRT and OpenWRT): iptables -t nat -I PREROUTING -p ipencap -d <GW Public IP> -j DNAT --to-destination <GW LAN IP> iptables -t filter -I FORWARD -p ipencap -d <GW LAN IP> -j ACCEPT **Command for Dynamic IP - (WAN is vlan1 in DD-WRT in OpenWRT it is usually eth0.1): iptables -t nat -I PREROUTING -p ipencap -i vlan1 -j DNAT --to-destination <GW LAN IP> iptables -t filter -I FORWARD -p ipencap -d <GW LAN IP> -j ACCEPT 73, Lynwood KB3VWG

11 years, 4 months

Re: [44net] gateways cleanup/deletion (Brian Kantor)

by Gabriel Medinas

Hello Brian and fellow amprnet friends. First, let me introduce myself, I am Gabriel Medinas YV5KXE from Caracas, Venezuela, working in the past time with the last one Venezuela amprnet coordinator YV5CIV that is away of the activity. I work amprnet for about 20 years, in the last years the activity in my country is down with the packet radio mode, but a group of YV-YY want rise it again. I maintain operative the last packet radio gateway (yv5kxe.org) with VHF 145.010 YVNET working together with APRS, in this month Brian Kantor let me the responsability of the Amprnet Local Coordinator of 44.152.x.x Venezuela network, I glad to share this with my friends in amprnet of many years, now in the coordination position. In a first step, I mount a Linux amprnet JNOS gateway with N6ROE help (thanks Kim). The second step is work to find the way to re-start the amprnet here, the idea of a new gateway with static IP or see the posibility to mount a dynaIP tool or other. I think (personal idea) this network may grow if our fellow ham radio may have the possibility to use their ADSL (dynamic IP) home connections to mount their NOS amprnet system, also we are study the ways to start first a static IP gateway to server the others via AXUDP/AXIP connections. Now Brian, with this comercial IP list see any of our old gateway IP (not working now), please you may delete it to clean the gateway list to be a real and accurate network, please to all gateways sysops, delete all 44.152.x.x routes to restart in clean mode. Grettings all for your time and hope work together in more and operative amprnet network! 73 de Gabriel YV5KXE AMPR Net IP Address Coordinator - Venezuela yv5kxe.org yv5kxe.ampr.org www.gmedinas.com Message: 1 Date: Tue, 7 Jan 2014 12:32:50 -0800 From: Brian Kantor <Brian(a)UCSD.Edu> To: 44net(a)hamradio.ucsd.edu Subject: [44net] gateways cleanup/deletion Message-ID: <20140107203249.GA8539(a)UCSD.Edu> Content-Type: text/plain; charset=us-ascii A while back I published a list of unclaimed gateways (those with no known owner/operator). Some small number of those were subsequently claimed and have been associated with their registered owner in the portal. However, there remain some 91 gateways whose owner/operator remains unknown. I intend to delete these gateways from the encap/gateways file around the end of the month. So in effect, this is the last chance for people operating these gateways to get them properly registered before they go away. If you find your gateway on this list, be sure you are personally registered with the portal and SEND ME AN EMAIL to get the gateway associated with your callsign in the portal. Thank you all! - Brian In order by commercial IP address: 8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.224.157.206 50.79.209.150 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.209.144.3 69.69.168.201 69.145.172.163 69.254.106.173 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 80.59.234.233 81.235.253.122 84.92.153.154 90.206.95.108 91.84.215.75 94.72.251.181 94.172.232.113 96.20.43.106 96.35.76.41 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 122.108.78.111 130.208.168.63 141.85.43.57 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 193.22.2.254 194.27.119.2 195.22.112.28 195.66.148.106 195.113.115.135 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 212.159.74.68 212.159.102.156 216.144.222.182 216.253.203.30 220.157.89.84 220.233.86.207 ------------------------------

11 years, 4 months

Hack fix for Pi

by Brian Rogers

Greetings list members; While I still search for a true fix, a hack fix would be to create a tunl1 and route via that interface, however if you take tunl0 down, for some reason rip fails. If anyone has a better solution or a true fix, please relay it. Thanks in advance... -- 73 de Brian Rogers - N1URO email: <n1uro(a)n1uro.ampr.org> Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.

11 years, 4 months

AMPRNet Flow Charts

by Jann Traschewski

Hi! I'm about to put some Flow Charts on the AMPRNet wiki. Can you please review the following files for correction? http://db0fhn.efi.fh-nuernberg.de/files/amprnet Thank you! 73, Jann -- Jann Traschewski, Lenbachstr. 6, D-90489 Nuernberg, Germany Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn

11 years, 4 months

gateways cleanup/deletion

by Brian Kantor

A while back I published a list of unclaimed gateways (those with no known owner/operator). Some small number of those were subsequently claimed and have been associated with their registered owner in the portal. However, there remain some 91 gateways whose owner/operator remains unknown. I intend to delete these gateways from the encap/gateways file around the end of the month. So in effect, this is the last chance for people operating these gateways to get them properly registered before they go away. If you find your gateway on this list, be sure you are personally registered with the portal and SEND ME AN EMAIL to get the gateway associated with your callsign in the portal. Thank you all! - Brian In order by commercial IP address: 8.22.205.37 12.195.50.128 24.55.199.25 24.84.205.232 24.89.203.65 24.137.76.29 24.224.157.206 50.79.209.150 64.22.214.233 64.119.33.202 64.119.42.138 64.255.99.17 65.41.209.137 65.48.61.133 65.70.212.35 66.11.68.11 66.112.51.126 66.114.139.158 67.108.91.190 68.61.222.68 68.209.144.3 69.69.168.201 69.145.172.163 69.254.106.173 71.36.92.66 71.107.40.238 71.107.40.238 71.201.92.148 74.85.194.5 75.21.234.175 76.14.161.185 76.64.80.228 76.247.140.206 76.253.114.92 77.249.108.97 79.116.75.255 80.59.234.233 81.235.253.122 84.92.153.154 90.206.95.108 91.84.215.75 94.72.251.181 94.172.232.113 96.20.43.106 96.35.76.41 98.193.215.29 98.208.81.22 99.88.77.66 99.116.194.13 108.185.66.208 113.212.169.28 122.108.78.111 130.208.168.63 141.85.43.57 146.48.126.26 146.48.126.28 148.223.34.6 150.188.8.195 152.66.0.109 155.207.19.57 158.42.128.200 161.53.16.179 168.96.128.17 173.14.57.181 184.175.46.166 186.125.37.47 189.42.190.50 190.31.163.55 190.139.56.180 193.22.2.254 194.27.119.2 195.22.112.28 195.66.148.106 195.113.115.135 198.108.247.220 200.17.207.2 200.46.129.3 201.252.37.40 202.63.57.97 206.251.38.99 207.111.203.194 207.179.123.166 208.74.106.137 208.94.114.29 208.115.126.75 212.159.74.68 212.159.102.156 216.144.222.182 216.253.203.30 220.157.89.84 220.233.86.207

11 years, 4 months

Re: [44net] gateways cleanup/deletion

by Wm Lewis

At 01:28 PM 1/7/2014, you wrote: > 50.79.209.150 This address is for KE6I, CATHRYN MATAGA. She does have an active node and BBS "BERK" in Berkeley, Calif. I sent her a copy of your first email but had no response. I'll try and contact her again. I suppose if you pull the plug, that will get her attention :) Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) (530) 263-1595 (Home/Office) ______________________________________________ ---------- This message is for the designated recipient only and MAY CONTAIN PRIVILEGED OR CONFIDENTIAL INFORMATION. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this E-mail is prohibited.

11 years, 4 months

Happy New Year

by Brian Kantor

I want to wish each of you a Happy New Year and to extend my thanks to you for all the contributions you folks have made to the advancement of amateur radio tcp/ip networking. And I'd like to extend a very special thanks to those of you who have been generous enough to make a donation to help keep the Amateur Radio Digital Communications non-profit corporation a going concern at http://www.ampr.org/donate.html Best wishes! - Brian

11 years, 4 months

Re: [44net] Pi bug for ipencap?

by lleachii＠aol.com

Brian, I found the following in a Linux manual for the 'ip tunnel' command: nopmtudisc -- disable Path MTU Discovery on this tunnel. It is enabled by default. Note that fixed ttl is incompatible with this option: tunnels with fixed ttl always make pmtu discovery. If you create a tunnel that does not care about MTU state, it's also unconcerend about the 'distance' the packet has traveled, your eth interface would handle both tasks in that instance (being a 'dumb tunnel,' if you will). With nopmtudisc on, your 44Router would properly fragment the packet when transmitting on eth and sets the ttl on the ARPA Internet, as opposed to AMPRnet. If this command worked before you updated your IP utilities, it was probally due to the previous version not being written true to RFC. 73, Lynwood KB3VWG

11 years, 4 months

Re: [44net] Pi bug for ipencap?

by Rob Janssen

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > [44net] Pi bug for ipencap? > From: > Brian Rogers <n1uro(a)n1uro.ampr.org> > Date: > 12/30/2013 12:59 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > Greetings; > > I've noticed recently after doing a package update on the iproute > packages I can no longer configure my tunnel interface tunl0. How did you get that update? is it an update that is currently queued on "apt-get upgrade"? or was it something you installed yourself? (my Pi is still working but I'd like to know what to avoid) Rob

11 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net