For some reason list switched to send me digests. How can i switch back
to single messages? There is no info in digest email.
Pedja
YT9TP
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Just a heads up. I have had the Toronto, Ontario subnet 44.135.88.0/24
subnet dark for a few years
now and plan to get it back online in a few weeks. For those in the
GTA, Bob, etc .. please drop me
a private email so I can coordinate bringing the Toronto AMPRnet GW back
online.
Michael Durrant
ve3pnx(a)andier.com
www.packetradio.ca
The IP address 44.140.63.5 just tried multiple ssh attempts using invalid
logins against six of our 44-net machines. The attempts were caught and
blocked. But beware.
Is there an abuse policy and, if so, what is it?
Michael
N6MEF
Hi Brian,
My name is Remi F6CNB and I am in charge of developing the HAMNET network in
France BUT I am not the IP address coordinator.
The subnets are distributed by the coordinator outside the portail. I am
using the hamnetdb.net to keep track of them. There are more than 50 sites
currently active on the network. The network is growing fast in the Paris
area with a lot of high speed backbones (typically 10 to 70Mbps). A lot of
additional isolated subnets are existing in France including the very remote
La Reunion island. They all are connected to the Paris area network thru gre
tunnels.
The main usages of the network are:
VOIP,
DMR/STAR repeater links,
DATV repeater,
Webcam,
APRS
......
I got a script from our german hamnet friends to automatically update by
email the main 44.0.0.0 DNS server from hamnetdb.net. I need to adapt it to
handle the 44.168.0.0/16 network. Could you send me a description of the
current way to update the DNS server by email and give me the privilege to
do it?
We also have a lot of issues with the current portail like I cannot assign
44.168.0.0/16 to my main ipip gateway (200Mbps connection both way) or the
DNS registration not working. That is probably the main reason of poor DNS
update.
73 Remi F6CNB (also W5/F6CNB 50% of the time)
The method is there. It's just almost hidden.
When you click "Database", you will see only data from 2011 and newer.
While looking at the right-side frame, each entry has an "update" option.
Look closely at the very first one, and just above the word "update" you
will see the word "New"
Click "New" to add your entry.
When you enter your data, the website will then attempt to use your
computers default email program to submit a new entry via email.
Depending on your email program, it may or may not try to warn you that
another device is attempting to use your email program to send data somewhere.
Cheers Peter.
Bill Lewis / KG6BAJ
At 04:03 PM 2/9/2016, you wrote:
>(Please trim inclusions from previous messages)
>_______________________________________________
>Hi All,
>
> Sorry for my off topic question, I shall be brief.
>
>Does anyone know where or how to update the listing on
>
>http://www.ampr-gates.net/frame_e.htm
Hi All,
Sorry for my off topic question, I shall be brief.
Does anyone know where or how to update the listing on
http://www.ampr-gates.net/frame_e.htm
Is there another site ?
Regards ..... Peter ZL2BAU
Hello Brian,
French Hamnet works fine on 44.151 subnet like you can see.
This is the historic network, no problem on it.
REF association ask for a new 44.168 subnet for their project.
For 44.168 subnet, contact the coord F1TZV at f1tzv(a)evc.net
I read the Hamlist of REF association http://ref-union.net/Hamnet/
and there is nothing since fews months. I just write a message on this
list
in order to know what happend. If i have a answer, i will put it here.
Best regards,
Ludovic - F5PBG.
Le 09/02/2016 20:00, 44net-request(a)hamradio.ucsd.edu a écrit :
> Message: 5
> Date: Tue, 9 Feb 2016 08:21:33 -0800
> From: Brian Kantor<Brian(a)UCSD.Edu>
> To:44net@hamradio.ucsd.edu
> Subject: [44net] HAMNet France
> Message-ID:<20160209162133.GA14859(a)UCSD.Edu>
> Content-Type: text/plain; charset=us-ascii
>
> Can anyone advise me of the status of the French HAMNet project?
>
> I've not heard anything from those folks in over a year, and the
> coordinator for 44.168.0.0/16 hasn't logged into the portal since
> May of 2015.
> - Brian
Can anyone advise me of the status of the French HAMNet project?
I've not heard anything from those folks in over a year, and the
coordinator for 44.168.0.0/16 hasn't logged into the portal since
May of 2015.
- Brian
> Why does an hostname of an isolated system need to be resolved in a world
> wide DNS?
> It has no connection to the internet via the gw or to the tunnelling system,
> so that DNS resolution will allways lead to an unreachable host.
Because there really is no relation between IP allocation and routing.
For example, back in the days when we ran a lowspeed IP packet network here and in surrounding
countries (1987-2003 or thereabouts), it was strictly forbidden in the regulations to have
a connection between a radio station and a public communication line.
We had thousands of stations active but none reachable from internet.
hostfiles were used instead of DNS, but the information in the hostsfiles was always
replicated to the public DNS, to indicate what addresses are allocated to whom.
Also, it would have been possible (had the software on the typical station supported it) to
download a zonefile and use it offline.
Now that we have linking over- and to internet, we are in fact still doing that.
Our gateway downloads the zonefile from hamradio.ucsd.edu daily, and loads it in a local DNS
server on 44-net, only reachable from the radio side.
So even when we lose our internet connection, we can still resolve .ampr.org addresses as
they were valid just before the breakdown.
I don't think that "reachable from the internet" or "reachable from net-44 systems that tunnel
over internet" should be a criterion for being in the .ampr.org DNS.
(this does not even consider that there may be firewalls that make it impossible to detect for
outsiders that a system is connected, while the system itself can perfectly make outgoing connections)
Rob
> If you look in the file that Brian posted you will see that there are no
> 44.137.X.X (or 44.130.X.X) records in the list to be deleted.
> So your DNS records should be okay.
I know that, and that is why I am taking up the job myself.
(I think it is a bit strange that the networks that are BGP or IPIP routed would not have
to be cleaned)
Rob
