rlogin fails on package name

[suki]

Hi,
I have 2 servers named host1(MC/SG) and host2(Standalone). Host1 is running with a package named pkg1.
The .rhosts file of host2 is having the package name pkg1 and the username.
When I try to do an rlogin from host1 to host2.It is asking for the password.
But after I login into host2 from host1 through telnet and I issue the command 'who -u'
It shows host1 is connected which is the hostname.For my scenario it should show the package name then only my rlogin will work.
Can someone help me to overcome this problem?
-Suki

[Bruno Vidal]

Hi
No it is the correct behavior. For security reason, the IP stack is showing always the IP of the host, not the IP of the package. So if you want use .rhost you should put both system name in it. Idem for firewalls. This behavior has been asked by customer to HP in order to avoid security pb.

Bye.

[suki]

Hi Bruno Vidal,
Thanks for your info.
Is it the fact, that package ip cannot be used to initiate an rcp,rlogin process Since every packet goes out from the host has the address of the hostname ?
-Suki

[Bruno Vidal]

Sorry, I don't understand very well your question. But if it is: can I detect from another system from which package I come from, the answer is no, it is not possible. You can still initiate rcp/rlogin, but from the point of the target system you are coming from host1 not from pkg1. I hope this help.

[Bruno Vidal]

Btw, an information about rcp/rlogin with MC/SG. If you are doing an r* command from the pkg on the same host (in your case: rlogin host1), because you don't go out of the system itself, the source IP seen by the system is the pkg IP (strange no :-).

Cheers.

[Stephen Doud]

Hello Suki,

I checked with our networking specialists on this issue and got two responses:

1. For supported techniques of binding to the relocable IP, refer to the "Managing MC/ServiceGuard" manual http://docs.hp.com/hpux/onlinedocs/B3936-90065/B3936-90065.html
section titled "Designing Applications to Run on Multiple Systems" and this document:
User Doc ID: KBAN00000700
ServiceGuard TCP/UDP Application Binding and Routing

2. There's a convoluted workaround (unsupported) of using a host route. It only works if
A) the clients are on the same subnet as the package, or
B) the routers can support proxy arp.

The package start script adds a route to the destination using the package IP as the gateway with a metric of 0. The package "stop" has to remove it.

Since this latter method is not supported, HP does not offer a document to describe the process, nor would HP support such a configuration.

-s.