From: Mike F. <vap...@gm...> - 2008-06-15 06:43:46
|
On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote: > for some reason, the incoming packets from the tftp client as seen by > colinux have the gateway's ip (10.0.2.2) instead of the real ip > (192.168.0.17) ... any hints as to what's going wrong here ? > > taking a step back and just hitting colinux with netcat shows the same > behavior. connecting to a tcp forwarded port and things look good > (the source ip is the real client, not the gateway). connecting to a > udp forwarded port and things look bad (the source ip is the gateway > instead of the real client). i noticed that there's a standalone exe called 'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from 0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP forwarded ports started working again ... guess it's a bug in the slirp daemon ? -mike |