Here's a CHALLENGE!! Win4Lin + vnet .. HELP!!
 

I am using one USB network adapter, it is a linksys Etherfast 10/100 USB Network adapter. I have no problems connecting in Linux. I have no problems connecting using Win4Lin if I use the Winsock 1 protocol. When I switch to vnet, my browser resolves hostnames, when I type a new address like www.excite.com, the browser will say connecting to site 208.45.133.23, but the connection then times out. Does anyone know what is causing this? For my TCP/IP settings, I have enable DNS, and my physical address of my network adapter in Linux (eth0) as a name server. I have nothing for Gateway in Linux or Windows, I have tried putting various settings in there and still I have had no luck. I have use DHCP for WINS RESOLUTION checked, I have also tried this unticked, no luck. I have obtain an IP address automatically ticked.

Please help if you can.

Check the routing tables

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.183.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.174.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo


If I request an address the routing table will be checked to see where it needs to go.

If it were on the network 172.16.183.0 like 172.16.183.117 for instance it will be sent through vmnet8, if it were on this network 192.168.174.0 like 192.168.174.3 it will go to the vmnet1 interface.

If it were on the 192.168.0.0 network it will go through eth0.
If I request a connectiong to network 127.0.0.0 network it goes to the lo interface


If it's 208.45.133.23 it does not go anywhere because it does not have a route on that network, and it will not simply guess at one.



Now look at this routing table


route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.183.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.174.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0



notice the last line 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

this says everything on any network goes through eth0 as designated by a Destination of 0.0.0.0

The routing table is check in order until a valid route is found, and finally everything that does not match will be sent through eth0 buy the Destination 0.0.0.0

This entry into the routing table is known as a default route or default gateway

you can add a default route like this

ifconfig add default gw 192.168.0.1

However the default gateway computer that you pick must be a router capable of handling this request. Such as your ISP's gateway server or your own router that has a connection established to your ISP's gateway sever.

Thanks for the info. It turned out to be something with Win4Lin. I wiped out the /home/win directory and re-installed my local windows 98 with winsock protocol, then switched to vnet with win_network -v. It then worked with my firewall disabled, so I had to put an entry in rules to allow the virtual network access to the internet, now everything is peachy. whew!!

Thanks again,
Danny