Although the AMPR web portal is still under development, it would be
very helpful if all the AMPR IP Address Coordinators were to please
connect to <https://portal.ampr.org/> and register their login and password.
In this way we can get the coordinator contact information updated.
Thank you.
- Brian
I just unplugged my jnos see if it stopped..
----- Original Message -----
From: 44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu <44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu>
To: 44net(a)hamradio.ucsd.edu <44net(a)hamradio.ucsd.edu>
Sent: Sun Oct 14 07:08:45 2012
Subject: [44net] Fwd: nuisance proto 94 ipip OSPFv2
(Please trim inclusions from previous messages)
_______________________________________________
Anyone else getting this from 99.119.146.20? It's not a huge amount of
bandwidth here, but it's a multicast of some type, and it comes from
that ip with a 44-net address encapped in it...resolved to a k9
something....been constantly hitting me at about 40-50 packets per
minute....
I've set my router to silently drop them for now....
Cheers,
John
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
Hi Chris,
my name is Marco and I'm Ampr Coordinator for Italy: 44.134.0.0/16.
Please, can you allocate this range to me ?
And...
please can you also add these Gateways to my account ?
Account name: iw2ohx
Gateways:
Title 83.211.73.103
Gateway IP 83.211.73.103
Subnet 44.134.160.0 / 24
Subnet 44.134.166.0 / 24
Subnet 44.134.167.128 / 25
Subnet 44.134.168.0 / 24
-
Title 91.121.90.186
Gateway IP 91.121.90.186
Subnet 44.134.0.0 / 20
Subnet 44.134.128.0 / 20
Subnet 44.134.144.0 / 22
Subnet 44.134.173.0 / 24
Subnet 44.134.174.0 / 23
Many thanks,
Marco
iw2ohx
On 10/09/2012 10:45 AM, Chris Smith wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Another point I should mention concerning the new portal and Gateways robot:
>
> All of the current Gateway data has been imported into the new system. This means that if you already have a gateway registered on the current system, it will be present on the new system, so there is no need to add it.
>
> The downside to this, is that if you register on the portal to manage your gateway, it will not simply "appear" on your account. This is because it is already present on a default account.
>
> The solution is to contact me with your gateway details (Username as registered on the portal, Gateway IP and Subnets serviced) and I will transfer it across to your account.
>
> Thanks,
> Chris
> G1FEF
>
>
>
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
>
--
---
Marco Di Martino
Via Attimo, 18 - Bollate (MI)
Mobile: +393285373364
e-mail:iw2ohx@iw2ohx.net
-
Amateur Radio: I W 2 O H X
Homepage Inet:www.iw2ohx.net
Homepage Ampr: iw2ohx.ampr.orgLinuxNode:telnet://iw2ohx.ampr.org/
(X)net:telnet://iw2ohx-2.ampr.org/
Packet Mail : IW2OHX @ IW2OHX.ILOM.ITA.EU
Ampr Mail:iw2ohx@iw2ohx.ampr.org
---
Please note that the DNS functionality on the new portal is not live yet, any DNS update requests will be silently discarded by the system.
It is planned that this functionality will be available quite soon, at which time an announcement will be made on this mailing list.
Thanks,
Chris
G1FEF
There have been a few enquiries regarding how to retrieve the encap.txt and gateways file from the new system:
You can use FTP by connecting to the host: portal.ampr.org
The username and password is the same as the old system (please drop me an email if you don't know it).
Once you have created an account on the portal, if you click on the top menu link "Gateways" then click on "Options" on the second menu line a page is displayed where you can enter an email address and select the frequency you wish to receive the encap.txt file. From that point on it will be emailed to the address you have entered. If the email address field is blank, you will NOT be emailed the encap.txt file.
If you click on "List" from the "Gateways" menu, you can also download the latest encap.txt file from the link at the top of this page.
The download link on the "List" page is "live" data, i.e. if someone updates their gateways entry, it will appear in the database immediately and so the moment you browse to that page, or refresh that page, you have the very latest data. The file on the FTP site is updated only when a change occurs, there is a cronjob that polls the database every 5 minutes and updates the file if anything changed, so the FTP file will at worst be 5 minutes out of date.
With regards to the "gateways" file that was available on the old system: we did not believe that this file was very useful as all the data it contained is now on the portal. However, there have been a few people ask about it. If this file is being used, then let me know and I can put work in to create the file on the FTP site. If it's not important then don't bother contacting me and I won;t spend the time on it ;-)
73,
Chris
G1FEF
Many thanks to everyone involved in the amprnet facelift/update.
I don't know if all of this will stay the same, but I just recently
documented the experimental gateway that I built.
http://www.qsl.net/kb9mwr/wapr/tcpip/rip44d.html
In poking around on www.ampr.org, I have to say I am in awe of what
the European hams are doing to build RF networks.
I know there are also some pretty talented microwave design amateurs
over there from reading Dubus and some of the RSGB books.
I am wondering if anyone has designed homebrew amplifiers for any of
the WLAN gear? Feel free to contact me off list.
73'
Steve, KB9MWR
It does not it act: ftp://ftp.ampr-gateways.org/
Did I overlook something ???
--
73 de Janusz / SP1LOP
===== Janusz J. Przybylski, SP1LOP ==================
Poland AmprNet Co-ordinator [44.165/16] from: 03.2003
=====================================================
i get the updates vy email and this is the last one i got on 10/02/2012
encap.txt,v 1.816 2012/10/02 05:02:01 gateways Exp $
#
On 10/06/12, Janusz Przybylski SP1LOP <44net(a)mail.sp1lop.ampr.org> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> It does not it act: ftp://ftp.ampr-gateways.org/
> Did I overlook something ???
>
> --
>
> 73 de Janusz / SP1LOP
> ===== Janusz J. Przybylski, SP1LOP ==================
> Poland AmprNet Co-ordinator [44.165/16] from: 03.2003
> =====================================================
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
>
>
Hi,
Thanks for writing this program and your support.
Turns out I had the wrong netmask on my tunnel interface.
Seems to be working now.
73'
Steve, KB9MWR
Not all that long ago I installed the new rip44d on a CentOS install.
It did receive the broadcasts as I saw them in debug mode. However it
didn't seem to install these routes to the local routing table.
I assume that has to with networking working slightly different on the
various flavor of Linux.
So now I am trying with Ubuntu 10.04 server, but I can't even seem to
receive the broadcasts. It just sits there in the main loop waiting
for broadcasts. Yet when I watch with tcpdump, there are things going
on. But I am mostly concerned by the udp port unreachable that I am
responding with:
(For now) I have the Linux firewall completely disabled (as far as I
know... more of a RedHat guy) and connected directly to the outside
world.
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
13:30:00.337401 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.337442 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.337454 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.337606 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.337624 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.337632 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.337976 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.338000 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.338008 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.338015 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.338026 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.339133 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
I am looking for tips on what I am doing wrong, or what distribution
and steps those who are doing this had success with.
Thanks,
Steve, KB9MWR