44net

44net@mailman.ampr.org

2 participants
3201 discussions

Wiki Updates
by Neil Johnson 07 Apr '14

07 Apr '14

All, I finished by volunteer stint at a youth robotics competition, so I have been poking around the Wiki making some changes. Mainly I have been adding some small pieces of content to eliminate the Wiki links that go to empty pages, but I have also rearranged some of the content on the main page. If you run across any issues, please let me know. I hope that is okay with everyone. -Neil -- Neil Johnson, N0SFH http://erudicon.com

1 0

Pi bug for ipencap?
by Brian Rogers 07 Apr '14

07 Apr '14

Greetings; I've noticed recently after doing a package update on the iproute packages I can no longer configure my tunnel interface tunl0. Mainly I'm trying to reset the ttl to 64 for traceroute to properly work. Everything I've searched comes up empty. Here's what I see: root@gw:/usr/local/bin# iptunnel show tunl0: ip/ip remote any local any ttl inherit nopmtudisc root@gw:/usr/local/bin# ifconfig tunl0 tunl0 Link encap:IPIP Tunnel HWaddr inet addr:44.88.0.1 Mask:255.255.255.255 UP RUNNING NOARP MULTICAST MTU:0 Metric:1 ttl is stuck on inherit and MTU autoconfigs to 0. This I know is set by nopmtudisc however if I try to adjust things: root@gw:/usr/local/bin# ip tunnel change tunl0 ttl 64 ttl != 0 and noptmudisc are incompatible root@gw:/usr/local/bin# ip tunnel change pmtudisc mode ipip add tunnel tunl0 failed: No such file or directory Why would it try to ADD? the command is CHANGE. Has anyone else suffered this before and if so what was the fix? 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.

4 6

Re: [44net] 44Net Digest, Vol 3, Issue 67
by Steve Wright 06 Apr '14

06 Apr '14

> The key here is access to "Amateur Radio Frequencies", e.g. getting on the > air / RF. Well, you cannot possibly open the door to the Internet, then close it again, or have half of it open and the other half closed, then change it again tomorrow, or change it when someone gets upset - all you are going to have is a 44net dominated by strong negative feelings and a whole lot of arguing - probably exactly what you have already. The decision has been made already to continue with an amateur PUBLIC 44net. If Members want to firewall off all incoming !44/8, then that is their choice, and they should do that, and no one should comment on their choice, and should certainly not be disparaging about it. Same rule applies to all others doing as they choose as well. Let's fix this wiki and get the documentation sorted. Steve ZL1BHD

1 0

Re: [44net] 44Net Digest, Vol 3, Issue 66
by Bryan Fields 04 Apr '14

04 Apr '14

On 4/4/14, 3:13 PM, Steve Wright wrote: > This is going to go nowhere. Go play with your netrom nodes and have fun > pinging each other at 1200baud, and keep being hostile to wireless ISPs who > just offered the use of tens of thousands of $$ worth of outdoor 100mbit > gear for no charge. TBH, 99% of WISP's run gear in the 100's of dollars range, it's not professional or even ham radio grade IMO. I've seen some real poor installations and even seen them kicked off sites. We should strive to be better than the average WISP. I'd say there is not implied guarantee that some one using a 44/8 IP is going to be a licensed ham radio operator. You as a control operator of the station are ultimately responsible for the transmissions. I don't get to concerned about it personally. I cannot police 100% of the traffic transiting my nodes, and I don't think anyone can. 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

1 0

Re: [44net] 44Net Digest, Vol 3, Issue 66
by Steve Wright 04 Apr '14

04 Apr '14

> Hmm, even here you may notice several people with quite networking > experience wanted to get involved but when they asked for help because > it is not that easy to understand how 44net works as there is tremendous > lack of information, they got pretty rude replies, like, they should > write documentation themselves. > > It's like there is some kind of elitism. If you are not involved in > development since mid 70's, and if you actually need to read > documentation, then you are not in a game. Yup, exactly. > I'd like to grant access to Amateur Radio frequencies if the source ip > is within 44.0.0.0/8. I assume that only radio amateurs are "behind" > net44 addresses. You see, but that is completely useless, because you just firewalled the entire internet. This is going to go nowhere. Go play with your netrom nodes and have fun pinging each other at 1200baud, and keep being hostile to wireless ISPs who just offered the use of tens of thousands of $$ worth of outdoor 100mbit gear for no charge. Think about it. S

2 1

Re: [44net] routable or private?
by Steve Wright 04 Apr '14

04 Apr '14

I guess my point is - there are those who sit around and cry and beat their forehead with their fist over authentication, the rules, third party traffic etc etc, and there are those who just go ahead, build it, and use it. The difficulty for me is, I returned to 44net hoping for the latter, or at the very least some tutorials on the wiki where it might be done, meet some people that are doing it, but the reality is more that the 44net list is dominated by crybabies who would far rather point the finger, overtly discuss, and get irate at the rulebreakers than actually build anything positive. My suggestion, if you were interested, which you're not, is to sit back a little and let the people who ARE ACTUALLY BUILDING SOMETHING, along with those who DO ACTUALLY INTEND to build something to get on with the task and keep your distracting discussion to yourself. Or maybe this is just never going to happen on this list, and we are forever doomed to listen to the repeated diatribe of how to overtly authenticate and heavily police and analyse every vagrant network ping like its' some heinous DDOS attack. If so, why not start a new list yourself and name it appropriately? Hrm?? :) Are we going put together a wiki on how to build a routable internet-connected 44net or not? What will it be? If we're going to shout, take offence, throw toys, and do nothing then I don't care for it. Make a decision. Steve

3 2

Re: [44net] routable or private?
by kb9mwr＠gmail.com 04 Apr '14

04 Apr '14

> Are we going put together a wiki on how to build a routable > internet-connected 44net or not? Google "setup an AMPRnet Gateway" the info is out there, one of the entries comes back from the wiki, It's actually a very simple process.

1 0

Re: [44net] 44net and consider... 100.64.0.0/10
by lleachii＠aol.com 03 Apr '14

03 Apr '14

* Here in the Washington DC area, we are ready and willing to make use of address space over RF links and make use of 44 address space. * I personally use 44 space for experimentation and development of new protocols, which in most cases, might not work over the Public Internet. I also am working to implement services and mesh access to/from agencies the our ARES/RACES serves (e.g. standing links in situation rooms of our local hospitals, public health facilities, shelter go-kits, etc.). * I'm not sure you reviewed RFC-6598 before suggesting use of 100.64.0.0/10 address space; but there are many technical restrictions that must be considered if using this address space. - DNS and Reverse DNS cannot be used - The addresses should not be forwarded outside of the "carrier's network," which could happen easily, even if by mistake - DNS filtering of addresses is recommended as to prevent leakage of 100.64.0.0/10 queries into the public Internet - A gateway's connectivity to the Public Internet may be lost if the carrier providing your "public" IP address switches to Carrier-Grade NATing (CGN) - Newer devices may be RFC6598 aware and not behave correctly using CGN IP space (e.g. not provide DNS responses, not routing or forwarding packets, etc.) If you need other private address space consider... 100.64.0.0/10 as defined in RFC-6598. 73, Lynwood KB3VWG

1 0

past and the future
by kb9mwr＠gmail.com 03 Apr '14

03 Apr '14

I can echo a lot of what Robbie wrote. My dad was in broadcast radio when I was younger. I read an article by Larry Kollar, KC4WZK on the Amateur Packet Radio Network that was floating around on dial-up BBS's and really caught my attention. That kind of sealed the deal that I needed to get into the hobby. When the locals gave me a copy of NOS, that was great. Before you know it I had two NOS boxes networked using NE2000 drivers. Moved from 1200 to 9600, and drooled when reading the VE3JF higher speed pages. We even did webpages on 9600 baud RF in the mid 90's when we all gravitated to Linux. Lots of learning and fun. Moving forward if you know anyone in the hobby with coding skills there are plenty of things that can be done. Hopefully in the future we can attract a few more of these types when they see the relevance ham radio can offer with higher speed networks and that sort. I am sure Chris could use a hand. How about a openwrt package for hams? Be that out of part 15 frequency control, or something like rip44d http://wiki.openwrt.org/doc/devel/packages Then there is always application ideas on 44net. I am impressed with what is out there already. On the RF side the broadband hamnet firmware developers could probably always use a hand too. 73 Steve, KB9MWR

3 2

Introducing myself
by charles＠thefnf.org 03 Apr '14

03 Apr '14

Hello, Charles Wyble here. I'm new to the list and thought I would introduce myself. Glad to be here. I'm the cofounder and CTO of the Free Network Foundation (http://www.thefnf.org). I'm not currently licensed as a HAM, however my co founder is. I stumbled across 44net via some folks up in Seattle doing a HAM WAN net. My background is in large scale systems (10000+ servers), storage, security, virtualization and basic data center networking. I'm now getting into WAN networking and the fact that an entire /8 is available to HAMs has convinced me to get my license very soon. For anyone who wants to experiment with BGP/WAN networking etc, please do let me know. (I've seen some folks on list express that, and I'll be reaching out). I know my cofounder will be requesting some address space very soon to experiment with. This is a great opportunity to get started on the real internet, because as mentioned IPv4 space is almost impossible to get these days. I look forward to being an active participant in the list. As far as I know, this is the only address space that's publicly administered/discussed etc. That alone is a huge draw for me. Everyone else that has space keeps governance closed.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net