thats is why the main callsign should be based on the club callsign and not based on the
technical support user.
if the ip space was for an organization that does not have a callsign the ham in it should
require to register the organisation as a club.
Pierre
VE2PF
________________________________________
De : Cliff Sojourner via 44net <44net(a)mailman.ampr.org>
Envoyé : 15 juin 2024 14:57
À : Eric Johnson; Eric Johnson via 44net; Terence Theijn
Cc : Amprnet 44 Net
Objet : [44net] Re: Club Callsign Verification
Why couldn't you use that ham's callsign for
DNS services?
What happens when the trustee changes?
Gotta rename everything!
Not good.
Cliff K6CLS CM87
On June 15, 2024 11:23:32 AM PDT, Eric Johnson via 44net <44net(a)mailman.ampr.org>
wrote:
Ok, makes sense. It sounds like there is a ham responsible for maintaining the node. Why
couldn't you use that ham's callsign for DNS services?
Eric AE0JE
On Sat, Jun 15, 2024, 1:55 PM Terence Theijn
<terence@theijn.nl<mailto:terence@theijn.nl>> wrote:
Ibm isn’t the user/maintainer they just host the site. They don’t have access to or are
allowed to use the network in any way. They just host the pop in my example.
So just providing roof access and power.
73
On 15 Jun 2024, at 19:46, Eric Johnson via 44net
<44net@mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote:
I understand it's not a repeater, that's just the best analogy I have. We have a
similar system here, but it's not as well-known or widespread as hamnet.
Usually, any DNS name that resolves to an IP is equivalent. Can you elaborate on why you
couldn't use a subdomain on a callsign?
Furthermore, could you address the questions regarding non-ham (IBM) use of this system?
Eric AE0JE
On Sat, Jun 15, 2024, 1:38 PM Terence Theijn
<terence@theijn.nl<mailto:terence@theijn.nl>> wrote:
Hamnet pop isn’t a radio repeater. It’s a pop for hamnet. We call the 44 net hamnet here
and it runs on wireless links.
It’s a complete wireless mesh network with many p2p links providing network connectivity
to other hams/repeaters etc.
So just adding a subdomain before a callsign isn’t going to cut the needs.
73
PD3T
On 15 Jun 2024, at 14:27, Eric Johnson
<micromashor@gmail.com<mailto:micromashor@gmail.com>> wrote:
Chris: Sounds good, thank you.
Terence,
I am not the most familiar with hamnet, although at some point, there has to be a ham
involved, right? The way repeaters typically work here is that a ham or group of hams
speaks to a building owner and asks for an agreement to host a repeater and a little bit
of rooftop space. That repeater is then usually referred to by the callsign of the ham(s)
who maintain it and have the agreement with the building owner.
Forgive me if I'm misunderstanding, but does hamnet usually work in a similar way? If
so, couldn't the site be named
pi90ibm.pd3t.ampr.org<http://pi90ibm.pd3t.ampr.org/>g/>, assuming you are the
maintainer of that site?
If there isn't a ham involved at any step:
- How is it legal use of the amateur bands?
- Is it really a ham radio network at that point?
Eric AE0JE
On Sat, Jun 15, 2024, 6:01 AM Terence Theijn
<terence@theijn.nl<mailto:terence@theijn.nl>> wrote:
I see a lot of issues with hamnet pops without clubcallsings and are just commercial
building owners willing to host the housing for a hamnet pop to extend the amprnet
wireless network range.
You do want those site to be recognizable some of those sites can even host services like
remote sdrs.
For example ibm is willing to host a pop for network coverage. To make it recognizable you
can name it pi90ibm. This aint an official callsign. How is one going to verify that?
Did you think about those?
Regards
PD3T
On 15 Jun 2024, at 09:12, Chris via 44net
<44net@mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote:
A copy of the official PDF download from the ULS site of the club’s call sign;
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org<mailto:44net@mailman.ampr.org>
To unsubscribe send an email to
44net-leave@mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>