Find the answer to your Linux question:
Results 1 to 3 of 3
I've got a strange problem, hope someone can help me. I've been wrestling with the approach to solve this problem for 6 hours now, and I've found what I believe ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2008
    Posts
    2

    Routing between 2 networks


    I've got a strange problem, hope someone can help me. I've been wrestling with the approach to solve this problem for 6 hours now, and I've found what I believe to be the true solution - but I'm having a problem.

    I've got a linux server that has 3 networks on it.

    wlan0 which is 192.168.1.x
    eth1 which is 192.168.0.x
    vmnet1 which is 172.16.137.x

    I have a virtual machine running Windows 2000 bound to vmnet1. I want to bring internet from wlan0 to this virtual machine. Since VMware will not allow me to bind to anything other than the vmnetX interfaces, I've created a route on the virtual machine:

    route add 192.168.1.0 Mask 255.255.255.0 172.16.137.1

    As I understand, this should direct any traffic for 192.168.1.x to 172.16.137.1 (which is my router/linux machine via interface vmnet1). The router internet machine is also accessible via 192.168.0.1 via eth1 and also via wlan0 on 192.168.1.100.

    This works, however I cannot ping the gateway for wlan0 (192.168.1.1). I AM however, able to ping 192.168.1.100, the servers assigned IP from the router but I can't ping the actual gateway, which is what I need. I'm looking to be able to access 192.168.1.1 from my 172.16.137.2 [the virtual machine] so I can use it as a gateway and thus bringing internet to the virtual machine from the wireless interface wlan0.
    I am able to ping the gateway from the server itself, so 192.168.1.1 is pingable.

    I've been going hard at this for over 6 hours, I even tried an iptables command to forward packets for 192.168.1.10 to 192.168.1.1 but still no go.

    Any ideas???

  2. #2
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,760
    Yes - read the VMWare docs. Since you didn't tell anyone you're using VMWare, I have to assume from the vmnet1 switch that it is VMWare.

    The default VMWare config is that vmnet1 is a HOST-ONLY network. To route out of it, you would need to put a VM with 2 NIC's connected to vmnet1 and another network with external access - vmnet8 or vmnet0.

    But again, since this is VMWare (which doesn't support a bridged connection over a wireless NIC), vmnet0 would need to be bridged to eth1.

    The easiest method would be to connect the NIC in the VM to the vmnet8 network - the default NAT'ed network.

  3. #3
    Just Joined!
    Join Date
    Nov 2008
    Posts
    2
    Thanks for the reply; I saw the host-only option and didn't choose it, I didn't know that the vmnetx's options were also host only..

    I will take a crack at this and read the suggested docs last tonight; my tie rods just came in and I have 3 hours before dark to get this done!

    I'll come back here later tonight and let you know how I made out

    thanks

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •