Chris Ruvolo <[EMAIL PROTECTED]> wrote:
>
> In specific, the X server is behind the masq (on the private network)
> and the X client (the machine running the apps) is out on the
> internet.
This is the problem. An X client opens a connection to the X server.
Since the X server is behind a firewall, it cannot be reached without
help from the firewall.
> Is there a ruleset I can use to allow the X data to be transported?
You can use ipportfw to forward the X port (6000) through the firewall,
to the private-LAN X server. You will need to tell your X client to use
a DISPLAY which matches the external IP address of the masq-firewall
(essentially, pretending that the X server is running on the firewall).
I have done this successfully; it works very well. If you have multiple
X servers behind the firewall, you can forward a different port to each
one of them (6000 -> server_A, 6001 -> server_B), and then use different
DISPLAY numbers (firewall:0, firewall:1) to reach the proper X server.
Easy. :)
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
