kern/147756: [libc] open_socket_in: Protocol not supported -
after a few days?
Kirill A Sarksyan
dot at kkursor.ru
Wed Aug 11 11:00:18 UTC 2010
The following reply was made to PR kern/147756; it has been noted by GNATS.
From: Kirill A Sarksyan <dot at kkursor.ru>
To: Martin Minkus <martin.minkus at pulseutilities.co.nz>
Cc: bug-followup <bug-followup at FreeBSD.org>
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported -
after a few days?
Date: Wed, 11 Aug 2010 14:51:18 +0400
--=-80mZ6+GDI4EpBIO08kxX
Content-Type: multipart/alternative; boundary="=-Cd5wzKAum3n+wEjSPCOI"
--=-Cd5wzKAum3n+wEjSPCOI
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
I know that it's not a good idea, though I want samba open over the
entire Internets. Anonymous default user from teh Internets can do
nothing, folders become available for authenticated users. I know about
vulnerabilities, etc. :)
In previous versions of Samba no interfaces directive was required and
Samba listened all interfaces by default. Maybe this behaviour has
changed in 3.4.
I discovered a work-around. I will probably use FTP for storing backups
from two office sites to my home server instead of SMB. Though Windoze
likes SMB more than FTP.
Thank you. :)
Ð ÐÑÑ, 10/08/2010 в 09:41 +1200, Martin Minkus пиÑеÑ:
> 1) yes, you can specify what interfaces and what subnets it will allow
> connections from in smb.conf. Checking those settings will allow you
> to do what you want.
>
> 2) However, you do not want samba open and accepting connections from
> the entire internet....... thatâs bad. Set up a VPN using openvpn or
> whatever to allow outside samba access to just those persons or sites
> that need it.
>
>
>
> Martin.
>
>
>
>
> From: Kirill A Sarksyan [mailto:dot at kkursor.ru]
> Sent: Tuesday, 10 August 2010 09:32
> To: Martin Minkus
> Cc: bug-followup
> Subject: RE: kern/147756: [libc] open_socket_in: Protocol not
> supported - after a few days?
>
>
>
>
>
> Strange. The computer I speak about works as my home server (including
> WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.
> I found a strange thing - Samba correctly works from inside of home
> network, but fails to work from the Internet. I will re-read
> configuration how-to, maybe there is some differencies between old
> Samba and the new one, because of which new Samba does not listen
> globally available network interfaces.
>
> Ð ÐÑÑ, 10/08/2010 в 09:23 +1200, Martin Minkus пиÑеÑ:
>
> In my case it was bad hardware. Seemed to be the PCI bus, so probably
> the southbridge.
>
>
>
> Anything using PCIe was completely unaffected, and mem tests running
> for days passed fine.
>
>
>
> Traffic going over the pci bus, even the onboard nic would silently
> get corrupted.
>
>
>
> Moved the hardware onto a new motherboard and all the issues magically
> disappeared.....
>
>
>
>
> From: Kirill A Sarksyan [mailto:dot at kkursor.ru]
> Sent: Tuesday, 10 August 2010 00:35
> To: bug-followup at FreeBSD.org; Martin Minkus
> Subject: Re: kern/147756: [libc] open_socket_in: Protocol not
> supported - after a few days?
>
>
>
>
>
> I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47
> MSD 2010.
> On start Samba log contains:
> [2010/08/09 16:19:04, 1] smbd/files.c:177(file_init)
> file_init: Information only: requested 16384 open files,
> 7014 are available.
> [2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)
> open_socket_in(): socket() call failed: Protocol not
> supported
> [2010/08/09 16:19:04, 0]
> smbd/server.c:457(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Protocol not
> supported
> [2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)
> open_socket_in(): socket() call failed: Protocol not
> supported
> [2010/08/09 16:19:04, 0]
> smbd/server.c:457(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Protocol not
> supported
>
> %pkg_info | grep samba
> samba34-3.4.8 A free SMB and CIFS client and server for
> UNIX
>
> And Windows clients cannot use Samba shares at all.
>
>
>
>
>
>
>
>
>
>
--=-Cd5wzKAum3n+wEjSPCOI
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY LINK="#0000ff">
I know that it's not a good idea, though I want samba open over the entire Internets. Anonymous default user from teh Internets can do nothing, folders become available for authenticated users. I know about vulnerabilities, etc. <IMG SRC="cid:1281523741.2195.14.camel at notebook" ALIGN="middle" ALT=":)" BORDER="0"><BR>
In previous versions of Samba no interfaces directive was required and Samba listened all interfaces by default. Maybe this behaviour has changed in 3.4.<BR>
I discovered a work-around. I will probably use FTP for storing backups from two office sites to my home server instead of SMB. Though Windoze likes SMB more than FTP. <BR>
Thank you. <IMG SRC="cid:1281523741.2195.14.camel at notebook" ALIGN="middle" ALT=":)" BORDER="0"><BR>
<BR>
<BR>
В Втр, 10/08/2010 в 09:41 +1200, Martin Minkus пишет:
<BLOCKQUOTE TYPE=CITE>
1) yes, you can specify what interfaces and what subnets it will allow connections from in smb.conf. Checking those settings will allow you to do what you want.<BR>
<BR>
2) However, you do not want samba open and accepting connections from the entire internet....... that’s bad. Set up a VPN using openvpn or whatever to allow outside samba access to just those persons or sites that need it.<BR>
<BR>
<BR>
<BR>
Martin.<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<B>From:</B> Kirill A Sarksyan [mailto:dot at kkursor.ru] <BR>
<B>Sent:</B> Tuesday, 10 August 2010 09:32<BR>
<B>To:</B> Martin Minkus<BR>
<B>Cc:</B> bug-followup<BR>
<B>Subject:</B> RE: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
Strange. The computer I speak about works as my home server (including WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.<BR>
I found a strange thing - Samba correctly works from inside of home network, but fails to work from the Internet. I will re-read configuration how-to, maybe there is some differencies between old Samba and the new one, because of which new Samba does not listen globally available network interfaces.<BR>
<BR>
В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет: <BR>
<BR>
In my case it was bad hardware. Seemed to be the PCI bus, so probably the southbridge.<BR>
<BR>
<BR>
<BR>
Anything using PCIe was completely unaffected, and mem tests running for days passed fine.<BR>
<BR>
<BR>
<BR>
Traffic going over the pci bus, even the onboard nic would silently get corrupted.<BR>
<BR>
<BR>
<BR>
Moved the hardware onto a new motherboard and all the issues magically disappeared.....<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE>
<B>From:</B> Kirill A Sarksyan [mailto:dot at kkursor.ru] <BR>
<B>Sent:</B> Tuesday, 10 August 2010 00:35<BR>
<B>To:</B> bug-followup at FreeBSD.org; Martin Minkus<BR>
<B>Subject:</B> Re: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD 2010.<BR>
On start Samba log contains:<BR>
[2010/08/09 16:19:04, 1] smbd/files.c:177(file_init)<BR>
file_init: Information only: requested 16384 open files, 7014 are available.<BR>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<BR>
open_socket_in(): socket() call failed: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<BR>
smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<BR>
open_socket_in(): socket() call failed: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<BR>
smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
<BR>
%pkg_info | grep samba<BR>
samba34-3.4.8 A free SMB and CIFS client and server for UNIX<BR>
<BR>
And Windows clients cannot use Samba shares at all.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>
--=-Cd5wzKAum3n+wEjSPCOI--
--=-80mZ6+GDI4EpBIO08kxX
Content-ID: <1281523741.2195.14.camel at notebook>
Content-Disposition: attachment; filename="face-smile.png"
Content-Type: image/png; name="face-smile.png"
Content-Transfer-Encoding: base64
iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAAB3RJ
TUUH1wgOER8RqU5d7gAAAwtJREFUOI1lk01oXGUYhZ/73Ts/sWPiT8YE2ti6SF00jDWBaBWLuhFB
QgUNQsFdCair2pVSBV3YGkNWDVjcqKlIaG2sLf5EUBqTBkqjTFMi2Px2ojOTpJnMZHLnfvd+3+si
VKR5V2dxOBx4z+Nw1419QZty3R5EdYmJmgEcpfIgF6zYT59+nan/+5074sYQ8XIQG/ASjYdbDxyP
px58Rql4M0hIFMxQKf5sb149pY1eOdOQ4I193ej/AoaGcFt07PKufUc6dmY+ShBOI+FfQAB4ID5C
CieeYWHy3SA/c/FaLsHB7m4MABNfxfpvTfb4YkpiNi+K1X+K2EDEhiKmIhIVxNauil55R6LNUZkZ
e96fGKQfwBn7jN3xhqZsx8tT9aInUYlOTvSeYrlYoK/3fcRWOdk7wHJxiY8/eBZdPo/X8BZ/XHql
HG5UM0olvaOtT7yXIprF8fYALmfPfcPwt5dANNgyZ8+PMPzdOJh/wOQx/ii7M6+mSHJU4ahDqfRz
SqJ5cGIgNR5t3Uv7/gxifbDr7H0kxeNtOxB9A3Aw/jip9EHlCIc8G0VNKpZGdBGiHOI+xODnJ0FC
xK6AKfDl6ZcgmkOiRcBg9QLJB1qwliYPAIkQKUM4DbYETt1WfSmDWQa7BraKNTXEBohoQADwHNct
mGD+YSUKMXkc8cFJbhlsFbFrYFYRW8KaDazxQaUJ/XmUoqAEM1wufG/xdkK0xOTICW4v/YKuTmP0
AjbMEdYWWc3Pcv1KFmMquHWdVJYvW3EY3nrjvfdl27t+qpfKaW5X2slN9VEtLWEiDYDredxT38iu
treJywB16Q/J/nikHG5UM1tDGlT9c1de9CN/XMK1T8TUrok1ayJWi9hAbLQqYXVUqn+/KUHpa5n5
7anNO0PyABbj9pi9+UOniNPR8tjxRLgxgvF/xeg5xAY4bhq37gDejhe4db2vVpwb/z2X4Ng2mNZr
DLjx+w/v2f9aPNX4pIolW0AsoT9LZWXCLmTPaaPXzzQk74JpG84OPQJdWJoBUOQduGCFbTj/C8H3
uN+XWOgHAAAAAElFTkSuQmCC
--=-80mZ6+GDI4EpBIO08kxX--
More information about the freebsd-bugs
mailing list