Hello everyone,
To be more concrete and to better understand issues behind the TAC
proposal, I draw a scheme for fictional scenario where German user with
non-public 44 IP wants to access via HAMNET a Dutch user's web service,
running on his computer with public 44 IP:
http://ftp.eranova.si/44net/scenario-de-nl-s57nk-jul21.png
Both have 44 IPs in 44.128/16 range covered in TAC proposal. HAMNET is a
closed network, non accessible from Internet while Dutch 44net is
completely open to public access. Two extreme cases therefore.
German user has set a simple static route: all traffic to 44.128/10
should go via HAMNET while all the rest via NAT to internet. NAT is
needed because his local 44 IP is from a HAMNET's subnet which is not
announced all over the Internet via BGP.
Contrary to Dutch user, which local 44 IP is from BGP announced subnet
and therefore everyone from Internet can access his web server. Also, he
can access anything on the public Internet without any NAT needed.
Furthermore, he is proudly represented on the Internet as radio amateur
because of his 44 IP.
Now to the scenario: German user finds his Dutch college website
interesting and he'd like to access it. But his 44.128/10 static route
will direct him over the HAMNET, not to public Internet.
No access possible until HAMNET is connected directly to Dutch 44net.
Now suppose we connect both those nets too.
Dutch web server will now respond to German college's web request and
response will be hopefully routed back to him. Hopefully the requests
from public internet will also be served as before.
Am I correct with this scenario? Are there any routing issues, are they
already solved? Or how to solve them?
If this scenario doable, are there some more issues?
Best 73
Janko S57NK
Hi there,
I found an organization called SSL Corporation (AS38281) start announcing 44.159.159.0/24 since 2021-07-29 14:08:00. I found it here: https://radar.qrator.net/search?query=44.159.159.0%2F24
It is strange with that a renumber plan which says 44.128/10 will be used for radio only was just came out several days ago. I tried to find it on portal, but there is not such a prefix.
I also tried to look it up with whois, but it reports a database error:
$ whois -h whois.ampr.org 44.159.159.0
#
# ARDC WHOIS data and services are subject to the Terms of Use
# available at: http://www.ampr.org
#
# If you see inaccuracies in the results, please report them at
# https://portal.ampr.org/contact-us.php
#
Database error#
# ARDC WHOIS data and services are subject to the Terms of Use
# available at: http://www.ampr.org
#
# If you see inaccuracies in the results, please report them at
# https://portal.ampr.org/contact-us.php
#
This prefix is announced with a route object:
route: 44.159.159.0/24
origin: AS38281
descr: Assigned by AMPRNET for radio experiment usage.
admin-c: Charles Wang
tech-c: Charles Wang
mnt-by: MAINT-AS38281
changed: charleswang(a)nekollc.com 20210729 #13:20:12Z
source: RADB
I am here to ask if this announcement authorized?
73,
Soha Jin
Hello Ian!
Speaking as the TAC again, RPKI ROAs and route(6) objects are also something we worked on. It’s going to be proposed later, definitely after the summer, and will hopefully help many users and make Internet routing more secure for everyone!
Thanks,
Antonis
> On 28 Jul 2021, at 23:03, Ian Chilton <ian(a)chilton.me.uk> wrote:
>
> Hi,
>
> Totally agree with all of the points about IPv6!
>
> On a related note….
>
> I’m sure this has been discussed many times over, but with so many announcing 44 space with BGP, I think going forward it’s important to be able
> to create RPKI ROAs (and IRRDB objects) for the space.
>
> Thanks,
>
> Ian
Hello 44Net,
Just to advise that there is likely to be heavy packet loss through the gateway server at UCSD currently. The 1G link has been fully saturated since just before midnight PST (see attached MRTG graph). I can’t even login to the server reliably enough to see what the traffic is but I guess some DDOS is ongoing. I will keep you informed as and when I have further information.
73,
Chris - G1FEF
Hello 44net!
Given that he just posted info for the next community meeting, this is
an excellent opportunity to welcome a new employee - Dan Romanchik,
KB6NU, who is our new Content Manager. He'll be helping us with all
things related to writing - newsletters, web content, and even helping
with grantee proposals.
Here's a little bit about Dan:
Dan, KB6NU, has been a radio geek ever since he turned on his
grandparents' Philco console radio about age 10. He got his first
license at age 16, then obtained a BSEE degree from the University of
Detroit. After working as a test engineer for a dozen years or so, he
decided to direct his engineering talents in another direction and
became a technical editor for Test&Measurement World magazine, a post he
held for six years. After leaving the magazine, Dan was self-employed as
a website developer and freelance writer. He blogs about amateur radio
at KB6NU.Com and self-publishes the "No Nonsense" line of amateur radio
license study guides. He's also self published *21 Things to Do After
You Get Your Amateur Radio License" and *The CWGeek's Guide to Having
Fun with Morse Code." He feels his biggest accomplishement has been
helping thousands of people get their first amateur radio license or
upgrade to General and Extra, either by reading his study guides or by
attending the classes he teaches. He's very excited to now be working
with ARDC and hopes that his work here will help even more people have
fun with amateur radio.
Please join me in welcoming him!
73,
Rosy
--
Rosy Wolfe - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
We’re midway through 2021, and it’s time for the next ARDC Community Meeting! It will take place on:
Saturday, 24 July 2021
1700 UTC (10am PT / 1pm ET / 7pm CET)
In this meeting, we’ll cover:
Grants made to date in 2021, including our first grant made outside the U.S. to DARC.
Introductions of two new staff members:
Grants Manager – Chelsea Parraga, KF0FVJ
Content Manager – Dan Romanchik, KB6NU
Questions from our attendees.
The meeting will be held on Zoom. Info on how to join is below.
This meeting is open to all interested parties, so please tell your friends!
See you on July 24!
//
Zoom Info
ARDC is inviting you to a scheduled Zoom meeting.
Topic: July 24 Community Meeting
Time: Jul 24, 2021 10:00 AM Pacific Time (US and Canada)
Join Zoom Meeting
https://us02web.zoom.us/j/86944554944?pwd=ZjlFdk5aUGgydGFCSnluenNzbm9SUT09
Meeting ID: 869 4455 4944
Passcode: 44net
One tap mobile
+16699006833,,86944554944#,,,,738141# US (San Jose) +12532158782,,86944554944#,,,,738141# US (Tacoma)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
Meeting ID: 869 4455 4944
Passcode: 738141
Find your local number: https://us02web.zoom.us/u/kc7yFYiowZ