17 Sep
2015
17 Sep
'15
12:36 a.m.
Quick fix though a bit ugly.. Shutdown the telnet daemon for a few seconds then restart
it. Ugly but effective and EASY!
-Steve
Sent from my iPhone
On Sep 16, 2015, at 10:07, Johnny Billquist <bqt at
softjar.se> wrote:
On 2015-09-16 16:03, Sampsa Laine wrote:
Well, you are trying to suggest ways to prevent this from happening. And no, VMS do not
have iptables, as far as I know.
When you are looking for is essentially a way to block some ranges of addresses. That can
be done in a router, or sometimes switch. Quite possible I'll look into that. But that
don't answer my current question, how to fix the current state on the VMS system. And
no, I do not consider "reboot" to be the solution. :-)
On 16 Sep 2015, at 15:01, Johnny Billquist
<bqt at softjar.se> wrote:
But this would also require that I have a separate network for this setup. We're
talking about a machine that are on the internet today... On a well known, static ip
address.
Then you're unfortunately pretty out of luck unless - AFAIK VMS doesn't have
anything like iptables to help you filter out the connections. A really crappy solution would be to restart the
IP stack every so often but there are of course issues with that as well..
Yeah... No... Not going there.
Johnny