Operating System - OpenVMS
1748285 Members
3784 Online
108761 Solutions
New Discussion

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

 
SOLVED
Go to solution
Steven Schweda
Honored Contributor

-TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

Has the problem shown below improved since:

ALP $ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 4
on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3

?

ALP $ tcpip set comm /reject = host = 1.2.3.4.5
%TCPIP-E-INETERROR, internet interface error
-TCPIP-E-INVQUAL, invalid qualifier value for /REJECT.HOSTS
-TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****






And then it hangs until Ctrl/C.
10 REPLIES 10
John Gillings
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

Steven,

Depends on your definition of "improved" ;-)

$ tcpip show version

HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6 - ECO 3
on an HP BL860c (1.67GHz/9.0MB) running OpenVMS V8.3-1H1

$ tcpip set comm /reject = host = 1.2.3.4.5
%TCPIP-E-INETERROR, internet interface error
-TCPIP-E-INVQUAL, invalid qualifier value for /REJECT.HOSTS
-TCPIP-E-INVADR, invalid internet address: x¶à z¸}ÿx¶à z¸}:~~à i+<~ÿ****\~H

But it doesn't hang...
A crucible of informative mistakes
Steven Schweda
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

> HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6 - ECO 3
> on an HP BL860c (1.67GHz/9.0MB) running OpenVMS V8.3-1H1

Well, that's a start (and it is one ECO
beyond what I have so far on my IA64
systems), but I was really hoping for
something on some edition of 8.4.

I'm just trying to determine whether it's
worth another fight with the Web form to see
if a complaint from a non-paying-peon will
get anywhere these days. (Or if anyone in
a position to do anything is paying any
attention to this place.)
Steven Schweda
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

Yet another IA64 ECO seems to matter little:

IT $ tcpip show version

HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6 - ECO 4
on an HP zx2000 (1.50GHz/6.0MB) running OpenVMS V8.3-1H1

IT $ tcpip set comm /reje = host = 1.2.3.4.5
%TCPIP-E-INETERROR, internet interface error
-TCPIP-E-INVQUAL, invalid qualifier value for /REJECT.HOSTS
-TCPIP-E-INVADR, invalid internet address: xà à z¸}ÿxà à z¸}:~~à i+<~ÿ****\~H
IT $

At least on the IA64 system it doesn't hang
the way it does on the Alpha.
labadie_1
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

On Alpha VMS 7.3-2 and
HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6

it displays the same rubbish, but it does not hang.

I guess VMS Engineering does not use a fuzzer to do some testing, because this and many other small (or not) problems would have been detected.
It is a pity, because a lot of companies use them to find bugs.

http://en.wikipedia.org/wiki/Fuzz_testing

http://lwn.net/Articles/322826/
Volker Halle
Honored Contributor
Solution

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

Steven,

CHAALP-E8.4 $ tcpip sho vers

HP TCP/IP Services for OpenVMS Alpha Version T5.7
on a DEC 3000 Model 400 running OpenVMS E8.4

CHAALP-E8.4 $ tcpip set comm /reje = host = 1.2.3.4.5
%TCPIP-E-INETERROR, internet interface error
-TCPIP-E-INVQUAL, invalid qualifier value for /REJECT.HOSTS
-TCPIP-E-INVADR, invalid internet address: à âzà ¬ÿà âzà ¬:*(­ÿ(­ôw\­ÿ****|­H
CHAALP-E8.4 $

At least it does not hang...

As it's still there in T5.7, I'll raise a (low priority) PTR.

Volker.
Steven Schweda
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

> As it's still there in T5.7, I'll raise a
> (low priority) PTR.

Ok. Thanks. I'll just hold my breath.


Not to change the subject, but while you're
at it, if there's a way to stop the SSH
server from translating some IP addresses to
names in the security audit log file, I'd
love to hear about it. I keep getting stuff
like this:

Security alarm (SECURITY) and security audit (SECURITY) on ALP, system id: 1119
Auditable event: Network login failure
Event time: 20-JAN-2010 04:19:41.99
PID: 202055EE
Process name: TCPIP$S_BG49876
Username: TCPIP$SSH
Remote node fullname: SSH_PASSWORD:NS6.LEEUWENHARTHOSTING.NET
Remote username: ROOT(LOCAL)
Status: %LOGIN-F-NOTVALID, user authorization failure

and, sometimes, when I get around to looking
up the name, it's impossible to determine the
IP address from the name. (_Please_ don't
help me so much.)

ALP $ tcpip show service /full ssh

Service: SSH
State: Enabled
Port: 22 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: TCPIP$SSH Process: TCPIP$SSH
Limit: 64 Active: 0 Peak: 64

File: TCPIP$SYSTEM:TCPIP$SSH_RUN.COM
Flags: Listen

Socket Opts: Keepalive Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: TCPIP$SSH_DEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG

Note: "Log Opts: [...] Addr". It doesn't
help, despite what the HELP says:

SET

SERVICE

/LOG_OPTIONS
[...]
[NO]ADDRESS For auxiliary server messages and OpenVMS
security events, the message displays the
IP address as a host name. If host names are
not relevant, HP recommends that you specify
[NO]ADDRESS.

Or should I specify NOADDRESS if I really
want only the address? "HP recommends that
you specify [NO]ADDRESS."? Who writes this
dreck? Could anything be less clear?

Well, it was still TCPIP-related.
Volker Halle
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

Steven,

here is the PTR number for reference:

75-123-82

Volker.
Peter Weaver_1
Frequent Advisor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

> Remote node fullname: SSH_PASSWORD:NS6.LEEUWENHARTHOSTING.NET
> Remote username: ROOT(LOCAL)

Just to follow up on your changed subject.

You must have an account on your VMS system named ROOT. If the hacker hit another account that is not in your SYSUAF then you would have seen

Remote username: SSH_455E869C

You can translate the 455E869C into a IP address with a little DCL code;

$ type prw_utl:convert_32bit_ipaddress_to_dotted.com
$!
$! Translate decimal IP address (32-bit) into dotted octets.
$!
$! > Auditable event: Network breakin detection
$! > Event time: 8-APR-2007 23:13:19.86
$! > PID: 2160541C
$! > Process name: TCPIP$FTPC00002
$! > Username: admin2
$! > Remote nodename: hn.kd.dhcp
$! > Remote node id: 1026966587
$! > Remote username: FTP_3D36443B
$! > Status: %LOGIN-F-NOSUCHUSER, no such user
$!
$! @prw_utl:CONVERT_32BIT_IPADDRESS_TO_DOTTED 1026966587
$!
$! OR
$!
$! @prw_utl:CONVERT_32BIT_IPADDRESS_TO_DOTTED %X3D36443B
$!
$!
$ hexip=f$fao("!XL", f$integer(p1))
$ a=%X'f$extract(0,2,hexip)
$ b=%X'f$extract(2,2,hexip)
$ c=%X'f$extract(4,2,hexip)
$ d=%X'f$extract(6,2,hexip)
$ write sys$output "''p1' converts to the IP address: ''f$fao("!ZB.!ZB.!ZB.!ZB",a,b,c,d)'"
$!
$ @prw_utl:convert_32bit_ipaddress_to_dotted %X455E869C
%X455E869C converts to the IP address: 69.94.134.156


Steven Schweda
Honored Contributor

Re: -TCPIP-E-INVADR, invalid internet address: ÀòÜzhÿÀòÜzh:*¸ÿ¸$yìÿ****

> You must have an account on your VMS
> system named ROOT. [...]

Guilty as charged. (Saves precious
keystrokes when using FTP (as "root") from a
UNIX(-like) system.)

> If the hacker [...]

Sadly, I can't rely on the hacker's
cooperation in a case like this.

> You can translate [...]

I can, _if_ there's anything to translate.
But I'd want to check the case of some ATT
address (12.x.y.z) to see if I get a leading
zero in the hexadecimal thing. Everything's
(potentially) complicated.