public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Hansen <cygwin@mehconsulting.com>
To: cygwin@cygwin.com
Subject: Re: Problem or question on Cygwin XWin
Date: Tue, 15 Jun 2021 04:41:26 -0700	[thread overview]
Message-ID: <saa3l4$kdg$1@ciao.gmane.io> (raw)
In-Reply-To: <60C82C87.1080401@tlinx.org>

On 6/14/2021 9:28 PM, L A Walsh wrote:
> On 2021/06/14 17:30, Duncan Roe wrote:
>> On Mon, Jun 14, 2021 at 04:41:42PM -0700, L A Walsh wrote:
>>   
>>> There is a listen parameter on XWin, but the man page doesn't
>>> say what format to use for the listen parameter.
>>>
>>> I want to have it listen for tcp from a local net: 192.168.3.0.
>>>
>>> I started having problems with my cygwin X receiving
>>> network connections via TCP, locally (like 192.168.3.1 => 192.168.3.12).
>>>
>>> And was trying to figure out what the syntax was for specifying what
>>> net to have it listen on.
>>>
>>> Thanks!
>>>
>>>     
>> At least under Linux, 'man Xserver' gives the format "-listen trans-type" with
>> example "-listen tcp". You can '-[no]listen' to tcp, inet (i.e.IP4), inet6,
>> unix or local.
>>
>> Cheers ... Duncan.
>>   
> ---
>      Ah, suspected something similar. But I couldn't remember
> the linux syntax off hand to narrow down addresses....but
> since no incoming TCP connections are working on my Winbox rt. now,
> its a bit moot.  Looks like I get to re-install-upgrade Win...what
> fun!
> 
> 
>      Thanks
> 
> 

I found that in addition to adding "-listen tcp" to the XWin server, I had to
change the setting of "enable_xauth" to "0" in the /usr/bin/startxwin script.


      reply	other threads:[~2021-06-15 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 23:41 L A Walsh
2021-06-15  0:30 ` Duncan Roe
2021-06-15  4:28   ` L A Walsh
2021-06-15 11:41     ` Mark Hansen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='saa3l4$kdg$1@ciao.gmane.io' \
    --to=cygwin@mehconsulting.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).