Hi,
what is the official resource of 44net allocations?
http://noh.ucsd.edu/~brian/amprnets.txt disappeared and as my
understanding http://portal.ampr.org/networks.php is the new source.
Are former allocations completely removed? Archive from 2007:
http://www.eastnetpacket.net/files/amprnets.txt
Even http://portal.ampr.org/networks.php seems not to be the place with
latest changes. At least I'm aware of an allocation of 44.188.128.0/20
(Russia D-Star) and 44.168.0.0/16 (France HAMNET).
How can we keep track of latest allocations?
Thank you,
73,
Jann
DG8NGN
--
Jann Traschewski, Lenbachstr. 6, D-90489 Nuernberg, Germany
Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de
Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good evening,
I have been trying to get information about this issue via other
channels, unfortunately I don't seem to have the correct contact data.
As a "simple" end-user I created an allocation request, which was sent
to the manager account for the end-user's location.
The email contained this link:
https://portal.ampr.org/coord_ip_requests.php?a=edit&id=266
The page request me to login, however after login (using the manager
account) no information about the allocation request is shown, instead
the regular welcome page is shown. Pasting the URL into the browser
URL bar again brings up the request to login again.
So somehow I'm unable to process the allocation requests. I have no
clue how to solve this issue, could someone point me into the right
direction please?
73 de Marc, LX1DUC
- --
http://lx1duc.mcs.tel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRvO23AAoJEHFIN1T8ZA8vrr8P/jKo+ImFclLPg7QOl+TB8MaI
ThcAxxpWqBd1aN5Jv2RSm8Yx4TgpfS+59u3xDnbCqtJw66mSEChTTnt5fUESpYo3
604XYuRxEfL6oyXLPR19bmQWhb1J7dKOcwzTDQvRkqa8IAg7aP1m3R7tN13fvQAV
7GL3F/csxeG7XHxXxwy60V0tR50MFmI7dSeXdGNS7FyzZlzfUwRFuSv0nXMEl6uj
2DdlT0BVQtDkv6d128a2+5xL1UV3IOx8osI4mmUGcK3i9+aS8NhQXp83D9O1j3Wa
6SPo2DlLFfHzqRnEe/wWZ1/ExzBb+CZNx3jheDfm8ULGpprnYcM43xDOObyjN/NS
Zx1nL/eVDI6LQa8IlcNIYR/E5I6yDDYwQXoGF5n5mrm0kx3Uqo3PbkE7TwmGmRP+
ld/NMZWHrE5tK5hZ7rvaF392feP6H4ORj68nWCSJhrOZ/BUeTNibwm+c3YDyH7tD
R3EAYUkE+Uek+tb47tdpJfstOzAHwlKDMFXT67LSygP4AQs2hdBSaF2NVWIy/Tbb
BNGw+qB/SqP+FYWTolKn/FuLdte1yfarZWIfQDLLVWUWF6QtDNct8iY4k/FlYxIw
Gfn85KMzciyPzjSWAVRQedAHQKl4Dvfmfxo8I4kSLo+Bn5sXCIaMOZL+xnJ9KK0P
rgE4ZH8TrkMVL+M0cypB
=cxg6
-----END PGP SIGNATURE-----
On 6/18/13 6:50 AM, Jerald A DeLong wrote:
>
>> The Florida coordinator said I should be good to go with this once I got the
>> assignment completed, is this not the case?
>
> This *not* at all what I told you and I have all the email I sent you.
> We can discuss further off the list.
To the list, It was a misunderstanding on my end, Jerry was correct on this.
Sorry for the confusion, didn't intend to ruffle any feathers.
The process here is a bit different than I'm use to, and I'm still learning
all the procedures of 44net. I'm excited to be a part of this, and it's got
me excited to be involved with high-speed radio again.
Brian's hit me up off list and we have ball rolling.
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
On 6/17/13 8:46 PM, Cory (NQ1E) wrote:
> 10 with permission and 10 announcements seen on the net (in addition to the
> /8). It's good that nobody is trying to do it without permission ;)
This actually brings up a good question, as some point this weekend I'll have
44.98.254.0/24 announced via BGP out of 12083.
The Florida coordinator said I should be good to go with this once I got the
assignment completed, is this not the case?
I'd be willing to put some hardware/bandwidth/colo towards an east coast
gateway for the 44net if we have an architecture that would work for
distributing our interconnection points.
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
bryan at bryanfields.net wrote:
>I'd ask, why only one gateway to 44/8? Why not setup some tunnel/peering
>points globally?
That is a plan. There just needs to be some folks to step forward to
make it happen.
Until recently, there wasn't a formal way to seek permission from ARDC
to have the high level BGP routing changed to support this.
I have been curious since ARDC announced that option, how many/which
local subnets are not being announced locally.
Maybe Brian Kantor can chime in on that.
Steve
Awesome, please send me the script. Ill have time tear into it this weekend.
As for hardware, I'll bet testing on a 2800 series with 1gb of ram.
Jason R Begley <jayray(a)digitalgoat.com> wrote:
>(Please trim inclusions from previous messages)
>_______________________________________________
>With regard to using Cisco routers for integration into the AMPRNET, if
>
>you are going to load full tunnels be ready to throw some descent
>hardware at the task. The first issue is the config length, you need
>config compression on and no less than a 2600 due to nvram size. The
>other issue is number of interfaces, you also need at least a 2600 to
>configure the number of tunnels needed to be fully meshed. I am
>currently running a 2651xm and it does an ok job. Let me know if you
>are
>interested in a script to convert the encap.txt into a loadable config.
>73,
>Jason KY9J
>_________________________________________
>44Net mailing list
>44Net(a)hamradio.ucsd.edu
>http://hamradio.ucsd.edu/mailman/listinfo/44net
>http://www.ampr.org/donate.html
--
Bryan Fields
727-409-1194
http://bryanfields.net
On 6/17/13 2:04 AM, kb9mwr(a)gmail.com wrote:
>
> Many gateway opperators only allow inbound 44-net IP addresses.
>
> Maintain a local route table alleviates bandwith issues at ucsd, and
> the single point of failure.
Thanks, this is good info. I think I can change the "munge" script to
generate a working 44/net config. Cisco/etc is going to need a tunnel
interface for each destination, but I think it will work.
Perhaps a template interface might be the best way.
I'll post my results back here.
I'd ask, why only one gateway to 44/8? Why not setup some tunnel/peering
points globally?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
Bryan,
I have some archived resources here:
http://www.qsl.net/kb9mwr//wapr/tcpip/index.html
---
But if I can reach all of 44/8 via ucsd via the internet, why bother with
tunnels in the first place?
--
Many gateway opperators only allow inbound 44-net IP addresses.
Maintain a local route table alleviates bandwith issues at ucsd, and
the single point of failure.
On 6/17/13 1:53 AM, C.J. Adams-Collier KF7BMP wrote:
> If you decided to go this way, you could use a perl script with Net::SSH
> to update the router's config. At least with IOS. I'm not familiar
> with JunOS.
Yea, I was thinking this. I have RANCID running on all the routers now, so
it's trivial to get it to push configs out once a day or so.
But if I can reach all of 44/8 via ucsd via the internet, why bother with
tunnels in the first place?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net