44net

44net@mailman.ampr.org

3194 discussions

Fwd: Re: AX25 and related software's future in Debian
by David Ranch 04 May '12

04 May '12

Hello Everyone, There is a thread going on in the linux-hams@vger list where the Debian folks are thinking about renaming the long standing AX.25 "node" program in favor of the new Node.JS program as well as thoughts of deeper changes to the AX.25 packages. http://www.spinics.net/lists/linux-hams/ Though Debian is a smaller distribution, it's influence is far reaching to many Debian-related distros (Ubuntu, Mint, etc.) The current HAM packages maintainer is seeking input and what better list to get potential Linux feedback than the AMPR list! I encourage you to join the conversation and be heard! --David -------- Original Message -------- Subject: Re: AX25 and related software's future in Debian Date: Fri, 04 May 2012 11:14:24 -0400 From: Patrick Ouellette <pat(a)flying-gecko.net> To: Dan Smith <dsmith(a)danplanet.com> CC: linux-hams(a)vger.kernel.org, debian-hams(a)lists.debian.org, ralf(a)linux-mips.org, ax25(a)x-berg.in-berlin.de (I added Ralf DL5RB and Thomas DL9SAU to the Cc: line. They are the upstream maintainers of ax25 and I am not sure if they have seen the thread/discussions) On Fri, May 04, 2012 at 07:06:33AM -0700, Dan Smith wrote: > > > So, what inspiration can you give me to keep me from packing up the tent? > > Some of us continue to develop and deploy new systems based on this > stuff. Linux provides the most modern way to integrate AX.25 with other > IP networks (IMHO) and Debian provides a good platform on which to > build. Yes, you and I can install our own stacks, but if it goes away > from the base distro, it will be harder to encourage other folks to do > the same. > Dan, Playing Devil's advocate - the argument has been put forth in the "other discussion" that according to popcon (the Debian popularity contest), node has 81 installs, and 17 reporting as "active" while the nodejs package has 720 installs with 163 reporting as "active." So their conclusion is the node package is only used by a small community. Looking at the ax25 packages: libax25 - 234 installs/ 49 active ax25-tools - 74/19 ax25-xtools - 45/6 ax25-apps - 74/17 other ham packages depending on libax25: xastir - 89/16 aprsd - 33/13 ax25mail-utils - 22/4 fbb -16/3 linamc - 13/0 and a couple of other ham packages: hamlib - 349/119 qsstv - 80/8 gmfsk - 64/10 fldigi - 113/24 xlog - 72/12 gpredict - 650/90 for comparison, the bash shell - 121423/110245 judging by these numbers (and let me make it CLEAR I do not put much stock in them personally since the package does not have to be installed, the machine has to have an internet connection, and the file system has to record atime - so low power systems or ssd drive systems with the mount option noatime don't count) hamlib *might* currently be *safe* in terms of keeping it's name, and clearly is used by others. The other issue, the one I was thinking of was the active user counts. With the exception of hamlib and gpredict they are all low double digit or even single digit numbers. Even if I believe there are many more users of the software, I have no way to prove it. I know there are many Debian and Debian based systems running ax25. Unfortunately "the squeaky wheel gets the grease" and the ax25 users haven't been squeaking. Flawed as it is, the "other side" will continue to use the only tool they have - popcon - to justify their actions in disregarding the place of long term packages in the distribution in favor of the next new / hot thing. I would like to run my tried and true systems as they are, and not have to reinvent the wheel and debug scripts every few years when this issue comes up again. The same thing happened with listen in Debian, so now it is axlisten while the music player now has the executable named listen. Everyone agreed then that "listen" was a generic name and should not really be used, and yet it is. You claim the existence of the packages in Debian encourages others to try ax25, if this is so where are these people? Pat -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message tomajordomo(a)vger.kernel.org More majordomo info athttp://vger.kernel.org/majordomo-info.html

1 0

Introducing YaCy Searchengine to HAMNET
by Michael Przybilla 04 May '12

04 May '12

Hi Folks I'd like to introduce a YaCy System as a distributed search engine for the HAMNET The important information on how to use it can be found here on our Webserver at DB0FHW: http://www.afu-ag.de/joomla/index.php?option=com_content&view=article&id=83… If you let Google translate the page, unfortunatelly, you do not get a very good translation... http://translate.google.de/translate?sl=de&tl=en&js=n&prev=_t&hl=de&ie=UTF-… ... So I'll explain it in a bit more detail. YaCy is a free dezentralized search engine that anyone can use to build a search portal for their intranet General information can be found here: http://yacy.net/en/ ... So lets consider HAMNET as a kind of intranet. We defined a root.unit for the system at DB0FHW, which has a quite good connection to the german HAMNET, an anybody can now connect a peer to this root.unit This unit is shared to all peers, so the network will stay alive, even if DB0FHW goes down. Peers temporarely connect each other like a full mesh, so a peer only needs to know one other peer to find its way back into the network. How do you connect peers now: 1. Download and install YaCy http://yacy.net/en/index.html 2. Do not start the YaCy Service, yet. 3. Edit the line "network.unit.definition" in your file "defaults/yacy.init". It should point to this URL now: http://yacy.db0fhw.ampr.org:8090/yacy.hamnet.unit 4. Start the YaCy Service Philosophy: There sould be (minimum) one YaCy peer in each AS of the HAMNET, crawling the Servers INSIDE ist own AS! How often you want to crawl is your free choice. Just depending on the changes of the servers content. It it holds "hot news", you may host you yacy peer quite close to it an crawl every hour. If content changes weekly, crawl weekly... (if you have a huge AS, you may have more peers and define which of them is crawling which server) So... Sounds not that hard at the end ;-) Give it a try 73 Micha, DD2MIC

1 0

WI Domain cleanup
by kb9mwr＠gmail.com 11 Apr '12

11 Apr '12

Hello, Thought I'd introduce myself. I have taken over for as the regional IP coordinator for Wisconsin and the Upper Peninsula (44.092/16). I wrote a script to help identify expired callsigns, and have since removed those entries for my area. This script my be handy to other coordinators: http://pastebin.com/d0HFmcG5 I made all attempts to not delete any active domains. If anyone is experiencing a problem please contact me. Steve Lampereur, KB9MWR

3 4

Re: [44net] WI Domain cleanup
by kb9mwr＠gmail.com 10 Apr '12

10 Apr '12

Rob, It isn't meant as an automated tool. It was to aide me in lookup of calls. It outputs a list of invalid calls, which I manually reviewed. Here in the US, when you lookup a call that has been changed, the databases reference that. ex: http://callook.info/n9nof What you describe sounds like a headache to keep track of.

2 1

Re: [44net] Slides from Presentation
by Kenny Richards 06 Apr '12

06 Apr '12

We shot video of the presentations last week, when we get them processed and posted, I'll make sure the link gets sent out to the group. 73, Kenny, KU7M > Message: 1 > Date: Thu, 5 Apr 2012 11:23:43 -0700 > From: "John D. Hays" <john(a)hays.org> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: [44net] Slides from Presentation > Message-ID: > <CAN77r3xzhdtYrJLZYj3LYM0H3Recxii3-3AgofVkyyiKPbWOGQ(a)mail.gmail.com > > > Content-Type: text/plain; charset="utf-8" > > http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf > > ------------------------------ > John D. Hays > K7VE > PO Box 1223, Edmonds, WA 98020-1223 > <http://k7ve.org/blog> <http://twitter.com/#!/john_hays> > <http://www.facebook.com/john.d.hays> >

1 0

Slides from Presentation
by John D. Hays 05 Apr '12

05 Apr '12

http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf ------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays> <http://www.facebook.com/john.d.hays>

3 2

WWConvers Australia carns ???
by Janusz Przybylski SP1LOP 04 Apr '12

04 Apr '12

Hi Sam VK4FQ I ask look on side: http://www.wwconvers.ampr.org and write them for cairns all data not to be anonymous -- 73 de Janusz / SP1LOP ===== Janusz J. Przybylski, SP1LOP ========== Poland AmprNet Co-ordinator [44.165.0.0/16] =============================================

1 0

Re: [44net] directly routed subnets
by lleachii＠aol.com 03 Apr '12

03 Apr '12

All, Many have posted good responses on what would be needed to continue this project. I don't want to repeat any good suggestions (which I am also re-reading); but wanted to add a few; as I originally requested a subnet for the purpose of peering with Amateur Digital Radio Communications, or up to consideration of a Layer 1 connections to PoPs (I am working on such arraignments for our area using multi-homed non-commercial means). I have polished up on my BGP routing concepts and found these things: - in the MDC section, we would be seeking local peers via other non-commercial backbones - Doing BGP, the assumption we were to arrange at least layer 1 connectivity (via wireless and/or terrestrial [our area is fiber or greater to peer] which we're working on), at least back to Brian, this will require an AS Number - the concern in my area, want to pursue non-commercial means of announcement, redundancy to the non-commercial/commercial backbone, etc, in case the commercial network went down - Internet2.edu is being built out from stimulus funds, it is primarily non-commercial - just a thought, and a path we're looking into - I am willing to assist in this endeavor, and would like to sit-in on a conference call, if convened - There are other networks I'm sure are willing to carry a VLANs over their fiber - BGP to a PoP for most who wishes to peer with us would require us to really lobby our CFR Title 47 §97.1(a), that we have other Peers willing to provide Layer 1 Transport (working on this) - I see no need for us to work seperately, and wanted to mention this Anyone interested in being homed with another Autonomous System, please consider working with together on a National Amateur Wireless Society, if we receive International Interest, we may have to see other regional interest. Also, would a regional authority be willing to donate us an AS number (made requests)? ~73, Lynwood KB3VWG

2 2

Re: [44net] Mini ATX Intel BOXD525MW Intel Atom D525
by lleachii＠aol.com 21 Mar '12

21 Mar '12

I'm also using a standard Ubuntu Linux Server 11.10 using rip44d and a Web Application providing a GUI named Webmin. This is a quick overview on setup. This setup can be done with telent and SSH; for simplicity of those who know the command line syntax, I will omit the necessaries. 1.) - with IP forwarding (Routing) enabled in /etc/sysctl.conf # Uncomment the next line to enable packet forwarding for IPv4 net.ipv4.ip_forward=1 2.) - I installed webmin (a Web GUI application for servers) package to better enable on the fly IPtables Firewall configurations, NAT, masquerade, etc. (these configurations allowed me to have this server as router for my 44.60.44/24 subnet over AMPR, while having the ability to also have a private 192.168/24 subnet that uses my standard non-tunneled gateway IP address from my ISP. PE1CHL recommended table-based policy routing; it configures any 44/8 address to use a routing tabled named "44," all other traffic is routed on main. If you setup this router to use NAT or Masquerade for a private network using your ISP's gateway, there will also be entries in the "nat" table. An edit to the rip44d script is necessary to place the 44/8 routes into a routing table named "table 44." 3.) - eth0 was configured at setup as the device connected to the Gateway address. 4.) - In this example, eth1 is the Ethernet interface that will be used as you LAN side providing your 44 Addresses (in this example 44.128.0.0/24) of the router connection (if you do not have access to another NIC, you may also want to set this up virtually to the address on your LAN if this is not the routing device for your physical network). Interface tunl0 is the default Linux IPIP encapsulation tunnel. The example/testing subnet 44.128.0.0/24 will be the subnet assigned to the gateway on tunl0 and eth1 used here. 5.) - with the help of Brian and PE1CHL, I then created a script named /usr/local/sbin/startampr to run on boot (it can be setup to run at boot in the webmin GUI under "Bootup and Shutdown" ### Enables AMPR IPIP Tunnel Interface modprobe ipip ip addr add 44.128.0.2/24 dev tunl0 # gives tunnel its own TTL enabling traceroute over tunnel ip tunnel change ttl 64 mode ipip tunl0 ip link set dev tunl0 up ### Creates AMPR Default Routes on main Route Table #route to 44.128.0.0/24 on main route table ip rule add to 44.128.0.0/24 table main priority 1 ### Specifies Routes to and from 44/8 are entered on Route Table 44 ip rule add from 44.0.0.0/8 table 44 priority 44 ip rule add to 44.0.0.0/8 table 44 priority 45 ### Creates Default Route to the AMPRGW and the ### Internet At-large, on the 44 Router ## Per PE1CHL: 'This is "required" to get routing of the net-44 traffic correct ## and have a default route for the tunneled traffic different from the default ## route of the system. It may be possible to get it working without this, ## but policy based routing is so much easier' # AMPRGW connects via eth0 ip route add 169.228.66.251 dev eth0 table 44 # Connection to 0/0 by 44/8 Hosts on AMPRGW, commenting disables Internet Access for your 44 subnet ip route add default dev tunl0 via 169.228.66.251 onlink table 44 ### this can be omitted if your device will not provide separate local traffic - KB3VWG - This adds a route to the local subnet on the 44 route table ip route add 192.168.0.0/24 dev eth0 table 44 ### Begins the rip44d Router ./usr/local/sbin/rip44d_table44 -a <my public gateway IP> -p <the password> < /dev/null & 6.) Table rip44d_table44 is a script editing the rip44d file to place the AMPR routing table into "Table 44": Line 201 - $cmd = "LANG=C $routebin route add $rkey via $nexthop dev $tunnel_if window $tcp_window onlink"; + $cmd = "LANG=C $routebin route add $rkey via $nexthop dev $tunnel_if window $tcp_window onlink table 44"; 7.) The routers 'main' Firewall Accept If state of connection is ESTABLISHED Accept If state of connection is RELATED * Accept If protocol is ICMP and ICMP type is echo-request * Accept If protocol is UDP and destination port is 33434:33534 + Accept If protocol is TCP and destination port is 10000 + Accept If protocol is UDP and source is 44.0.0.1 and input interface is tunl0 and source and destination ports are 520 + Accept If protocol is TCP and destination destination port is 22 (if you have other services on your Router machine, you would accept their IP's, source, destinations, etc. here) + - enables: webmin, rip44d and SSH respectively, you may further restrict this access to SSH or Webmin configuration by specifying allowed hosts, subnets, etc. 8.) IP Forwarding [the Router's] Firewall Accept If state of connection is ESTABLISHED Accept If state of connection is RELATED * Accept If protocol is ICMP and ICMP type is echo-request * Accept If protocol is UDP and destination port is 33434:33534 Accept If source is 44.128.0.0/24 Accept If source is 192.168.0.0/24 (if you have services on devices inside your subnet, you would accept their destination IP's ports, source, destination ports, etc.) 9.) Network Address Translation Firewall (only needed if routing traffic from a private network [eg 192.168.0.0/24] not carrying 44 Traffic) Accept If source is 192.168.0.0/24 and destination is 44.128.0.0/24 Masquerade If source is 192.168.0.0/24 and destination is 0.0.0.0/0 Accept If source is 44.128.0.0/24 Accept If destination is 44.128.0.0/24 10.) as you create AX.25 interfaces, etc, ensure you enable those protocols, etc in the firewalls. NOTE: Accepting echo-request and protocol is UDP ports 33434-33534 enable Unix and windows based ping and traceroutes from the Internet, you can also place further restrictions on those rules. 11.) Typing the command # ip route list table 44 default via 169.228.66.251 dev tunl0 onlink <between here should be many lines of 44.x.x.x direct IPIP Encapsulated routes that are populated by rip44d from 44.0.0.1 over the tunnel (e.g. '44.x.x.x/x via x.x.x.x dev tunl0 onlink window 840')> 169.228.66.251 dev eth0 scope link 192.168.0.0/24 dev eth0 scope link ~73, KB3VWG

2 1

Re: [44net] directly routed subnets
by lleachii＠aol.com 19 Mar '12

19 Mar '12

All, I actually had a thought on this before I read the current line of discussion. Alot has been highlighted on the nature of a 501(c)3 and what it can and cannot do (feel free to read up on the IRS.gov publications). A 501(c)7 is also a route we may wish to take (depending on California Law and if the filing for determination process had not already proceeded). I also noted that keeping it for Amateur use by Hams is a very good idea. Also recall that we need to keep the network flexible, as testing and development of new protocols and types of equipment, etc. is also something that may become of interest in the future. Also, if you are going to announce space, I am capable of having it housed; so agreements regarding equipment, etc. would be on an Intergovernmental network in my area that RACES and local Emergency Radio Foundation will petition for a seat on, we don't happen to have any carrier-grade network equipment in our shacks on the East Coast (lol).. HSMM-MESH seems like something we want to experiment on right now. In addition, we peer with non-commercial networks; NetworkMaryland is the ISP that we wish to approach for holding an announcement. And it will be Internally BGPed to my County. I'd like to talk with my State Coordinator about this. I know that we are a network neighbour to the Internet2.edu backbone and other carries as well. ~73, Lynwood KB3VWG 44.60.44/24

15 28

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net