Bug 9723

Summary:	-from local-address should default to local address according to routing table
Product:	xorg	Reporter:	Thomas Bettler <thomas.bettler>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED MOVED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	high	Keywords:	janitor
Version:	7.1 (2006.05)
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Thomas Bettler 2007-01-20 21:31:23 UTC

The behaviour of -from is unintuitive. It just delivers any address / hostname
that the computer is connected to. (Well maybe the primary)
This doesn't serve in cases of vpn tunnels, where the destination route passes 
trough the tunnel (routing table), but the connecting client delivers the public / 
outside address to the server, so the server reconnects to a different address using 
another route instead of the tunnel.

Therefore I propose:
leave the -from option to explicitly define an origin.
But change the default value of -from to reflect the origin according to the routing 
table (and the respective device).

Comment 1 Thomas Bettler 2007-01-20 21:33:10 UTC

Have a look for a nasty example:
http://bugs.kde.org/show_bug.cgi?id=139639

Comment 2 Daniel Stone 2007-02-27 01:35:52 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 3 chemtech 2013-03-26 07:49:23 UTC

Thomas Bettler,
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Or close this bug.

Comment 4 GitLab Migration User 2018-12-13 22:17:35 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/349.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.