!!! URG !! rx2660 - HP-UX v3 Server setting (156 Views)
Reply
Frequent Advisor
Neoma
Posts: 78
Registered: ‎11-06-2007
Message 1 of 4 (156 Views)
Accepted Solution

!!! URG !! rx2660 - HP-UX v3 Server setting

Hi Guys,

I have rx2660 server with HP-UXv3 OS running over it.

There are two network cards names lan0 and lan1.

lan0 is assigned IP with 192.168.0.2 and
lan1 with 10.1.1.5

I have Xming server running on my PC.
Whenever I open a first ssh session(with x forwarding on) with this server DISPLAY is set to 10.1.1.5:11.0
and I am able to open ovw screens.

For the 2nd ssh session DISPLAY is set to 10.1.1.5:12.0 (please note display number is increased by 1)

for 3rd it is DISPLAY=10.1.1.5:13.0 and so on.

and I am able to start multiple X window applications.

I want to do the same setting on my 2nd rx2660 Server which has lan0 assigned IP with 192.168.0.4 and lan1 with 10.1.1.7.

Can anyone please help me with providing the changes so that 2nd one also sets the display to 10.1.1.7:11.0 , 10.1.1.7:12.0 and so on.

PS: It is not done in .profile for sure on my 1st server.
Honored Contributor
Honored Contributor
Jov
Posts: 1,574
Registered: ‎01-12-2000
Message 2 of 4 (156 Views)

Re: !!! URG !! rx2660 - HP-UX v3 Server setting

Hi,

Firstly, the question you're asking should be under the HP-UX forum.

What you're descibing is an ssh daemon configuration. Uncomment the line 'X11DisplayOffset 10' in /opt/ssh/etc/sshd_config. Add it if it's not there.


Jov
Frequent Advisor
Neoma
Posts: 78
Registered: ‎11-06-2007
Message 3 of 4 (156 Views)

Re: !!! URG !! rx2660 - HP-UX v3 Server setting

Thanx Jov for the quick reply.

I will surely try that.

Can you please let me know if I need to change some configuration file to have DISPLAY set to lan1 interface always for each and every ssh session?
Honored Contributor
Honored Contributor
Jov
Posts: 1,574
Registered: ‎01-12-2000
Message 4 of 4 (156 Views)

Re: !!! URG !! rx2660 - HP-UX v3 Server setting

Hi,

The display setting is set on your X Server application.

If yousing ssh it will be inherited from the sshe shell.

Its not wise to lock to to an interface as that can block traffic destined to the other.


Jov
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.