binding xdm to a single ethernet interface

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.

any suggestion?

thanks
Jose

.

Relevant Pages

  • Re: binding xdm to a single ethernet interface
    ... 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 ... However it appears that after the the remote x-server queries the ... either of the nics. ...
    (comp.os.linux.x)
  • Re: Virtual LAN Problem
    ... > connectivity with the remote LAN and from the remote LAN. ... It collapsed after trying to allow it to have a remote DNS address ... Confirm a decent tunnel by pinging the remote site internal clients. ... > But I had full access to the files shares on the SBS box! ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual LAN Problem
    ... Gateway device and MANUAL DNS settings to get it to work. ... connectivity with the remote LAN and from the remote LAN. ... Confirm a decent tunnel by pinging the remote site internal clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Multiple Locations
    ... You asked why I joined the remote clients to the SBS domain. ... how can they connect to the Exchange server ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003, Outlook 2003, VPN Connection Issues
    ... I would take the path of testing an Outlook Client with RPC over HTTPs from the remote location to your main office thus bypassing the VPN entirely or have the user connect to using a VPN client from the remote location. ... What I am trying to suggest is bypassing your dedicated VPN between the sites and go straight through Internet Interface of your Router to see if you have the same issue with the Outlook Clients. ...
    (microsoft.public.exchange.admin)