To make it clearer, ASSP cannot bind to 0.0.0.0 and [::] at the sametime despite other services being able to. Is this an issue with the OS or the perl code?
Keep this example in mind. Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1486/rpcbind tcp6 0 0 :::111 :::* LISTEN 1486/rpcbind udp 0 0 0.0.0.0:111 0.0.0.0:* 1486/rpcbind udp6 0 0 :::111 :::* 1486/rpcbind You can see NFS rpcbind running on 0.0.0.0 TCP and UDP, also on [::] TCP6 and UDP6. That one service is listening on 4 wildcards. This is presently IMPOSSIBLE with ASSP due to some bug/limitation in IO::Socket::INET6. The operating system DOES NOT have such a limit or will prevent such. It is how ever the IO::Socket::INET6 module is coded, how it brings up the wildcard interfaces, it confuses itself and generates the error "Address already in use". When coded properly a port can be opened on both IPv4 and IPv6 wildcards for TCP and UDP. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
