> Yes, I'm now aware that there are nameservice problems
> and I'm working on it. It won't be fixed quickly because
> it requires manual intervention by several people in many
> different places around the globe, including the registries.
> Thanks all for bringing this to my attention.
> - Brian
Well, it appears that the originally envisioned problem (not all servers uptodate) has
been fixed. The 2nd problem (incorrect servers in org zone) is still open, but that
should affect only the lookup time. It probably explains why ampr.org lookups are
often so slow.
However, when I checked before there were only some servers that were at most 24h behind.
Maybe they synchronize only once per day.
Was that the "slave nameservers are not updating" issue that you were after?
Or was there another slave that had not been updating for a much longer time?
Generally, 24h out of date should not be that much of an issue. Of course, when it stopped
syncing completely that would be bad.
Rob
Hopefully this isn't too far off topic. I've just completed testing of
an OFDM modem using IP over DVB-T2. It uses an SDR transmitter and a
commercial DVB-T2 receiver to implement the RFC 4326 Unidirectional
Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an
MPEG-2 Transport Stream (TS). ULE is supported in the Linux kernel for
DVB receivers.
https://tools.ietf.org/html/rfc4326
It's a full-duplex modem capable of up to 50 Mbps (in both directions)
in an 8 MHz bandwidth. The current test bed consists of an Ettus B200
SDR transmitter, PCTV 292e DVB-T2 USB receiver, Kuhne down converters
for 13cm and 9cm, Microlab BK-26N diplexer and RFSpace TSA600 Vivaldi
antenna.
http://www.w6rz.net/IMG_0119.jpghttp://www.w6rz.net/traceroute.png
The transmitter is based on the DVB-T2 transmitter in GNU Radio and uses
this OOT module for the ULE protocol.
https://github.com/drmpeg/gr-ule
To reduce the latency, I've merged the DVB-T2 blocks to avoid having so
many buffers between blocks.
https://github.com/drmpeg/gr-dvbt2ll
Current test frequencies are 2305 and 3429 MHz with an 8 MHz bandwidth.
The bit-rate is 28.6 Mbps (symmetrical).
It's intended to replace commercial WiFi equipment for amateur WAN
interlinks.
Advantages:
1) Full-duplex. Adding power amplifiers, preamps, diplexers/duplexers is
easy.
2) Frequency agile. Can work on any band above 420 MHz. 70cm through 5cm
direct TX from the SDR and millimeter frequencies with an up-converter.
3) Bandwidth agile. 5, 6 ,7 and 8 MHz bandwidths.
4) May be legal on 70cm. Although I haven't implemented it yet, a small
portion of the bandwidth can be used to send a low-rate video stream
(for example, a still picture of your call sign for ID). This would
classify the emission as digital ATV, not data.
Disadvantages:
1) Latency is a bit high. It's currently 100 ms (200 ms round trip).
This is a function of buffering in GNU Radio and the USB 3.0 connection
to the SDR. An FPGA implementation of DVB-T2 and a different SDR
architecture could solve this.
2) Cost. It's difficult to compete with commercial WiFi equipment.
However, lower cost components can be used instead of the "Cadillac"
test bed I constructed. For example, a ADALM-PLUTO at $99 could be used
instead of the Ettus B200 for transmit. Two antennas instead of a
diplexer and lower cost down-converters than the Kuhne units.
3) Requires a Linux computer to run it. An Odroid XU4 may be adequate,
but I haven't tested it.
73,
Ron W6RZ
It's come to my attention that some of our worldwide slave nameservers are
not updating when changes are made to the DNS on our master
nameserver, 'ampr.org' (44.0.0.1).
It will take me a while to contact the operators of those nameservers
to ensure that their configurations are correct for them to get the
latest changes as they occur.
In the meantime, there may be differences in the answers you get
regarding new entries in the DNS depending on which nameserver your
query is actually made to.
The way to tell if a particular nameserver is current is to examine
the serial number in the ampr.org SOA record as retrieved from it
and compare that with the SOA from ampr.org (44.0.0.1). I use the
'dig' tool for this purpose; there are other tools as well.
- Brian
Hi all
thanks for testing ping 44.177.10.254.
I apologize re 44.177.10.254 node callsign. It's OK0NMG.
For Brian: ok0nmg.ampr.org (or maybe gw.ok0nmg.ampr.org)
was registered for 44.177.10.254 in ampr.org DNS some monthes ago, maybe
years. But disappeared.
It was registered by OK2OP (Czech coordinator) who
unfortunately passed away and there is no Czech callsign
coordinator up to now. I asked Chris who is listed in amprnet
coordinators for Czech rep. but he says he is not able
to provide DNS registering.
For Peter ZL2BAU: Peter 44.177.10.10 is not changed and I do
not know why it is impossible to ping it from your system.
It can be pinged from N1URO, VE2PKT, VK6HGR and others.
Re 44.177.10.254 - it is node OK0NMG:CZGATE. I am sysop of
it as well. It is of different net then 44.177.10.10.
For Tom SP2L: Thanks for test/reply.
73
Dalibor
Hello,
I've just provisioned with a 44.182.24.0/24 subnet.I have a DD-WRT box on TP-Link TL-WDR3600 and a Ubiquiti NanoStation Loco M2.I want to interconnect with somebody via VPN for the moment. I am located in Romania and i have a static public IP from ISP.
Can you please provide me a little help?
Thank you in advance!
Sent from my Samsung Galaxy smartphone.
Does anyone have a valid current email address for
Hank Magnuski, KA6M (one of packet radio's pioneers)?
The only address I have for him is decades old and
doesn't work anymore.
Thank you.
- Brian
Background: HPWREN is the High Performance Wireless Research and
Education Network, implemented using commercial wireless equipment
and housed on several mountaintops around southern California USA.
A recent news item from them has some impressive images that you
folks may find interesting. You'll need a high-performance web
browser/viewer and network connection to get the most from it.
- Brian
----- Forwarded message
Subject: What does it look like being on a mountain top engulfed by fire?
A new HPWREN update:
What does it look like being on a mountain top engulfed by fire?
is available at http://hpwren.ucsd.edu/news/20170815/ The article,
contributed by Paul Bourke, shows an immersive time-lapse animation of
a four-camera 360 degree view in high resolution of the Whittier Fire
near Santa Barbara in July 2017, projected onto the inside of a sphere,
within which a viewer can pan, tilt and zoom.
Older HPWREN news updates can be found at http://hpwren.ucsd.edu/news/
----- End forwarded message -----
Ok, I've updated his email address in the portal to that address
from the on4sax(a)on4sax.be address that it used to be, which has
apparently been taken over by a domain parking service which does
not deliver mail. We'll see if this address gets through.
Thank you, Jan.
- Brian
On Mon, Aug 14, 2017 at 08:20:11AM +0200, Jan Poppeliers wrote:
> robbie.delise(a)gmail.com
>
> 73, Jan
> ON7UX
>
>
> -----Oorspronkelijk bericht-----
> Van: 44Net [mailto:44net-bounces+jan.poppeliers=online.be@hamradio.ucsd.edu]
> Namens Brian Kantor
> Verzonden: maandag 14 augustus 2017 7:25
> Aan: 44net(a)hamradio.ucsd.edu
> Onderwerp: [44net] Belgium AMPRNet coordination
>
> Unless someone can supply me with a working email address for the Belgium
> AMPRNet coordinator, Robbie De Lise ON4SAX, there won't be any more
> allocations in the existing Belgium subnet because there is nobody to handle
> them. I need a mailbox that is actually read and responded to, not just one
> that doesn't bounce mail sent to it. Or if it's the case that he's turned
> coordination over to someone else, I wish someone would let me know.
> - Brian
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
>
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
Unless someone can supply me with a working email address for the Belgium
AMPRNet coordinator, Robbie De Lise ON4SAX, there won't be any more
allocations in the existing Belgium subnet because there is nobody to
handle them. I need a mailbox that is actually read and responded to,
not just one that doesn't bounce mail sent to it. Or if it's the case
that he's turned coordination over to someone else, I wish someone
would let me know.
- Brian