44net May 2012

44net@mailman.ampr.org

28 participants
22 discussions

by Maiko Langelaar

Good afternoon, It would see that 44.133.48.66 is popping, snmpding, and other amounts of traffic from time to time to various ampr.org systems and doing so *without warning* type of thing. I just got hit with a bunch of SNMP requests, others have been hit with POP requests. Can anyone find out who the owner of that particular system or network is, so that I can contact the entity or person. Or perhaps a bit more draconian, can someone deal with it. Thanks in advance. Maiko Langelaar VE4KLM

11 years, 2 months

Re: [44net] directly routed subnets

by William P.J. Bressette

As well all of a advertised block must me advertised only from a single asn. This is where this will start to get tricky. Sent from my Windows Phone ________________________________ From: Michael Fox - N6MEF Sent: 2012-03-16 12:56 To: 'AMPRNet working group' Subject: Re: [44net] directly routed subnets (Please trim inclusions from previous messages) _______________________________________________ There are different levels of peering. The policies below describe tier 1/2 peering between the big guys. Most peering relationships are not at that level. Many small businesses have peering with more than one service provider. It's quite common. The current startup I work for has a /24 that they announce to their colo provider in San Francisco, as well as the ISP that serves their HQ location further down the peninsula. (The colo and their HQ are tied together as one ASN). Michael N6MEF -----Original Message----- From: 44net-bounces+n6mef=mefox.org(a)hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Tim Pozar Sent: Friday, March 16, 2012 9:43 AM To: AMPRNet working group Subject: Re: [44net] directly routed subnets (Please trim inclusions from previous messages) _______________________________________________ On Mar 16, 2012, at 8:20 AM, Brian Kantor wrote: > Perhaps I should start collecting AUPs from various sources rather > than having to create one from scratch. > > URLs to model AUPs would be appreciated. In concern of BGP peering... You can see some of the hoops that ARIN requires for an ASN at: https://www.arin.net/policy/nrpm.html See section 5 <https://www.arin.net/policy/nrpm.html#five> for ASN requirements. Certainly there are policies for peering that other ASNs. Some of these policies are good to look at for requirements for announcing address space. Some of the requirements are a bit onerous and don't apply. Comcast has their set of requirements at: http://www.comcast.com/peering/ Certainly things like "Applicant must operate a US-wide IP backbone whose links are primarily 10 Gbps or greater" should not be a requirement. But points like: * Applicant must have a professionally managed 24x7 NOC and agree to repair or otherwise remedy any problems within a reasonable timeframe. Applicant must also agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems. or * Applicant must maintain responsive abuse contacts for reporting and dealing with UCE (Unsolicited Commercial Email), technical contact information for capacity planning and provisioning and administrative contacts for all legal notices. may be a good idea. The latter one would be needed to help resolve poisoning of address space and getting listed on various RBLs. Other sites that have peering requirements can be seen at: ATT - http://www.corp.att.com/peering/ Verizon - http://www.verizonbusiness.com/terms/peering/ AOL - http://www.atdn.net/settlement_free_int.shtml MFN/Abovenet - http://www.above.net/peering/ If folks want can make a stab at a draft for requirements for someone announcing 44/8 space. Tim _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

13 years

Re: [44net] directly routed subnets

by Tim Osburn

Brian and All, I always thought it was a waste of a routable /8 to not have it routed on the Internet, otherwise why are people just not using IANA space instead? However, if it is to be routed on the internet I think some ground rules must be established of what is and is not acceptable and penalties for not following the rules and established guidelines. Additionally, and I bring this up again, a RWHOIS server should/must be used (tied in with ARIN on the 44/8 allocation) so that people can query specific address space that will return the contact/owner of whatever space is being advertised for whatever reason. Additionally, IRR entries should also be required for anyone wanting to advertise space via BGP. Those should be some common sence polices that need to be followed at the very minimum. Obviously nothing smaller then a /24 should be advertised on the internet as most Tier 1 carriers will block any address space that is smaller in their BGP configs. I don't know what the whole breakup of space looks like within each coordinator's /16 space (for those that have a /16 of space), but I would think there surely is space in each that could be a usable /24 or larger that could be utilized for that. Alternatively there seems to be a lot of space at the upper end of the 44 block that could be used for internet routed blocks if we wanted to use that first? IP Space justification will be whole issue within it's self as well, because if you only REALLY need /28 or /27 of IP's, one will still need to advertise a /24. Perhaps who ever advertises space via BGP should accept the condition that if only a portion of the advertise space is being used that you will accept and allow another person needing the available space so that it's not wasted. This could be tracked and allocated via the rwhois server in conjunction with entries in IRR. UCSD can still advertise the 44/8, and of course if anyone advertises a more specific route, that will be preferred of the larger aggregate. Be nice if we were all on a IRC chat channel to bounce ideas around? If anyone is interested, how about channel #44net on IRC server network freenode (irc.freenode.net). I'm on there now. Tim Osburn www.osburn.com 206.812.6214 W7RSZ On Tue, 6 Mar 2012, Brian Kantor wrote: > Date: Tue, 6 Mar 2012 11:14:57 -0800 > From: Brian Kantor <Brian(a)ucsd.edu> > Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > To: 44net(a)hamradio.ucsd.edu > Subject: [44net] directly routed subnets > > I've gotten several requests for directly routed subnets (ie, BGP announced > CIDR blocks as subnets of 44/8, not tunneled) for ham radio use. These are > people who want to set up HSMM networks in the ham bands, D-Star > constellations, etc. > > I thought I'd ask folks what they think of the idea of setting aside part of > the address space for that purpose? > > What issues do you see arising from doing so? > - Brian > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net >

13 years

Some newbie guidance.

by Max Lock

Hi All, I'm interested in building a tcp packet network for my local town. Theres no packet activity here, apart from aprs. The local club are generally focused on competitions, but there is a local hackspace in it's infancy with a number of people interested in doing 'something cool' with packet. So, I've been in touch with the UK ampr co-ordinator, and am now administering our local /24. Given I have a clean slate what subnetting approaches have people found that work well, maybe subnets for different technologies dstar, ip over x25 packet etc. In the UK I understand there's essentially no routing, but have read about routing being used in the US, what are the reasons? I don't currently have a fixed IP, so am currently unable to provide 44 net access to the rest of the world unless I can come up with something clever, or a fixed IP. Has anyone successfully implemented a workaround, maybe an ip tunnel from another host with a fixed ip? If anyone has any documents on any aspects of ampr network design, or links I'd be very interested in taking a look. I want to get as much right first time as possible. -Cheers Max G7UOZ

13 years

Help please

by Jerry

Hello. Does anyone have a working JNOS2 autoexec.nos. running under linux RedHat Fedora 4 Looking for the following minimum. 1 RF port com 1 1 Ethernet lan port Converse server Net 44 access. I would like to use it as a reference and or modify for my use.. Many Thanks Jerry

13 years

44 AMPR email list issues..

by David Ranch

Hello Everyone, I noticed two things today when trying to invite a prospective packet user into the AMPR group: 1. The mailmail list manager at http://hamradio.ucsd.edu/mailman/listinfo/44net isn't responding 2. It seems the http://wiki.ampr-gateways.org/index.php?title=AMPRnet_contacts still points users to 44Net-owner(a)cows.net --David

13 years

Unsuscribe

by Joshua Fuller

Sorry if this hits the list

13 years

Building block for rebuild of AMPRNET

by John D. Hays

A new digital radio was announced at Dayton - http://nwdigitalradio.com http://groups.yahoo.com/group/UniversalDigitalRadio ------------------------------ 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>

13 years

Re: [44net] Network map of active AMPR stations -- Packet "proxy arp" in Linux and/or JNOS?

by Kutche, Jerry (Mitchell) USA

Many thanks.. I bet you are correct.. I will see if I can fix it on my end.. Have a nice day... Jerry

13 years

Network map of active AMPR stations -- Packet "proxy arp" in Linux and/or JNOS?

by David Ranch

Hello AMPR folk, I'm curious if there is an map of *active* geo-ip located AMPR stations out there? Ideally, I'm thinking of something like the various CONVERSE maps out there .. for example: http://www.wwconvers.ampr.org/ . The Michagan AMPR people do have a live monitoring system but it's text based: http://server1.nuge.com/~drg/network.html and I'm specifically looking for a Northern California map. Maybe there is something like an MRTG system that actively probes these systems from say the AMPR hub in San Diego? I'm also curious if anyone has ever heard of the following: I'm going on a vacation this summer where I know there isn't any reachable packet systems (both APRS or known packet systems) due to the mountain terrain. I know because I was there last year and though I could hear very faint packet stations, nothing could be decoded. What *is* available here is the commercial cell network and what I was thinking was tethering my Linux machine to the cell IP network and running an AXIP/AXUDP tunnel to re-link into the fairly extensive 145.050 KB2KB packet network: http://varmintal.com/ahamp.htm . I don't think this would be too difficult but what I'm trying to figure out is if it's possible to have my Linux machine send beacons, netrom updates, etc. from my machine via a tunnel to a remote AMPR station (proxy arp if you will) and then have all those AX.25 packets broadcasted on RF from there. There are a few Northern Califnornia Linux-based stations I know of that are on AMPR with JNOS that might be willing to try something like this but I wanted to run it by the group to see if it's been done / impossible / etc. --David

13 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net May 2012