-=> mark lewis wrote to Allen Prunty <=-

 ml> you cannot bind to an address that is on another device (eg: your
 ml> router)... you can only bind to addresses assigned to and active on
 ml> your device... just let it bind to all of your active interfaces by
 ml> using 0.0.0.0 and then the port
 ml>  forwarding in your router thing can send the traffic to your device
 ml> and thus to your mystic installation...

Unless you have a specific reason to bind a specific IP address, 0.0.0.0 is the
best bet.  The main reasons to bind to a specific IP are:

1.  You only want to listen on one of the attached networks (mosy typically a
service intended for a LAN that's on a host that has an interface on a public
IP).

or

2.  You need to bind the same ports on another IP (e.g. BBS listens on 23 for
outside users, another process listens on 23 on a LAN IP), or you're running 2
different BBSs on different IPs, and want to use the same port on both.


... We are the very model of cartoon individuals.
--- MultiMail/Win32 v0.49