From: Henry N. <Hen...@Ar...> - 2008-01-23 22:45:25
|
Frédéric L. W. Meunier wrote: > I don't know what caused it, but now everything works. I > changed it to > > eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080 > > and it works if I use in 80 or 8080. This confiused me! ;-( If you not have a server on port 8080 on coLinux (Linux) side, you should no have a positive response from port 8080 on Windows side. Or, you found a bug. Plesase send me your used colinux config file or batch script and say, what distri you use. > But if I recall correctly, when it didn't work, dhcpcd had set > my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything > it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer > 10.0.2.15. IP 10.0.2.16 is not ok for DHCP. Have you more about the DHCP protocoll from /var/log/message with typicaly OFFER/ACK/NAK messages? Sems me, we have the bug with badly DHCP offers not fixed. Only 10.0.2.15 is the right address. The DHCP-Server inside slirp should give only this one address all times. You can set the working config as static to have no problems in future. -- Henry N. |