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 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 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, 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 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 wrote:
A copy of the official PDF download from the ULS site of the club’s call sign;
I think that using the hierarchy type of domain name is logical.
Something like hotel-dieux.ve2cbs.ampr.org where hotel-dieux is the site name ve2cbs is the club callsign and the rest is obvious.
This would be the real dns name I would use for the club I am the secretary and technical support.
But after that being said. Who would be able to control those dns? There should be a way to ID the tecnical support staff for the club call sign and those named as technical support be able to do the dns for the club.
In fact even a single user should be able to point another user as able to control the dns section of his/her allocation in case they are both sharing the same ip space for whatever reason, or the first does not know enough or understand enough to do it all.
But in any case all the ip allocation should have something like X.Y.ampr.org where Y is ALWAYS the call sign of the club or individual that requested the ip space. and X can be whatever that club or individual want.
Pierre
VE2PF
________________________________________ De : Eric Johnson via 44net 44net@mailman.ampr.org Envoyé : 15 juin 2024 13:45 À : Terence Theijn Cc : Amprnet 44 Net Objet : [44net] Re: Club Callsign Verification
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.nlmailto: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.commailto: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.orghttp://pi90ibm.pd3t.ampr.org/, 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.nlmailto: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.orgmailto:44net@mailman.ampr.org> wrote:
A copy of the official PDF download from the ULS site of the club’s call sign;
On Sat, Jun 15, 2024 at 2:41 PM pete M via 44net 44net@mailman.ampr.org wrote:
I think that using the hierarchy type of domain name is logical.
Something like hotel-dieux.ve2cbs.ampr.org where hotel-dieux is the site name ve2cbs is the club callsign and the rest is obvious.
This would be the real dns name I would use for the club I am the secretary and technical support.
But after that being said. Who would be able to control those dns? There should be a way to ID the tecnical support staff for the club call sign and those named as technical support be able to do the dns for the club.
In fact even a single user should be able to point another user as able to control the dns section of his/her allocation in case they are both sharing the same ip space for whatever reason, or the first does not know enough or understand enough to do it all.
Right now, the portal supports the concept of an organization that provides this functionality, albeit not in its fully elaborated form yet. But the ideas of multiple users associated with an organization, and assigning some sort of role-like permissions to those users, are there now.
What's missing is decoupling the idea of an organization from a specific user (I think) and allowing existing users to become affiliated with an organization, as opposed to creating new user accounts that are conceptually "owned" by the organization.
- Dan C.
I like this idea, it would be the simplest way to keep DNS namespacing clean and is in the spirit of how DNS was originally envisioned to work. There's obviously legacy allocations that do not follow this format, and we'd have to come up with a policy to address those. CNAMEs are an option, but they will break things like MX and TXT records if I recall correctly. An alternative that I've thought of is putting the controlling call sign in a TXT record for every host in the database.
Thanks, Dan Theisen KK7OZY
On Jun 15, 2024, at 15:31, Dan Cross via 44net 44net@mailman.ampr.org wrote:
On Sat, Jun 15, 2024 at 2:41 PM pete M via 44net 44net@mailman.ampr.org wrote:
I think that using the hierarchy type of domain name is logical.
Something like hotel-dieux.ve2cbs.ampr.org where hotel-dieux is the site name ve2cbs is the club callsign and the rest is obvious.
This would be the real dns name I would use for the club I am the secretary and technical support.
But after that being said. Who would be able to control those dns? There should be a way to ID the tecnical support staff for the club call sign and those named as technical support be able to do the dns for the club.
In fact even a single user should be able to point another user as able to control the dns section of his/her allocation in case they are both sharing the same ip space for whatever reason, or the first does not know enough or understand enough to do it all.
Right now, the portal supports the concept of an organization that provides this functionality, albeit not in its fully elaborated form yet. But the ideas of multiple users associated with an organization, and assigning some sort of role-like permissions to those users, are there now.
What's missing is decoupling the idea of an organization from a specific user (I think) and allowing existing users to become affiliated with an organization, as opposed to creating new user accounts that are conceptually "owned" by the organization.
- Dan C.
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
-
Dan Cross -
Daniel Theisen -
Eric Johnson -
pete M