On Thursday, May 12, 2016 at 12:37:49 AM UTC+2, John Kettlekey wrote: > > Binding to a port is per IP address. > > Most of the time you bind to a port on all available IP addresses at once > and then you can't bind anything else to that port. > > But you can bind to a port on a specific IP and allow something else to > bind to the same port on a different IP. >
Agreed. > > Remember that local host (127.0.0.1) counts as a separate IP so even a > machine with just one real/public IP can end up with two things bound to a > port; one on the real/public IP and one on the localhost interface. > > From the netstat output it looks like something has bound to port 80 of > the real/public IP and the other process has bound to port 80 for every > remaining address (255.255.255.255) which will probably just be localhost. > > The thing that is bound to an IP in the netstat output is the production APE process (aped). This is correct. The other process (aped_staging) should bind to the other IP but binds to 255.255.. instead. And I wonder why... > -JK > > -- -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/ --- You received this message because you are subscribed to the Google Groups "APE Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
