18 Jul
2022
18 Jul
'22
2:55 p.m.
I did not claim that "because an operator has some involvement with an ISP that they
are by default up to no good".
When the ham that asked for the allocation had been active with a smaller allocation
before, I would
have asked him why he needs a /22. I never allocated a /22 to an individual. Subnets
that large are only
allocated to regions, where they are put up on radio access points where many users in the
region each
get a smaller allocation. The default is a /28 but some /27 and a single /26 exist. That
is about what you
can reasonably use as a single user. A /22 (1024 addresses) requires some explanation.
And it would not
be likely that for a first application, never having used AMPRnet, so many addresses would
be required.
So I do some research and find what I wrote below.
That does not mean that EVERY operator which has involvement with an ISP is rejected. Not
at all. When
they make a reasonable request, of course they get the allocation. And when it would be
to host some
amateur service that requires a lot of addresses, we could have offered to host the
servers as well.
(we do host amateur services like 230 echolink proxies, 10 echolink relays, brandmeister
services, etc)
Rob
On 7/18/22 03:59, Matt - VK2FLY via 44net wrote:
Hi Rob,
Just thought I would give you some feedback on your comment. I understand there seems to
have been a breach of the rules in the case Gary has brought to light. But i think
it's a big jump to cast dispersion on every Ham that happens to have connections with
an ISP that they are up to no good. When I first ask for my allocation (i also am a
principal at an ISP) i was told by my regional co-coordinator that I was an evil ISP
operator and my attempt to steal 44 net space would not be tolerated. I was perplexed by
there attitude as I was a legitimate licensed radio operator who wanted to use the space
for radio related things not only that I wanted to use my position within the ISP to help
other operators route 44 space for their radio projects for free without the added latency
and packet size constraints of a vpn. I must say i went away very disheartened with the
whole 44 net idea.
About a year later i learnt that the regional co-coordinator had moved on so I
re-applied and got a /24. Since then I have routed a few /28 /29's from my block to
local hams and clubs for radio projects, radio related web sites DMR and allstar networks
all for free thought the charity of the ISP that was mainlined by the radio community as
being evil.
I think it's a far leap to assume that just because an operator has some involvement
with an ISP that they are by default up to no good. In fact some of us are interested in
giving our services and vast knowledge obtained in the commercial world to radio related
projects for free and in good faith sticking within the rules. There's always some
bad apples sure. But not everyone is up to no good.
Best regards 73
Matt
On 17/7/2022 10:52 pm, Rob PE1CHL via 44net wrote:
Unfortunately it is not unheard of...
In the past I also got an allocation request for a /22 from a ham who had not been active
at all on AMPRnet before.
A little research showed that his son has an internet hosting company.
Not difficult to imagine what would have happened when I had assigned that block.
Of course, when a coordinator does it by himself it is more difficult to track. Maybe in
the new system where coordinators will be less bound to regions and other coordinators
could oversee this happening. But of course they would still have to do that and report
it.
Rob
On 7/17/22 12:50, F4HIN via 44net wrote:
In reality, after searching on the AMPR portal,
this block was assigned to a ham. This ham is the national Hamnet coordinator of a
country, and the person using and misusing it is none other than his son who is not a ham!
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org