Hi all.
Just got a notice from our network person that he'd received an email
from Chris notifying him of a renumbering of our allocated segments.
Since I couldn't remember a discussion here (please excuse me if this
has been discussed before), I just wanted to raise a few question - out
of curiosity.
We currently have a few /24 allocations within the 44.141.0.0/16
regional block (Norway). I think two or three of the /24 blocks are
published via BGP.
In the email, we're requested to renumber, and move the BGP announced
segments over to the 44.31.0.0/16 (in the US regional /9 block). I
don't think we've heard anything about the other addresses in
44.141.0.0/16 which are not BGP announced?
I guess I'm curious about the rationale behind this decision? I think
efficiency was stated, but I really can't see any big difference in
having a /24 announced either here or there? Since we don't have the
same upstream providers as our neighboring nets, there won't be any
aggregation benefits (?).
Is the plan to also deprecate the national and regional allocations?
For our part, quite a few of the devices with 44-addresses are on
mountain tops (beacons, remote receivers, sensors, etc.), but we have a
4 month window, starting in a months time, to get up there and do the
renumbering. No big deal..
Just curious what the thoughts are..
--Magne / LA1BFA
Hello everyone.
Maybe a long shot but figure there is some cross over. I setup an instance of APRSC in a "very good" location network wise (internet exchange, very low regional latency, no other APRS tier 2 servers close latency wise, data center, virtualized, multihomed etc - this is my day job, I run AS 55016 and announce 44net addresses via BGP, of which one is being used for APRSC). Anyway, would like to reach out to the folks at aprs2.net and see if I can get my server added to the noam.aprs2.net pool - pending meeting their requirements of course. I cant find any contact information however about who would be the correct person to contact about that, or the process to apply. Hoping someone here can help me get in touch?
-Colin / VA6CCB
Good day,
This message is for all of you using the NNTP on VA2OM, due to a
misunderstanding in gateway configurations I had to do some changes.
Now you can access the NNTP using jnos.ve2pkt.ampr.org port 119, if you
like to POP some of your mail, you need to contact me for a access.
if you have any question, feel free to ask by sending a message to:
va2om(a)jnos.ve2pkt.ampr.org
This is the same for all of you who had and AXIP linlk to VA2OM. please
contact me
--
73 de Jean,
VA2OM / VE2PKT
All,
I'm actually learning a lot. Some I heard before; but didn't understand the implication - (not saying the research is/was bad). I'd simply say (as I read more on this topic) - that it wouldn't make any sense for an NGN44 Group to finally suggest something and it's not compatible with the "owner's" desire for the block/network. I digress.
73,
- Lynwood
KB3VWG
Good day,
To all of you having a link or trying to reach VE2PKT.AMPR.ORG, I
am having difficulty creating a new gateway on the portal.
I keep getting the gateway IP all ready exist. But nothing is show when
I log in. Working on the problem. Will let know the list
once the gateway IP address is updated.
--
73 de Jean,
VA2OM / VE2PKT
Is there an allocation for documentation similar to RFC 5737? I was going to upload some stuff to the GitLab server but I wanted to generalize it so people didn't just copy/paste deploy stuff with my IP allocations in it. I looked on the portal but couldn't find anything. If there isn't, I'd like to propose that two /24s get set aside for documentation out of 44.0.0.0/9 that don't seem ripe for future use such as 44.0.192.0/24 and 44.1.255.0/24.
Jason
Clive,
Can you verify your callsign, please. I"m having a serious issue looking it up.
Since transit is kinda physical (and AMPR/ARDC/TaskForce/committees are working on something for the future), I'm not sure why your offer makes sense. Can you more clearly explain how others not located near your data center obtain benefit?
73,
- Lynwood
KB3VWG
-----Original Message-----
Message: 1
Date: Sun, 28 Mar 2021 19:41:09 -0700
From: Clive Blackledge <clive(a)ansible.org>
To: 44Net general discussion <44net(a)mailman.ampr.org>
Subject: Re: [44net] DigitalOcean / Droplet
Message-ID:
<CAOqEX=gcXGmiKYOkNCueosi0=F-w2wtXzFQ29mNAiSo2K+hh6A(a)mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Angelo,
Can you describe some of the issues or requirements that makes finding IP
transit difficult? I can suggest quite a few options that have worked out
for me, but it usually requires asking for exactly the right thing and
little bit of luck of finding the right person.
It is possible some of us here can start a joint venture and share some of
the cost. Ideally we'd do it under the AMPRnet name, I guess it really can
be under any corporate/LLC name.
73,
-Clive
KF6DFMA
Hi All,
If Rial, N0OTZ is seeing this, please can you email me privately.
If anyone knows, or is in contact with N0OTZ, please could you pass this message on.
Thanks,
Chris - G1FEF
Hello friends,
I have a problem with incoming connections to telnet port (23) in the login
step that never put their credentials give a open tcp connection causing me
to have a large sockets open. I have tried the mbox tdisc command which is
not valid since the connection is still in the login stage without entering
the mbox, consuming connection resources in the system. There will be some
command to kill automatically the connections in the login stage by idle
time (disc-timer) to delete this? JNOS 2.0m.4 (linux).
Thanks, 73 de Gabriel YV5KXE
YV AmprNet coord.
