From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 9 21:50:03 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79FF0106564A for ; Mon, 9 Aug 2010 21:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5CC9C8FC12 for ; Mon, 9 Aug 2010 21:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o79Lo3YD082218 for ; Mon, 9 Aug 2010 21:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o79Lo3eY082217; Mon, 9 Aug 2010 21:50:03 GMT (envelope-from gnats) Date: Mon, 9 Aug 2010 21:50:03 GMT Message-Id: <201008092150.o79Lo3eY082217@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Martin Minkus Cc: Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Minkus List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2010 21:50:03 -0000 The following reply was made to PR kern/147756; it has been noted by GNATS. From: Martin Minkus To: dot Cc: bug-followup 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@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@kkursor.ru]=20 Sent: Tuesday, 10 August 2010 00:35 To: bug-followup@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

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.

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.

 

Martin.

 

From: Kirill A Sarksyan [mailto:dot@kkursor= =2Eru]
Sent: Tuesday, 10 August 2010 09:32
To: Martin Minkus
Cc: bug-followup
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supp= orted - 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 Sam= ba 3.4.
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.

В Втр, 10/08/2010 в 09:23 +1200, Martin Min= kus пишет:

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 d= ays 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@kkursor.ru]
Sent: Tuesday, 10 August 2010 00:35
To: bug-followup@FreeBSD.org; Martin Minkus
Subject: Re: kern/147756: [libc] open_socket_in: Protocol not supp= orted - after a few days?

 

I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47 MSD 2= 010.
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 cli= ent and server for UNIX

And Windows clients cannot use Samba shares at all.



 

--2_0_2fd_b54f96MHTML_=_01--