44net

44net@mailman.ampr.org

4 participants
3196 discussions

44Net VPN?
by KJ7DMC 29 Jun '19

29 Jun '19

Hello, This is sort of a follow up to my last email, which I ended up figuring out. This link, http://he.fi/amprnet-vpn/amprnet-vpn-win.zip to download the amprnet crt file is invalid. Any idea where I would obtain that file from? Thanks! -Nate

3 2

Old Files
by vk2tv 25 Jun '19

25 Jun '19

I apologise in advance if this message is misplaced, but I've seen some names/callsigns on the list that go back far enough to possibly have what I'm looking for. Some weeks back I performed some hardware decode comparisons for old packet hardware - MFJ1270B and Tiny2 mk2 TNCs, serial port Baycom modem (TCM3105 based), Baycom USCC>4 card with 1x9k6, 1xAMD7911 and 2xTCM3105 modems, a YAM modem, and some relatively new hardware, the TNCX and Byonics TT4) - with Dire Wolf software decoding, with some surprising results, except for the YAM. Try as I might I couldn't get the YAM to rx data at 9k6, but I was able to tx to the Baycom 9k6 modem which decoded packets. That was after I added external, 5V powers supplies because the comport wasn't up to the task (-5V/+2.8V)! The YAM won't tx or rx at 1k2. I know the YAM is old - about 1998 - and there isn't much information beyond what little I already had for the unit, which was capable of two-way communication (over wire) with the Baycom many years ago, so I know it "did" work. The Wayback Machine provided nothing useful. My request is for any information pertaining to the YAM, and in particular, any mcs configuration files for Linux. I have yam96v13, yam17 and yam1k2b5. My fading memory seems to recall documentation pertaining to faults and modifications, so that could also prove useful .. if any still exists. Thank you for your ears (or is that eyes?) Ray vk2tv

1 0

NPR (New Packet Radio) : new firmware with 56kBaud and 120kBaud
by f4hdk 19 Jun '19

19 Jun '19

Hello. I have updated the firmware of my NPR (New Packet Radio) project with 2 expected features, mainly for America: * New modulations (11, 12, 20, 21) for lower datarates, lower bandwidth. Symbol rates: 56kS/s (complies with FCC) and 120kS/s. You now have the choice between 9 modulation parameters, in order to adapt to lots of situations and needs. * Frequency range extended to 420-450MHz instead of previously 430-440MHz I have updated all the documentation accordingly. https://hackaday.io/project/164092-npr-new-packet-radio/ Several people here expected these features. I hope you will enjoy it! 73, Guillaume F4HDK

5 9

Re: [44net] IRR Entries for BGP Filtering
by G1FEF 19 Jun '19

19 Jun '19

> On 19 Jun 2019, at 17:33, チョーチュアン via 44Net <44net(a)mailman.ampr.org> wrote: > > > From: チョーチュアン <quanzhou822(a)gmail.com> > Subject: Re: [44net] IRR Entries for BGP Filtering > Date: 19 June 2019 at 17:33:31 BST > To: AMPRNet working group <44net(a)mailman.ampr.org> > > > IIRC Vultr registers your prefix with the RADb as "Vultr Customer Route" or > something alike. That will make your asn/prefix pair work with most > providers. On the other hand, I met some providers completely ignores the > RADb and/or LoA, and do their own due diligence, I believe there are good > stories behind these practices. Indeed, I have (not so fond) memories of trying to convince some carriers (usually tier 2 / wannabe tier 1’s) that they needed to update their filters so our customers could reach their networks. Those were the days! I guess not much has changed in 20 years. Chris

1 0

IRR Entries for BGP Filtering
by Jonathan Lassoff 19 Jun '19

19 Jun '19

Hello 44Net friends -- I'm operating a BGP-announced subnet of 44/8 for some paging and SDR experiments, and with some new access to other facilities, I'm looking into adding some geographic redundancy for my network, setting up an ASN, and beginning some public peering. However, what I am coming to discover is that Brian's LOA only gets me so far... :) Many networks in Europe are doing proper per-peer prefix filtering, constructed from IRR data in various registries. I would like to get my 44/8 prefix listed in one of these registries with my ASN listed, so that I can get all this automatic filtering working. Generally, most networks seem to be using the RIR-provided IRR registry for this data, which for us in the US and with AMPR would be ARIN. There are also some commercial IRR databases. https://www.radb.net/ seems to be the most-widely mirrored, but it costs ~$500/year to use. As this is just a hobby project for me, it's difficult to justify the costs of a commercial registry. Might it be possible for AMPRNet users to use ARDC's ARIN accounts to list some "inetnum" IRR data for our prefixes? Depending on the outcome, maybe this would be some useful information to list on the FAQ in the Wiki. Thanks, jof

8 9

Re: [44net] NPR (New Packet Radio) : new firmware with 56kBaud and 120kBaud
by Leon Zetekoff 17 Jun '19

17 Jun '19

hi there...sound good but why aren't we using 2.4 or 5g for high bandwidth backhauls? The hardware is cheap enough and works well. 73 Leon wa4zlw Blandon, PA On 6/16/2019 10:40 AM, pete M via 44Net wrote: > To: > AMPRNet working group <44net(a)mailman.ampr.org> > > > A big thank you for that effort. This will surely start a new boom in "packet radio" in north America. I for one will push to implement the fastest links to our audio links back bones that is all in uhf for our emergency net . That way we will work in Voip rather then analog voice opening the way to many more service at the same time . > > Télécharger Outlook pour Android<https://aka.ms/ghei36> --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

7 10

Re: [44net] NPR (New Packet Radio) : new firmware with 56kBaud and 120kBaud
by Mark Phillips 17 Jun '19

17 Jun '19

".... may use any technique whose technical characteristics have been documented publicly ...." This mode is documented publicly along with its source code. I'd say we are good. So now it's just the symbol rate and bandwidth issue to overcome. I like the idea of multiple carriers too. Bond them together on demand perhaps? Mark On Mon, Jun 17, 2019 at 4:54 PM Steve L via 44Net <44net(a)mailman.ampr.org> wrote: > > > > ---------- Forwarded message ---------- > From: Steve L <kb9mwr(a)gmail.com> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Cc: > Bcc: > Date: Mon, 17 Jun 2019 15:54:13 -0500 > Subject: Re: [44net] NPR (New Packet Radio) : new firmware with 56kBaud > and 120kBaud > The rules no longer really specify how you must ID, like pre-1980's. > Basically in this case you ID in the mode > itself, just like D-Star, YSF etc, does. > > If the digital code was unspecified (also allowed) you'd likely have > to default to a CW ID. > > §97.119 Station Identification > > (b) The call sign must be transmitted with an emission authorized for > the transmitting channel in one of the following ways: > > (3) By a RTTY emission using a specified digital code when all or part > of the communications are transmitted by a RTTY or data emission; > > §97.309 RTTY and data emission codes. > > (4) An amateur station transmitting a RTTY or data emission using a > digital code specified in this paragraph may use any technique whose > technical characteristics have been documented publicly, such as > CLOVER, G-TOR, or PacTOR, for the purpose of facilitating > communications. > > On Mon, Jun 17, 2019 at 11:40 AM David Ranch <amprgw(a)trinnet.net> wrote: > > > I'm not an expert on FCC Part 97 and I don't want to derail this > > conversation but I don't think some of these protocols are legally > > self-identifying. > > > > > > > ---------- Forwarded message ---------- > From: Steve L via 44Net <44net(a)mailman.ampr.org> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Cc: Steve L <kb9mwr(a)gmail.com> > Bcc: > Date: Mon, 17 Jun 2019 15:54:13 -0500 > Subject: Re: [44net] NPR (New Packet Radio) : new firmware with 56kBaud > and 120kBaud > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net >

1 0

Hamnet over 70cm : NPR (New Packet Radio)
by f4hdk 08 Jun '19

08 Jun '19

Hello, I am Guillaume, callsign F4HDK, a french amateur-radio operator, and a hacker-maker. I would like to share with you my last project : NPR (New Packet Radio). All documentation is provided here : https://hackaday.io/project/164092-npr-new-packet-radio This solution can transport bi directional IP trafic over 70cm radio links, in a 'point to multipoint' topology, at datarate up to 500kbps. This can be used to increase the range of existing HSMM-Hamnet networks, at lower datarates. It's designed for "access", not backbone, and not designed for H24 use. Its is 100% open-source. Do not hesitate to ask me questions about it. I hope it will interest some people here. 73, Guillaume F4HDK

16 41

Re: [44net] Hamnet over 70cm : NPR (New Packet Radio)
by Rob Janssen 05 Jun '19

05 Jun '19

> On Mon, 3 Jun 2019, David Ranch wrote: > >/(6) A RTTY, data or multiplexed emission using a specified digital code /> >/listed in ?97.309(a) of this part may be transmitted. The symbol rate must not /> >/exceed 56 kilobauds. A RTTY, data or multiplexed emission using an unspecified /> >/digital code under the limitations listed in ?97.309(b) of this part also may /> >/be transmitted. The authorized bandwidth is 100 kHz. / > 56 kilobauds is because the Telebit Trailblazer existed; it used OFDM > and 6 "baud" carriers. The Trailblazer was fast, but it wasn't *that* fast! It actually was like 19200 baud async, internally some 18kbps sync. This was fast compared to the usual V.22bis (2400 bps) modems of the day, but of course later telephone modems appeared that could to 56k. We ran a Unix system with UUCP at work in those days but we could not use modems that fast because the machine wasn't able to handle full 19200 baud async I/O as it could not handle the interrupt load... those were the days. (It was an NCR system with a separate processor for serial I/O, but IBM PC and clones in those days also struggled at 19200, that is why the 16550 chip with hardware FIFO was created...) A couple of years later I bought a ZyXEL U-1496+ modem that also did 19200 over phone lines, and was popular at some local ISPs. Like the Trailblazer it also used a 68000 processor and it cost well over $500 in local currency. I agree that those modems are not going to work over radio. Even on telephone lines they perform lengthy "training" sequences to measure the phase response of the line, and then assume it remains the same over the duration of the call. Rob

1 0

Re: [44net] Telebit Trailblazer over radio
by John Gilmore 05 Jun '19

05 Jun '19

Telebit was doing the modulation in signal processing software in a dedicated big-grasshopper-sized Motorola 68000 chip inside the modem. These days we could do the same modulation in software in just about any chip. But as Brian said, the signal impairments in multi kilometer twisted pair telephone circuits with occasional loading coils, chopped into 56k digital bitstreams and reconstituted at the other end before transiting a different long twisted pair, are very different than the impairments typically experienced when passing a signal thru typical radio circuitry and kilometers of radio "ether" and interference. There's free software for messing with OFDM over narrowband radio (e.g. not WiFi); here are a few starting points: https://github.com/rwth-ti/gr-ofdm https://ro.uow.edu.au/cgi/viewcontent.cgi?article=4984&context=theses https://github.com/kit-cel/gr-lte John

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net