Bug 60649 - Replies to XDMCP query sent to wrong address, cause connection to fail
Summary: Replies to XDMCP query sent to wrong address, cause connection to fail
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.2
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-04 05:31 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-05 01:00:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-03-04 05:31:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
Replies to queries sent to wrong address

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Enable XDMCP on a RedHat machine (Standard steps: editing xdm-config, 
Xaccess, gdm.conf, kdmrc, etc) at address 192.168.1.10.
2.Install Cygwin/XFree86 under Windows 2000 at 192.168.1.1. 
3.These two machines are on the same subnet 192.168.1.x, sharing an Internet 
connection through a Windows 2000 Server at 192.168.1.100.
4.Launch XWin under Cygwin with the command "XWin -query 192.168.1.10 -from 
192.168.1.1
5. Use netstat -an to examine socket info on the RedHat 7.2 machine 
immediately. Notice that the RedHat 7.2 machine is sending UDP data to 
192.168.1.100, not 192.168.1.1 !!! 
	

Actual Results:  The XDMCP query fails. Although one can add route specifically 
on thr RedHat 7.2 machine to the machine that does the query and fix this 
problem, this just is not right.

Expected Results:  The RedHat 7.2 machine is supposed to send UDP data directly 
to the address of the machine that does the XDMCP query, not the gateway 
address !!!

Additional info:

Comment 1 Than Ngo 2002-03-04 12:19:41 UTC
aasign to XFree86

Comment 2 Mike A. Harris 2002-03-05 01:00:34 UTC
You might want to report this bug to XFree86.org also, so more eyes
are on it.

Comment 3 Mike A. Harris 2002-05-21 08:55:16 UTC
Just tested, and it works for me.  You must have some local configuration
issue.  Nobody else is reporting this problem.


Note You need to log in before you can comment on or make changes to this bug.