Re: [coLinux-users] change in slirp behavior from 0.7.1 to 0.7.3 with udp forwarded ports

[Mike F. <vap...@gm...>]

On Sun, Jun 22, 2008 at 4:59 PM, Henry Nestler wrote:
> Mike Frysinger wrote:
>> On Sun, Jun 22, 2008 at 3:51 PM, Henry Nestler wrote:
>>> Mike Frysinger wrote:
>>>> 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 ?
>>> In Version 0.7.2 the builtin TFTP-server was disabled. This server was a
>>> host only server and opens files on the Windows side. This should have
>>> nothing to do with the redirections. I hope, that is not the problem here.
>>>
>>> I have build a slirp version with enabled builtin TFTP-server:
>>> http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080622-slirp/
>>>
>>> Please test this.
>>
>> doesnt seem to make a difference :(
>
> OK. That is very nice. So, I know, that this change was not the problem.
>
> The difference for coLinux 0.7.1 and 0.7.3 are very small. Mostly are
> fixups for compiler warnings.
>
> There exist an other interesting change between versions:
> http://colinux.svn.sourceforge.net/viewvc/colinux?view=rev&revision=574
>
> This sets the 10.0.2.2 as source for broardcasts. Perhaps somethin is
> wrong there? I will check it with netcat and tcpdump next times.

i'm building the devel branch now (./configure && make) so i can go
back through the versions

the easy test is to run `tcpdump` in colinux and then just connect
with netcat from another machine:
nc -u colinux 69 <<<"MOO"

a broken system will show the packet coming from 10.0.2.x rather than
the real host
-mike