Re: [coLinux-users] unable to get slirp (ping) working

[Hari K. D. <har...@gm...>]

On Sat, May 8, 2010 at 3:39 PM, Henry Nestler <hen...@ar...> wrote:
>  Hari Krishna Dara wrote:
>>
>> eth0=slirp
>>
>> On the linux side, I used dhcp and after a reboot, I do get the right
>> values for ip (10.0.2.15) and gateway (10.0.2.2). I can ping to
>> 10.0.2.2 and 10.0.2.3 as well, but I can't ping to anything outside,
>> even though their ip gets resolved.
>
> Ping (IMCP-protocol) is not supported by SLiRP.
> Try any other applications with TCP or UDP to check the connection, for
> example "wget google.com"
>

I can't believe I missed to see this information already documented,
thanks for pointing it out. I can see that I am able to access both
internet and VPN via slirp.  However, there are a few issues:
- Name resolution is not working well. I can't resolve names over VPN
(even after adding my VPN name servers to /etc/resolve.conf file) and
a few others that can be resolved from WXP (e.g., names in my local
network).
- I have my tuntap adapter getting registered as the default gateway,
so at first nothing worked. Only when I added the slirp gateway as the
default gateway and removed the tuntap gateway from being the default,
the internet even started worked. Is there a better solution for this
than putting the route commands in /etc/rc.d/rc.local file?

On a side note, I also notice that tuntap adapter started becoming my
default gateway on XP side as well, not sure what is causing this. May
be a reboot will fix it.

-- Hari