Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Jul 2020 18:48:24 +0200
From:      Michael Tuexen <tuexen@freebsd.org>
To:        "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>
Cc:        Ian Lepore <ian@freebsd.org>, "bergerkos@yahoo.co.uk" <bergerkos@yahoo.co.uk>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Re: ? ????? ??: vnc can't connect to socket
Message-ID:  <9D2DC5CD-5003-4142-A0AA-B2F8B354C488@freebsd.org>
In-Reply-To: <3E06883E-BAB1-4E1A-AB20-06DD1F812057@freebsd.org>
References:  <202006212112.05LLCKQR006977@gndrsh.dnsmgr.net> <3E06883E-BAB1-4E1A-AB20-06DD1F812057@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> On 22. Jun 2020, at 15:55, Michael Tuexen <tuexen@FreeBSD.org> wrote:
>=20
>> On 21. Jun 2020, at 23:12, Rodney W. Grimes =
<freebsd-rwg@gndrsh.dnsmgr.net> wrote:
>>=20
>>>> On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
>>>>>> On 21. Jun 2020, at 14:28, Kostya Berger <bergerkos@yahoo.co.uk>
>>>>>> wrote:
>>>>>>=20
>>>>>> Ok, it turns out, it gives the previously mentioned error only if =
I
>>>>>> use VNC server string 0.0.0.0:5900 (as I always did). in my VNC
>>>>>> client.But when replaced with127.0.0.1:5900it connects all right.
>>>>>=20
>>>>> I don't hink 0.0.0.0 is a valid destination address you can use in
>>>>> connect(). Using 127.0.0.1 should
>>>>> be fine.
>>>=20
>>> I do not believe that this is a destination address when your =
talking
>>> about 0.0.0.0:5900 on the VNC server side, that is a wild card =
accept
>>> any address and if this has been broken.. it must be fixed!
>>>=20
>>>>> I guess, https://svnweb.freebsd.org/changeset/base/361752 is the
>>>>> relevant commit here.
>>>>>=20
>>>>=20
>>>> *BSD has always accepted 0 as a synonym for localhost (and iirc, =
linux
>>>> does not).  If this no longer works, it's a regression which is =
going
>>>> to cause existing applications and scripts to fail.  At the very =
least
>>>> it deserves an entry in UPDATING.
>>>=20
>>> I am not aware of that, but can not deny it either, and just =
confirmed
>>> it to be true:
>>> root {1002}# telnet 0.0.0.0 22
>>> Trying 0.0.0.0...
>>> Connected to 0.0.0.0.
>>> Escape character is '^]'.
>>> SSH-2.0-OpenSSH_7.8 FreeBSD-20180909
>>=20
>> And to add the netstat data to show what connected:
>> tcp4       0      0 127.0.0.1.22           127.0.0.1.43135        =
ESTABLISHED
>> tcp4      38      0 127.0.0.1.43135        127.0.0.1.22           =
ESTABLISHED
>>=20
>> Can we back this commit out, discuss it in next weeks call,
>> and then find a way forward?
>>=20
>>>=20
>>> INADDR_ANY is the wildcard listen address, but as a destination what =
code remapped
>>> it to 127.0.0.1?
>>>=20
>>> We should very seriously consider restoring this behavior.
> Reallowing 0.0.0.0 is covered by https://reviews.freebsd.org/D25401
Fixed in https://svnweb.freebsd.org/changeset/base/363256

Best regards
Michael
>=20
> Best regards
> Michael
>>>=20
>>>> -- Ian
>>>>=20
>>>>> Best regards
>>>>> Michael
>>>>>> ?????????? ?? Yahoo ????? ??? Android=20
>>>>>>=20
>>>>>> ??, 21 ???. 2020 ? 9:40 Kostya Berger<bergerkos@yahoo.co.uk>
>>>>>> ???????(-?):   Hi,upgraded to 362292 via buildworld.Now I cannot
>>>>>> connect to my bhyve guest as I used to: neither via VNC nor via
>>>>>> RDP.VNC gets error: unable to connect the socket. Address family
>>>>>> not supported by protocol family (47).
>>>>>> Neither can I ping my bhyve IP (it uses a separate NIC and should
>>>>>> have no problems)
>>>>>> Internet connectivity is ok and I can ping other hosts on my
>>>>>> network.
>>>>>> In 359997 all works fine.
>>>>>> ?????????? ?? Yahoo ????? ??? Android =20
>>>>>> _______________________________________________
>>>>>> freebsd-current@freebsd.org mailing list
>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>>>> To unsubscribe, send any mail to "
>>>>>> freebsd-current-unsubscribe@freebsd.org"
>>>>>=20
>>>>> _______________________________________________
>>>>> freebsd-current@freebsd.org mailing list
>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>>> To unsubscribe, send any mail to "
>>>>> freebsd-current-unsubscribe@freebsd.org"
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> freebsd-current@freebsd.org mailing list
>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
>>>>=20
>>>>=20
>>>=20
>>> --=20
>>> Rod Grimes                                                 =
rgrimes@freebsd.org
>>> _______________________________________________
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
>>>=20
>>=20
>> --=20
>> Rod Grimes                                                 =
rgrimes@freebsd.org
>=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D2DC5CD-5003-4142-A0AA-B2F8B354C488>