On Thu, 2008-05-29 at 06:08 +1000, Tim Lyth wrote: > tcp6 is not spurious.
Netstat is somewhat confused about these things. On my system, I get: tcp 0 0 :::25 :::* LISTEN 1092/couriertcpd Addresses are still in v6 format but the daemon is listening on both v4 and v6 sockets. There seem to be issues. See http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/f6c65fec92ea7f13/ab14a2c1e49b7ce6 > If you look at the IP address columns, you'll notice that they're in > IPv6 format - tcp6 is the same. > But the connections from the outside world, as well as from within the > LAN, are IPv4 connections - it all just works and the netstat output > is just a matter of default formatting within in IPv6 capable > environment. My server kernel and tools are likewise v6 capable, as is Courier. Is it possible that Jan's Courier is listening _only_ on a v6 socket and not on a v4 socket? This isn't clear from the netstat output. -- Lindsay Haisley | "In an open world, | PGP public key FMP Computer Services | who needs Windows | available at 512-259-1190 | or Gates" | http://pubkeys.fmp.com http://www.fmp.com | | ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
