Re: Listening on specific interfaces

[Chip Seraphine]

Are we talking about the same thing here?  Or am I misunderstanding the 
whole conversation?

--
$ man -S 2 bind

NAME
       bind - bind a name to a socket

SYNOPSIS
       #include <sys/types.h>
       #include <sys/socket.h>

       int bind(int sockfd, struct sockaddr *my_addr, socklen_t addrlen);

DESCRIPTION
       bind  gives  the  socket  sockfd the local address my_addr.


--

Mark Burgess wrote:
> On 26 Aug, Reenen Kroukamp wrote:
>
> > When allowing a server to bind to an IP you can ensure a specific
> > source address/interface for packets coming from cfservd.
> >
> > On Mon, Aug 25, 2003 at 06:26:51PM +0200, Mark.Burgess@iu.hio.no wrote:
> >
> > > Cfservd already has this kind of access control. You don't need
> > > any more layers, I would say.
> > >
> > > M
> >
> > ...
>
>
>
> I'm not sure, but I suspect that there is a general misunderstanding
> here. When a server binds to an address, it binds to an address that
> it is *listening for traffic from*, not the address that it claims
> to be itself.
>
> Servers generally bind to 0.0.0.0 whih means, I'm accepting traffic
> from anyone in principle.