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

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

On Sun, May 9, 2010 at 1:48 PM, Henry Nestler <hen...@ar...> wrote:
>> 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).
>
> SLiRP use only the first nameserver from Windows and forwards it under
> 10.0.2.3. So, it is a good idea, to add more nameserver's in
> /etc/resolve.conf manualy. For me, it works in special environment with DNS
> server on intranet (closed DNS, not Internet) it was ok. Not explicitly
> tested for a VPN.

I added DNS servers ips from my vpn adapter to the /etc/resolve.conf
along with my router's ip. I am able to ping to those name servers
when my vpn is up (which BTW, I thought wouldn't work because slirp is
not supposed to support ping). I suppose there is nothing that can be
done on the windows side? Would adding additional NAMESERVER entries
into the /etc/sysconfig/network-scripts/ifcfg-eth0 help (which I am
not actually sure is valid).

>
>> - 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?
>
> Don't set any gateway for TAP.
>
> TAP is a private network between Linux and host and not need a default
> gateway. The route for this network will automatically set after the
> interface will coming up.
>
> That means, don't set gateway in file /etc/network/interfaces for tap device
> under Debian.
>
> PS: In some docs a gateway was set, because TAP device was used as "Internet
> connect sharing" (ICS).
>
>> 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.
>
> I hope the TAP has an other network range as all your other networks
> (Ethernet cards and Wi-Fi). And the same as under Linux: Don't set a route
> or gateway for TAP device.

Great, these two changes got me the right gateway settings for both
linux and windows and everything seems to be working great (except for
the name resolution as described above).

Thank you very much for getting me through so far, I really appreciate
it. I got slirp port-forwarding also to work beautifully and all of
this would help reduce the complexity of how I move files around and
work with our SCM without additional ssh tunnels.

PS: Henry, sorry about the duplicate, I first used reply instead of reply all.

-- Hari