>> Nope. The TAP adapter is the gateway for your coLinux in the same way
>> that your router is the gateway for your notebook.
> aaaaaaaaaaa, now i understand. thanks
>> It's also good idea to keep the coLinux networking on a different
>> subnet of 192.168 than the one you're using for your home network, to
>> prevent IP address conflicts.
>> So you might want to try setting the TAP adapter to, say,
>> 192.168.40.1, then set the coLinux IP to 192.168.40.2 (anything from
>> 2-254 should work, actually), then try the NAT again with 602LAN SUITE.
>> -- Aaron
> ok i start 602LAN SUITE and
> NAT started..
> my router is 192.168.0.1
> notebook 192.168.0.3
> tap (on notebook) 192.168.40.1
> on colinux... (gentoo) i type
> ifconfig lo 192.168.40.2 broadcast 192.168.40.255 netmask 255.255.255.0 up
Why on earth would you need a local interface with a different ip than 127.0.0.1 ??
> ifconfig eth0 192.168.40.2 broadcast 192.168.40.255 netmask
> 255.255.255.0 up
And why should it carry the same address than eth0?
Leave lo at 127.0.0.1.
> route add default gateway 192.168.40.1
> in resolv.conf i type my real isp dns
> win don't ping 192.168.40.1 or 40.2
Most likely because the default gateway entry doesn't tell which interface to use and an echo via lo is useless.