From: SourceForge.net <no...@so...> - 2006-09-02 18:30:55
|
Bugs item #1247417, was opened at 2005-07-29 07:29 Message generated for change (Comment added) made by gboutwel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1247417&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Later Priority: 5 Submitted By: Dr Bill C Riemers (docbill) Assigned to: Nobody/Anonymous (nobody) Summary: Slirp host address failures Initial Comment: When using addresses: 10.0.2.5/24 and 10.0.2.6/24 Slirp sockets timeout, and fail to connect. (ping of 10.0.2.2 does work) The address: 10.0.2.15/24 does work. All none reserved addresses of the format 10.0.2.X/24 should work... Bill ---------------------------------------------------------------------- >Comment By: George P Boutwell (gboutwel) Date: 2006-09-02 13:30 Message: Logged In: YES user_id=30412 Please submit this as a feature request. The software currently works as designed. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2005-10-07 12:29 Message: Logged In: YES user_id=579204 Only the IP 10.0.2.15 is reserved for colinux guest and "soft routed" inside the SLiRP to guest. The host known only the 15 as destination to the guest. It's static codes in source. Perhaps it can be a future request? The others: SLiRP can't ping to others as the gateway 10.0.2.2, it's not supported. Ping on Windows needs IMCP sockets, and SLiRP only supports simple TCP or UDP sockets. A ping to the world is implement as an UDP ECHO, but not all machines supports the echo on port 7/udp. So ping is not usable under SLiRP. Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1247417&group_id=98788 |