kern/147756: [libc] open_socket_in: Protocol not supported -
after a few days?
Martin Minkus
martin.minkus at pulseutilities.co.nz
Mon Aug 9 21:50:03 UTC 2010
The following reply was made to PR kern/147756; it has been noted by GNATS.
From: Martin Minkus <martin.minkus at pulseutilities.co.nz>
To: dot <dot at kkursor.ru>
Cc: bug-followup <bug-followup at FreeBSD.org>
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after
a few days?
Date: Tue, 10 Aug 2010 09:41:38 +1200
--2_0_2fd_b54f96MHTML_=_01
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=E2=80=99s bad. Set up a VPN using openvpn=
or
whatever to allow outside samba access to just those persons or sites
that need it.
=C2=A0
Martin.
=C2=A0
From: Kirill A Sarksyan [mailto:dot at kkursor.ru]=20
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?
=C2=A0
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.
=D0=92 =D0=92=D1=82=D1=80, 10/08/2010 =D0=B2 09:23 +1200, Martin Minkus =D0=
=BF=D0=B8=D1=88=D0=B5=D1=82:=20
In my case it was bad hardware. Seemed to be the PCI bus, so probably
the southbridge.
=C2=A0
Anything using PCIe was completely unaffected, and mem tests running for
days passed fine.
=C2=A0
Traffic going over the pci bus, even the onboard nic would silently get
corrupted.
=C2=A0
Moved the hardware onto a new motherboard and all the issues magically
disappeared.....
=C2=A0
From: Kirill A Sarksyan [mailto:dot at kkursor.ru]=20
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?
=20
=20
=C2=A0
=20
I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul=C2=A0 1 01:27:47 MS=
D
2010.
On start Samba log contains:
[2010/08/09 16:19:04,=C2=A0 1] smbd/files.c:177(file_init)
=C2=A0 file_init: Information only: requested 16384 open files, 7014 a=
re
available.
[2010/08/09 16:19:04,=C2=A0 0] lib/util_sock.c:902(open_socket_in)
=C2=A0 open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04,=C2=A0 0] smbd/server.c:457(smbd_open_one_socket)=
=C2=A0 smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/08/09 16:19:04,=C2=A0 0] lib/util_sock.c:902(open_socket_in)
=C2=A0 open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04,=C2=A0 0] smbd/server.c:457(smbd_open_one_socket)=
=C2=A0 smbd_open_once_socket: open_socket_in: Protocol not supported
=20
%pkg_info | grep samba
samba34-3.4.8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A free SMB and CIFS c=
lient and server for UNIX
=20
And Windows clients cannot use Samba shares at all.
=20
=20
=20
=20
=C2=A0
--2_0_2fd_b54f96MHTML_=_01
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
"http://www.w3.org/TR/REC-html40">
<head>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
=2EMsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-NZ link=3Dblue vlink=3Dpurple>
<div class=3DWordSection1>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>1) yes, you can specify what interfaces and what subnets i=
t will
allow connections from in smb.conf. Checking those settings will allow yo=
u to
do what you want.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>2) However, you do not want samba open and accepting conne=
ctions
from the entire internet....... that’s bad. Set up a VPN using open=
vpn or
whatever to allow outside samba access to just those persons or sites tha=
t need
it.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>Martin.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<div>
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
m 0cm 0cm'>
<p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font=
-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-s=
ize:10.0pt;
font-family:"Tahoma","sans-serif"'> Kirill A Sarksyan [mailto:dot at kkursor=
=2Eru] <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 supp=
orted
- after a few days?<o:p></o:p></span>
</p>
</div>
</div>
<p class=3DMsoNormal><o:p> </o:p>
</p>
<p class=3DMsoNormal>Strange. The computer I speak about works as my home=
server
(including WWW- and Mail) for 2 years, I never had any issues, except Sam=
ba
3.4.<br>
I found a strange thing - Samba correctly works from inside of home netwo=
rk,
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 w=
hich
new Samba does not listen globally available network interfaces.<br>
<br>
В Втр, 10/08/2010 в 09:23 +1200, Martin Min=
kus
пишет: <o:p></o:p>
</p>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>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 d=
ays
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>
<o:p></o:p>
</p>
<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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 supp=
orted
- after a few days?<br>
<br>
<o:p></o:p>
</p>
</blockquote>
<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'> <br>
<br>
I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD 2=
010.<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 cli=
ent
and server for UNIX<br>
<br>
And Windows clients cannot use Samba shares at all.<br>
<br>
<br>
<br>
<o:p></o:p>
</p>
</blockquote>
<p class=3DMsoNormal><o:p> </o:p>
</p>
</div>
</body>
</html>
--2_0_2fd_b54f96MHTML_=_01--
More information about the freebsd-bugs
mailing list