Re: [coLinux-users] Strange SLIRP behaviour

[Henry N. <hen...@ar...>]

Marek Jawurek wrote:
> I had coLinux successfully set up at home using SLIRP but at a different
> site I am having problems:
> 
> I can DNS out but my TCP SYN packets are reseted and do not leave my
> machiene.

Remember: Slirp only supports TCP connections and UDP packets. No other
protocols, no IMCP packets.

> In my coLinux configuration file I have set up eth0=slirp
> In my Linux system I obtained network settings via dhcp and verified
> them against the static configuration in the manual. Then I try to wget
> a website via: wget http://heise.de
> 
> With wireshark I analysed the packets going out on eth0:
> There I first have the DNS request and reply going from my 10.0.2.15
> address to 10.0.2.3 and back.
> Then the TCP SYN packets go out to the PROXY set up for HTTP ( 10.0.2.15
> to the PROXY address) but an RST comes back ( PROXY -> 10.0.2.15).

Proxy setup? Perhaps Slirp does handle proxy wrong? Works it without proxy?

> On the windows side I have wireshark running on my Physical Ethernet
> Adapter. There the DNS request goes out and comes back ( WindowsIP ->
> DNS) and ( DNS -> WindowsIP).
> But then there is no TCP Syn Packet leaving my Windows Host.
> 
> The Windows Firewall is disabled globally. I tried to run the colinux debugger but it does not show the actual packets
> sent/received just memory addresses. Is there a way to see what colinux receives and resends in the debugger ?

Run TCPdump or process-Explorer from http://www.sysinternals.com
(forwarded to MS) to see what packets the slirp daemon on windows send
and received.

-- 
Henry N.