Guys,
I basically had HILANT:: totally lose the plot because of these telnet botnets that are hitting port 23/tcp all over the place.
Have any of you guys been affected? I have a feeling as I?ve got a Finnish IP address I might be one of the Lucky Winners of Putin?s latest ragefest.
FYI, these scripts are smarter than the usual root/Administrator scripts - I logged in and there had been over 49,000 attempts to log in to the SYSTEM account?
Anyway, I?ve changed the NAT forwarding to another port (if you happen to use HILANT:: via Telnet it?s now at telnet://hilant.sampsa.com:2389.
Also, is renaming the SYSTEM account likely to break stuff? They seem to be targeting that specific username so I figured I?d change it to STALIN or something?
Sampsa
So I basically got another 8 IPs from my colo provider and I decided to set up a socat forwarding box.
Basically, socat will literally forward anything to anything.
So I?m going to try to set up my bridge (which currently has to deal with the fact that the HILANT WAN IP isn?t static) through it, if it works, anyone else who wants to connect through it is welcome to do so, I?ll allocate a port for you.
Sampsa
Guys,
I?m planning on running the Telnet Tetris Challenge again and I think one of you guys is hosting a TETRIS account in the US, if I recall correctly.
If not, any volunteers? I?ve got both the AXP and VAX binaries + login scripts etc, I just need someone in the US (because of ping times) to have a Telnet-accessible VMS box with a captive account for the tournament (15-NOV-2016 to 1-JAN-2017).
Thanks,
sampsa
On 2016-10-31 16:32, Paul.Koning at dell.com wrote:
>
>> On Oct 29, 2016, at 11:32 AM, Sampsa Laine <sampsa at mac.com> wrote:
>>
>> Johnny,
>>
>> Could you please add the following nodes to the node database:
>>
>> 8.200 TACO
>> 8.201 HIRAME
>> 8.202 INARI
>> 8.203 HAMACHI
>
> Ah, a sushi fan.... The usual rule is that node names are limited to 6 characters. I don't know if some implementations allow longer ones.
I didn't know there was some suhi called "TACO". :-)
Anyway, HAMACHI was truncated to HAMACH. There are no systems with any
other limit that I know of, and I doubt it would make sense to have some
have a different length. I suspect too much assumes that nodenames are
max 6 chars.
Johnny
Johnny,
Could you please add the following nodes to the node database:
8.200 TACO
8.201 HIRAME
8.202 INARI
8.203 HAMACHI
8.204 SUZUKI
8.205 EBISU
8.207 UNAGI
They are SIMH-VAX OpenVMS 7.3 running in a cluster called MOSHIX (8.199, already registered but you might want to change the node type to cluster alias).
The SIMH-VAX is running Ubuntu Server 16.04 LTS x86-64bit.
Cluster owner is Moishe Bar, location Houston, TX.
Thanks,
Sampsa
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
This release address some serious bugs and also address performance.
I strongly encourage people to upgrade to the latest version to get
these fixes, since they can otherwise cause system crashes.
Things that have been done since the last release:
ICMP:
- There was a bug that triggered for some specific ICMP error packets,
which cased stack corruption, and system crashes. This bug have been
around for a long time, but usually don't trigger, which is why it have
remained around for so long.
TCP:
- Reworked the timer code. Under some circumstances, the timers was not
restarted properly, which could cause longer timeouts of things than
there should be.
- Reworked how ACKs for packets are generated. TCP can delay sending
ACKs in some cases, to improve performance. The algorithm for this have
been improved to better interact with Nagle.
- Added new functionality, by which writes can add data in a pending
state, meaning it will not be sent immediately. This can improve
performance where Nagle is used, but it is known that several writes
will be done in short succession. (telnetd is now using this feature.)
- Added the ability to define the keepalive time for individual connetions.
- Correct retransmit timer on accept calls.
HTTP:
- Improve the handling of subprocesses for CGI scripts, to make it more
error proof.
- Stop defining the QUERY_STRING logical for CGI scripts, if no query
string exist.
SPOOF:
- Bugfix: The spoof handler could block the same address multiple times
under some circumstances.
TELNETD:
- Changed code to use pending data feature in TCP for better network
utilization.
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
The firewall for Mim have now been removed, so no need for the alternate
ports, but Mim is still listening to the alternate ports as well.
ftp: 10021
telnet: 10023
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Thu, Oct 27, 2016 at 11:26:22AM +0200, Johnny Billquist wrote:
>
> 100Gb/s to a 10Mb/s interface... Poor Magica... :-)
I think there is probably a 100GB -> 10GB -> 1GB -> 100MB ladder in
between :) So she will not have to feel ashamed.
/P
Hi
Since some of you use Johnnys bridge or connect to MIM or Magica I
though you wanted to know that Uppsala University is getting a network
upgrade and will flip the switch(es) on tonight at 19:00 and on the
31:st.
I'm told we shouldn't notice it due to redundant lines, but you never
know :)
If all goes well you should, at least part of the way, be able to telnet
to our old machines at a whopping 100GB/s
Cheers,
Pontus.
