44net

44net@mailman.ampr.org

4 participants
3198 discussions

Hello
by Tom C 02 Mar '17

02 Mar '17

I've bitten the bullet and started to make some progress getting on 44net. I'm certain my current issues are firewall and I'll get it sorted out. My non-ham network is in the 172.29.60.0/22 range. I don't think I'm leaking internal stuff to my partially built tunnel but If anyone sees packets from that block please let me know. Status: Attempted to ping 44.0.0.1 on a system on the ampr enclave on my network, With tcpdump listening on the gateway ampr0 interface I can see packets going out on the interface but that doesn't mean the packets are getting out of the box. I'm not seeing a response but like I said, I think it's a firewall issue. I just wanted to say Hi to to everyone and say I'm looking forward to exchanging packets with everyone 73 de n2xu Tom Cardinal/MSgt USAF (Ret)/BSCS/Security+ ce -- 73 de N2XU/Tom Cardinal/MSgt USAF (Ret)/BSCS/Security+/IPv6 Certified

4 4

Re: [44net] AXUDP spec
by Rob Janssen 02 Mar '17

02 Mar '17

> Unfortunately, there are problems with AXIP and AXUDP ever since the > revisions of AX.25 were published - the AX.25 frames may get too big > to encapsulate in unfragmented IP and UDP frames. Any new document > would have to discuss the fragmentation issues, and I'll bet they're > not defined. (As far as I know, the same issue applies to ROSE, KISS, > and Net/Rom encapsulation too.) Is this an issue? The AXUDP protocol simply is "put AX.25 frames in UDP datagrams" and an UDP datagram can be nearly 64KB in size so I would not think there are any issues. UDP and IP handle the fragmentation and reassembly and the receiver gets the original datagram to insert it into the AX.25 stack. Of course, AXUDP senders should not set the DF flag, and if they do, they should not expect more than about 512 bytes maximum frame size. Which still is enough for classic AX.25 packet radio. > Do any of the various implementations of AX.25 encompass v2.0 et seq as > published by TAPR? Ie, is anyone actually implementing jumbo frames, > expanded frame sequence numbers, etc? Or should we just treat it as a > bad idea that should be buried and go on with the old protocol? The actual AX.25 version and extensions like jumbo frames and extended sequence numbers should not affect AXUDP at all. The UDP layer only replaces the HDLC layer normally used to transfer data over radio, and all things happening in AX.25 should be compatible between the endpoints, as always. Rob

1 0

amsat.org mail
by Rob Janssen 23 Feb '17

23 Feb '17

Earlier I wrote: > Well I did not get a mail from you, probably it has been lost somewhere due to spamfiltering. I now found how that happened... I use my @amsat.org address on this list, and I found that the forward address has been reset about 2 weeks ago, back to a value that it was a few months ago. I had changed it since. I still receive most of my mail because that other path still sort of works, but it tends to block a lot of mail that from the amsat.org forwarder as spam. So I now found a couple of mails in a spamfolder where I normally don't look anymore. I'm not sure what happened, there appears to be no announcement on the amsat.org page, but it could be that they had to restore a backup of the alias database. So when you use amsat.org and changed your forwarding address, it might be worthwhile to check if it is still OK. Rob

1 0

Re: [44net] Is AMPR still relatively active?
by Elias Basse 20 Feb '17

20 Feb '17

I have received repeated requests from a non licensed user. When I reject, he resubmits. It is obvious that this person may have an alterior motive as it is a hosting company. What to do in such cases? I have just let the request sit. None of the hams or it people in my area have ever heard of the hoster. Any way to ban a submission? Best, Elias Kd5jfe On Feb 20, 2017 3:00 AM, "Rob Janssen" <pe1chl(a)amsat.org> wrote: (Please trim inclusions from previous messages) _______________________________________________ > I was thinking what would be helpful is if there was specific information > required, it would be good to prompt for it ahead of time. In reading > through these threads, it appears there can be some variance in what may be > required by each coordinator. Perhaps instead of free form text block > there could be a means to prompt for some of the information that would be > considered qualifying fields. > That is a good point! There should be an optional text record for each network, to be entered by its coordinator, about the local requirements for allocation and that will be displayed on the request form above the input section. Rob _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

4 3

Re: [44net] Is AMPR still relatively active?
by Rob Janssen 20 Feb '17

20 Feb '17

> I was thinking what would be helpful is if there was specific information required, it would be good to prompt for it ahead of time. In reading through these threads, it appears there can be some variance in what may be required by each coordinator. Perhaps instead of free form text block there could be a means to prompt for some of the information that would be considered qualifying fields. That is a good point! There should be an optional text record for each network, to be entered by its coordinator, about the local requirements for allocation and that will be displayed on the request form above the input section. Rob

1 0

Re: [44net] Is AMPR still relatively active?
by Rob Janssen 20 Feb '17

20 Feb '17

> Thanks Tom. The portal already automatically sends reminder notices > to coordinators with outstanding allocation requests, twice a month. > If all the coordinators agree, we could change that to weekly. I don't think that will help. In the cases where I did not get a response from others it usually turned out they were moving, busy at work, etc. Overwhelming them with more notices is not going to solve that. > I find that the coordinations which take more than a few minutes to handle > are those where the requester is confused and asking for something that > is not sensible, so an email exchange is necessary to get the request > straightened out. That is correct. There should be an option for the coordinator to abandon the request and take the thing to e-mail. Now the only option is to reject the request, which often upsets the requester and also (because of language barriers) the requester often clicks all links in the message, causing it to be re-submitted. I would like to see a button on that screen that just deletes the request without further mail towards the requester, so I can then send mail and explain the situation. Rob

1 0

Re: [44net] How to reach VE2HOM?
by Rob Janssen 20 Feb '17

20 Feb '17

> Hello Rob, > I have receive your email this morning and reply to it before your send > on the group, I also close my amprnet for the moment. I'm new with the > mikrotik router and don't know all, I get information on the internet to > get it work. Sorry for the bad packet this is not intentionnal. > 73 de Pascal > ve2hom Hi Pascal, Well I did not get a mail from you, probably it has been lost somewhere due to spamfiltering. Good to hear you use a MikroTik router! It is possible to fix it on this kind of router. When you go to the IP->Firewall page and open the NAT tab, you will find an existing NAT rule that you use for your internet connection. It will probably show something like "masquerade", chain srcnat, out.interface ether1. You can just add another item like that, with the settings: chain srcnat src.address 192.168.0.0/16 out interface ! ether1 (click in the empty box for the ! to appear and select your internet interface) action src-nat to address 44.135.50.x (select an address you want to use for this) That should fix your problem, assuming you use this router only for internet and hamnet and have no other interfaces to other networks. This rule will make any traffic from the 192.168 range to be translated to a fixed address in hamnet (but only when it is not sent to the internet interface, that is where the other rule applies) Rob

1 0

Is AMPR still relatively active?
by F6CNB 19 Feb '17

19 Feb '17

Jim, For the european activity, you should read the Jann DG8NGN paper presented at the DCC 2014 in Austin, TX. http://tapr.org/pdf/DCC2014-TheEuropeanHAMNET-DG8NGN.pdf 73 Remi F6CNB/AG5IR

8 13

Re: [44net] Is AMPR still relatively active?
by William Lewis 19 Feb '17

19 Feb '17

> This also provides an opportunity for peer review in cases of misguided > allocation schemes >(such as breaking up a state block by county). > >Tom Tom. Can you validate why using a county scheme is misguided? ---------- Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) ______________________________________________ ---------- 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.

3 2

How to reach VE2HOM?
by Rob Janssen 19 Feb '17

19 Feb '17

Does anyone know how to reach VE2HOM? He is keeping his contact information well-hidden, it appears. His gateway at 206.80.251.222 is sending a lot of traffic with RFC1918 source address: Feb 19 15:00:53 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=13455 DF PROTO=TCP SPT=40510 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 Feb 19 15:00:57 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=38262 DF PROTO=TCP SPT=40512 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 Feb 19 15:01:01 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=14124 DF PROTO=TCP SPT=40480 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 Everyone remember: when you are combining the routing of AMPRnet and other network traffic, make sure you have the proper routing and/or NAT rules in place, and preferably also a filter, to make sure you don't send traffic with a source address like 192.168.0.5 into an AMPRnet tunnel. Rob

4 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net