> Trumpet Winsock :-)
> I Installed Windows NT on my 386/40MHz (some 35 3.5 floppy disks) which
> barely run on it, but had the necessary dialup software just to download
> Trumpet Winsock to use it afterwards on Win 3.1 on the same machine
> (only some 15 disks to reinstall)...
> Later came Win 3.11 which had a TCP/IP + Internet explorer 3 addon which
> made Trumpet Winsock and Mozaic obsolete.
> That where times...
When I got access to "the Internet" (of course via dialup modem too) I already
had a running Linux system with native TCP/IP networking.
I installed that in december 1992 on a 486/33 MHz with 16MB RAM.
And a QIC cartridge tapedrive, so no messing with floppies.
The internet became available for the general public in 1993 here, I joined in 1994.
But of course I had been using TCP/IP since 1988 using KA9Q NET on the Atari ST.
Rob
> I just applied for a /24 out of 44.190/16, to help with this endeavor.
> I’ll be announcing the prefix out of a commercial datacenter in Fremont, CA under ASN 7247.
> 73,
> -jav k4jh
Jav is the first one to get his proxies/relays running as a result of this call.
He said "This was easy!".
Rob
> FYI folks...I used to run proxies on my subnet in the past. The only
> issue was, that since subnet is not not BGP, it was intended for your
> use only (i.e. not using AMPRGW for Internet, but still able to use
> EchoLink).
I agree it is probably not a good idea to run proxies or relays on a network
only connected via tunnels. That would pose a load on AMPRGW. In that case
it would be better to run them there. But other volunteers in that area have
now stepped up.
> I used the Java JAR that was available form EchoLink (I understand you
> have a C program). I also used the Linux version, but the EchoLink
> Validators stated that should not be used without permission (and only
> for conference servers).
The Java version uses lots of resources... The C program was written to
mimic the Java version closely but in a more efficient way, both because
it is in C and because a single instance can run multiple proxies.
Later I received the C source of the relay program from EchoLink and merged
its functions with the proxy program so these can both run on the same system.
This is in full agreement with EchoLink, and they very much welcome the
hosting of proxies and relays around the world to help users that are on
limited internet connections or are not proficient in configuring port
forwarding on their routers.
Fortunately in our circles we have people who understand the internet and
its protocols. (vs the applications that are now called "the internet")
Rob
> >/when the directory server is on AMPRnet, the problem with NAT between /> >/HAMNET and internet disappears /
> I'm afraid, it would raise new issues...
> For those who are planning to provide echolink proxy services (or any
> other useful internet based amateur radio services) within the AMPRNet
> by direct BGP, please ask for an /24-allocation within 44.190.0.0/16.
> We will promote to all HAMNET users and sysops to route 44.190.0.0/16 to
> their ISP rather than to their radio device on the roof.
> Best case would be to host such services on non-44 IP-space at all.
As you know, I don't agree with that. We should not segregate our addresses
into different classes and force everyone into some class depending on what
they want to do. It is a stopgap measure that will lead to endless changes
and work, and it isn't even clear what "internet based amateur radio services"
are exactly. For example, our repeaters are on Echolink on their AMPRnet address, they
would be such services, we would have to route part of that space deeply into our
network to get "special" addresses all the way there. Not going to happen!
At the moment I am in contact with the Jonathan from Echolink and he is interested
in setting up more relays as his existing relays in the US are getting overloaded.
(he has temporarily moved some US users to our relays in Amsterdam)
I think now that this is under change we could suggest moving everything to AMPRnet
and it should solve the NAT problem there is now. Maybe the directory server could
have both an AMPRnet and a public address to resolve remaining issues.
Rob
> "from the people who built it". Really? Gee, I don't remember any of those
> names back in the early 80s (except for Stallman, but Emacs is not the
> Internet).
I fully agree!
When I saw the list I immediately thought "those aren't the people who built the internet!"
Not even the world wide web. Maybe Web 2.0.
Hello All,
We’ve (HamWAN) become aware of a new vulnerability on the Mikrotik devices that could allow an attacker to grab passwords off of the devices. If you block WinBox access you should be safe, but I’d recommend upgrading as soon as possible as well.
More information about this vulnerability, as well as what versions are impacted, and what the patched version numbers are, are available from Mikrotik here: https://forum.mikrotik.com/viewtopic.php?f=21&t=133533 <https://forum.mikrotik.com/viewtopic.php?f=21&t=133533>
Thanks,
Nigel
> I found your C program in your follow up emails so seemed like I
> should have everything I need. Sorry for the confusion, initially I
> thought i needed to contact you for the C program.
It probably wasn't clear in my first message... there is no need to contact me to deploy Echolink PROXY
servers, the C program has been on my server for a long time (others are using it as well) and it can
be installed on AMPRnet or commercial IP addresses alike.
However, there are already quite some proxy servers and there is no immediate need for new ones, although
they are always welcome.
The call was mainly to get a number of new RELAY hosting sites, as there are currently not enough of them.
Running PROXY servers is a good way to get some experience using the program, making sure it is started
automatically and remains running, arranging for the extra addresses on the system (I do that using a
script that does "ip addr add 44.137.75.$i dev eth0" in a loop, but it can be handled via the native
network management of the distribution just as well. just don't create an extra interface for each)
Once that is all clear and comfortable, RELAY servers can be configured (about 10, but in such areas as
the US west coast maybe 5 is better as there are several volunteers now) and then you can contact me
or K1RFD with the IP addresses so that they are going to get registered so they are really used.
This is not required for PROXY servers, these register themselves automatically.
Rob
> I like to help with this as well. Please let me know the details on how to
> setup your C program.
I know I am a bad writer, but I'm afraid you have to do with what is already in the README
file and what I explained here on the list.
Note it isn't really a beginner project, it assumes you are familiar with running a Linux
system and compiling your own software on it.
As a baseline, you are supposed to know what to do when you find a .tar.gz file and seeing
that it contains a README, a .c file, a Makefile and an example configuration file.
When there are obvious omissions, I am willing to update the README.
Rob
