I know a couple of groups now have proper reverse delegation of DNS for their subnets… Wondering who to drop a line to so I can get 44.103.0.0/19 delegated to a.ns.mi6wan.net and b.ns.mi6wan.net ?
Didn’t see it in the portal or wiki and my notes from a few months ago are foggy...
--
Fredric Moses - W8FSM - WQOG498
fred(a)moses.bz
All,
I've added a new tool that I'd like you to test. This web application
should provide the registration code required by APRS software suites.
In order to use it, you must browse to:
http://kb3vwg-010.ampr.org/tools/aprscode
or
http://44.60.44.10/tools/aprscode
If you're on AMPRNet, you should be able to enter the callsign and look
up the registration code. If you access it from outside of AMPRNet, you
will be prompted for an access code (1234).
Please let me know how it works
73,
KB3VWG
> Subject:
> Re: [44net] Portal
> From:
> Tom Hayward <esarfl(a)gmail.com>
> Date:
> 02/26/2015 08:06 PM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> I think if you were to open source the portal you would get more
> volunteers. I, and many other open source developers, tend to wait to
> jump in to a new project until we have an itch that needs scratching.
> When a bug affects me, I'll look to the source to see if I can squash
> it. If I can, the project maintainer can expect a patch from me. If
> the source isn't public, I'll send a bug report to the developer. I
> presume you would prefer patches to bug reports.
I agree with that. I have submitted several reports and explained my requirements to Tom SP2L
but as I have no access to the code I cannot have a glance to see how quickly some of my immediate
requirements can be built in, let alone do the work and submit it.
I still get "DNS requests" from users who apparently do not see the big red print on top of the DNS page,
and I cannot edit the subnet structure in the system to match reality. I submitted it in text form to
Chris long ago but it was not inserted.
We are currently building a HAMNET similar to what has been done in Germany and Austria, and
we really need a working system some time. I fully understand that time is not always available,
but some way has to be found to keep the day-to-day operations possible, maybe with a lower
level access to the data when writing code for the userfriendly web frontend is the bottleneck.
Rob
> Subject:
> Re: [44net] Portal
> From:
> "SP2L-wp" <sp2l(a)wp.pl>
> Date:
> 02/26/2015 11:24 PM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
>
>
> All of us, we are just(?) human beings. We make
> mistakes, we forget things... Also, all of us,
> we have our private life, family, health problems...
> And what Chris perfectly pointed out, sometime
> life unexpectedly, without any excuse - intervenes!
> Thus making our life much harder and tough...
Sure I agree with that. But as it is, the portal is so far from what we need, and
the move towards the goal has been so slow, that I think we must re-think what to do.
It is all a hobby, but at times some people are very active developing some part of
it, and it becomes a problem when other parts don't keep up with the needs and they
are dependent on it.
This afternoon I entered a lot of data in the HAMNET DB. (hamnetdb.net)
That system is much more like what is required. I could easily enter existing subnet
layouts and other definitions, because it does not have that strict "owner" model
that the portal has. And it also allows to enter a lot more info.
Of course it does not have the links to the tunnel gateway and RIP server, and some
more info would be required for that (like defining gateway entries), but it is an
opensource project and it might well be easier to extend it towards what we need
than to continue developing the portal.
Rob
+1
This needs to be open source, it's a major core component of the AMPRnet space.
On February 27, 2015 9:38:21 AM EST, "Javier Henderson (javier)" <javier(a)cisco.com> wrote:
>
>Why the reluctance to put the code on a public repo that is easily
>accessible without having to ask?
--
Bryan Fields
727-409-1194
http://bryanfields.net
> Subject:
> Re: [44net] 44.151.29.29/32 F4LTS
> From:
> "Marc, LX1DUC" <lx1duc(a)laru.lu>
> Date:
> 02/25/2015 08:25 PM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>> >I would be happy to scrap the Portal and go back to the procmail
>> >scripts that Jim Fuller developed and operated for decades.
>> >Things worked, and worked dependably, back then!!
>> >
>> >The Portal is way too "vaccuumous" for me:(
>> >
>> >--- Jay WB8TKL
> Hello Jay,
>
> I assume that like any development project, Jim's solution didn't work
> 100% from the beginning either. Cut the developers of the portal some
> slack and report your issues here, so the issues become known and can
> be fixed (or someone may provide a workaround).
>
> Anyway the thanks to all the developers on the project!
>
> 73 de Marc
I agree with that in principle, but I have reported several issues and rarely ever was anything
changed to solve those issues, while in the meantime things were changed that caused
even more issues (like the mandatory selection of a registered subnet for an IPIP tunnel),
or that added features that were not near the top of any wishlist observed here (like an API).
What I need in my daily work as a coordinator in a network that has been springing into life
again is a usable mechanism for address assignment, and a way to edit an existing structure
into the new database. Without those present, I have to work around the system and tell
people to ignore features and make requests in a separate mail.
That would be fine if there would be visible progress, say a new feature every month or two,
but I have a hard time seeing any.
Rob
The other day I helped another 44net user troubleshoot his IPIP
configuration by running a traceroute from our network. He asked,
"what is the last working hop?" I decided it might be useful to the
community at large to release a tool that allowed doing this test from
our network without waiting for me to run a command.
Here it is:
http://trace.hamwan.net/
It is simply a web interface to mtr. I hope this allows people to
confirm their IPIP tunnels are working properly.
The tool is published on non-44net IPv4 and IPv6 addresses, in case
your tunnels aren't working properly yet. (This plan might not be as
good as I'd hoped, because the DNS is still on 44.24.240/20.) The
source IP for the actual traceroute will be 44.24.241.98.
If you would like to deploy this on your piece of 44net, or improve
the code, the source is available here:
https://github.com/kd7lxl/mtr-web
Tom KD7LXL
Hello Andrew et al.
I would like politely remark, that although I participate
in portal.ampr.org development, my only task (so far)
to which I volunteered, is polish language version
of portal.ampr.org
Surely, working closely with the source code of portal
I spotted some minor mistakes, misprints and so on
which I always passed to Chris for review.
But to be candid, myself I introduced to the code
(fortunately ONLY in polish language version!)
some mistakes which made this part of code
temporary unusable; Chris needed to correct them!
All of us, we are just(?) human beings. We make
mistakes, we forget things... Also, all of us,
we have our private life, family, health problems...
And what Chris perfectly pointed out, sometime
life unexpectedly, without any excuse - intervenes!
Thus making our life much harder and tough...
With best regards from Gdynia.
_____
Tom - SP2L
(ex sp2lob)
__________________________
Send from Sony Xperia Z1
http://aqua-mail.com
On 2/26/15 4:25 PM, Andrew Ragone (RIT Student) wrote:
> To clarify, too, this would be not only for the portal but the website as
> well ... in which everyone could contribute to web content / wiki to
> describe aspects of 44net and IP in Amateur Radio.
have you seen http://wiki.ampr.org/index.php/Main_Page ?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
> Subject:
> [44net] 44.151.29.29/32 F4LTS
> From:
> "Marc, LX1DUC" <lx1duc(a)laru.lu>
> Date:
> 02/14/2015 12:21 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Good evening,
>
> is Eric F4LTS on this list or does anybody have his contact data?
>
> Eric has added network 44.151.29.29/32 with Gateway 44.151.29.29, once
> the IPIP interface on my router comes up, the route for
> 44.151.29.29/32 via 44.151.29.29 comes up, which in turn takes down
> the interface which disabled the route, which allows the interface to
> come up... a fine loop.
>
> I had to filter his network 44.151.29.29/32 from the results I fetch
> via the API in order to keep my log size down.
>
> I'm not sure if the portal should allow the gateway for a network to
> between inside that same network. I think it makes no sense but please
> correct me if I'm wrong.
>
> 73 de Marc, LX1DUC
It is certainly not correct... fortunately ampr-ripd ignores such routes after it was found
that other people (like SA0BXI) had created them and they caused encapsulation loops.
But of course you are right, the portal should simply refuse to store such incorrect
information in the first place. It should issue an error message that makes the user
think again about what they have requested.
I am a bit disappointed about the progress in the portal development. Sure it can happen that
people are temporarily busy and have to postpone things a bit until more time is available,
but the portal as it is now has halted the development of amprnet and left everything in
a stalemate situation. The DNS part needs to be finished, the allocation of subnets has
to be much more flexible, overrides have to be made available to coordinators, and some
address management tools have to be added. When it is decided that this cannot be done
in the time available to the developer, it may be better to switch to another management system
like the hamnet-db.
73,
Rob
