Re: binding xdm to a single ethernet interface
- From: Emmanual Kann <kann@xxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 21:06:30 GMT
An Wed, 08 Mar 2006 11:44:25 -0800, barros.jos hat geschreibt:
Hi
I have a m/c with dual ethernet interfaces running suse 9.2 pro and
want to ensure that xdm communicates with other remote clients only via
a single (first) ethernet interface as i'm running other services bound
to the second nic . Initially I thought it was just a problem of
configuring the correct iptables rules for blocking all except the
required ports (exept xdmcp) on the second nic while for the first nic
i just kept it open on all ports.
However it appears that after the the remote x-server queries the
correct (first) interface, xdm communicates back to the clients on
either of the nics. Thus sometimes my remote session would hang midway
thought the kde initailisation while sometime it would'nt even start.
From what info i've found so far it seems that this sort of behaviour
should be configured in the Xaccess file in /usr/X11R6/lib/xdm (for
suse) . However just how I cannot determine as all examples i've come
across so far give examples for specifying which clients can get a
login session.
Some x-servers allow you to do a direct xcmp request to the nic you
want, or you can set up the XDM to LISTEN only on the desired nic.
any suggestion?
Yes use LISTEN in the Xaccess file:
LISTEN 10.11.12.13 # assuming this is the nic you want to use.
thanks
Jose
If you still have problems with the return packets coming back through the
wrong interface, you will have to do some fancy routing using iproute2 or
plain static routing with route.
.
- References:
- binding xdm to a single ethernet interface
- From: barros . jos
- binding xdm to a single ethernet interface
- Prev by Date: Re: start an application under X11
- Next by Date: Re: start an application under X11
- Previous by thread: binding xdm to a single ethernet interface
- Next by thread: Run X client with ssh tunnel after su
- Index(es):
Relevant Pages
|
