Re: restrict implicit binding to interfaces

Allen Kistler wrote:

I think what he's asking is how he can control on what
addresses an app
listener opens a socket. Most apps open sockets on 0.0.0.0
(i.e., every
interface) by default. Some let you specify listening
addresses. He appears to want a way to designate some
interfaces as "restricted" and others as "not restricted" so
that apps open listeners on the "not restricted" interfaces by
default, but can open listeners on the "restricted" interfaces
if their configs specifically request it.

Yes, that's exactly what I want.

Wolfgang Draxinger
--
E-Mail address works, Jabber: hexarith@xxxxxxxxxx, ICQ: 134682867

.

Relevant Pages

  • Re: restrict implicit binding to interfaces
    ... Most apps open sockets on 0.0.0.0 ... Some let you specify listening ... that apps open listeners on the "not restricted" interfaces by ...
    (comp.os.linux.networking)
  • Re: restrict implicit binding to interfaces
    ...  Some let you specify listening addresses. ... others as "not restricted" so that apps open listeners on the "not ... restricted" interfaces by default, but can open listeners on the ...
    (comp.os.linux.networking)
  • Re: httpcfg delete iplisten -i 0.0.0.0 ?
    ... > Deleting 0.0.0.0 does NOT cause all IPListen addressed to be cleared. ... HTTP.SYS will continue to listen on those interfaces. ... I want to clear all the IP listeners in the easiest way ... I'd prefer not to parse the console output of httpcfg query ...
    (microsoft.public.inetserver.iis)
  • Re: MVC pattern
    ... > Listeners are interfaces to the Controller. ... You're right that listeners are interfaces. ... In MVC input and output are handled separately by two parts, ...
    (comp.lang.java.programmer)