-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am running samba on a machine with 2 outside interfaces. I want samba to
listen only to one of them so I put these lines on smb.conf:
bind interfaces only = True
interfaces = 192.168.1.1 127.0.0.1
These setings produce this in netstat -a:
(...)
udp 0 0 192.168.1.1:138 0.0.0.0:*
udp 0 0 192.168.1.1:137 0.0.0.0:*
udp 0 0 0.0.0.0:138 0.0.0.0:*
udp 0 0 0.0.0.0:137 0.0.0.0:*
(...)
I was told this was because nmbd uses broadcast packets to do it's work and
for it to listen to broadcast packages it must listen to 0.0.0.0. Is this
true. Can't it bind to 192.168.1.0 instead?
How does linux's interface binding API work? Is this really necessary?
Greetings from Portugal,
Pedro.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE71GQ82SBo0jBmgGARAoODAJ9FxNU2C+Eu3mtx5b4TTZ8KB9K5KACg2IY4
MkH7qmx8c9qq1xwB26GmDR4=
=A+CG
-----END PGP SIGNATURE-----
This is correct behaviour for Samba. It's not a security issue, since Samba isn't listening in any useable sense to interfaces other than those you request. You'll get 'connection refused' if you try to contact another interface.
Nik
>>> Pedro Corte-Real <[email protected]> 10/22/01 02:23PM >>>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I am running samba on a machine with 2 outside interfaces. I want samba to
> listen only to one of them so I put these lines on smb.conf:
> bind interfaces only = True
> interfaces = 192.168.1.1 127.0.0.1
> These setings produce this in netstat -a:
> (...)
> udp 0 0 192.168.1.1:138 0.0.0.0:*
> udp 0 0 192.168.1.1:137 0.0.0.0:*
> udp 0 0 0.0.0.0:138 0.0.0.0:*
> udp 0 0 0.0.0.0:137 0.0.0.0:*
> (...)
> I was told this was because nmbd uses broadcast packets to do it's work and
> for it to listen to broadcast packages it must listen to 0.0.0.0. Is this
> true. Can't it bind to 192.168.1.0 instead?
> How does linux's interface binding API work? Is this really necessary?
> Greetings from Portugal,
> Pedro.