• need route help

    From Todd@110:110/2002 to All on Sat Nov 2 06:52:14 2013
    Hi All,

    I have a Virtual Machine on 192.168.255.0/24
    with an address of 192.168.255.101

    On that network is a tap device (OpenVPN) with is
    192.168.210.0/24. It resides on 192.168.255.10
    The Tap's IP is 192.168.210.50

    From 192.168.255.10, I can ping 192.168.210.100

    From the VM, I can ping 192.168.255.10.
    But, I can not ping 192.168.210.100.

    What is the syntax for the route command that I
    need to add to the VM? What am I doing wrong?

    Many thanks,
    -T


    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    the riddle wrapped in an enigma wrapped
    in a couple slices of baloney
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: A noiseless patient Spider (110:110/2002@linuxnet)
  • From Pascal Hambourg@110:110/2002 to All on Sat Nov 2 09:05:11 2013
    Reply-To: pascal.news@plouf.fr.eu.org

    Hello,

    Todd a ‚crit :

    I have a Virtual Machine on 192.168.255.0/24
    with an address of 192.168.255.101

    On that network is a tap device (OpenVPN) with is
    192.168.210.0/24. It resides on 192.168.255.10
    The Tap's IP is 192.168.210.50

    IIUC, there is a host with two interfaces :
    - a regular ethernet interface connected to network 192.168.255.0/24
    with address 192.168.255.10 ;
    - a TAP interface connected to network 192.168.210.0/24 with address 192.168.210.50.

    Am I correct ?

    From 192.168.255.10, I can ping 192.168.210.100

    Actually from 192.168.210.50, I guess.

    From the VM, I can ping 192.168.255.10.
    But, I can not ping 192.168.210.100.

    What happens exactly ?

    What happens if you ping 192.168.210.50 from the VM ?
    If you get a reply, then it means that the VM has the proper route to
    reach 192.168.210.0/24. Otherwise, you need to add one with gateway 192.168.255.10. Now you should get a reply.

    Then try again to ping 192.168.210.100 from the VM. If you don't get a
    reply, then either the intermediate host is not acting as a router (i.e.
    doing IP forwarding) and you need to enable ip_forward, or the remote
    host 192.168.210.100 does not have a proper route to 192.168.255.0/24
    and you need to add one with gateway 192.168.210.50.

    What is the syntax for the route command that I
    need to add to the VM?

    man route
    man 8 ip

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: Plouf ! (110:110/2002@linuxnet)
  • From Todd@110:110/2002 to All on Sat Nov 2 22:48:51 2013
    On 11/02/2013 02:05 AM, Pascal Hambourg wrote:
    Hello,

    Todd a ‚crit :

    I have a Virtual Machine on 192.168.255.0/24
    with an address of 192.168.255.101

    On that network is a tap device (OpenVPN) with is
    192.168.210.0/24. It resides on 192.168.255.10
    The Tap's IP is 192.168.210.50

    IIUC, there is a host with two interfaces :
    - a regular ethernet interface connected to network 192.168.255.0/24
    with address 192.168.255.10 ;
    - a TAP interface connected to network 192.168.210.0/24 with address 192.168.210.50.

    Am I correct ?

    From 192.168.255.10, I can ping 192.168.210.100

    Actually from 192.168.210.50, I guess.

    From the VM, I can ping 192.168.255.10.
    But, I can not ping 192.168.210.100.

    What happens exactly ?

    What happens if you ping 192.168.210.50 from the VM ?
    If you get a reply, then it means that the VM has the proper route to
    reach 192.168.210.0/24. Otherwise, you need to add one with gateway 192.168.255.10. Now you should get a reply.

    Then try again to ping 192.168.210.100 from the VM. If you don't get a
    reply, then either the intermediate host is not acting as a router (i.e. doing IP forwarding) and you need to enable ip_forward, or the remote
    host 192.168.210.100 does not have a proper route to 192.168.255.0/24
    and you need to add one with gateway 192.168.210.50.

    What is the syntax for the route command that I
    need to add to the VM?

    man route
    man 8 ip


    Hi Pascal,

    Before I waste your time, I think there is a setting in
    my OpenVPN tunnel config file for this. Let me read it over
    really closely first.

    -T


    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    the riddle wrapped in an enigma wrapped
    in a couple slices of baloney
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: A noiseless patient Spider (110:110/2002@linuxnet)
  • From Tauno Voipio@110:110/2002 to All on Sun Nov 3 08:04:36 2013
    On 3.11.13 12:48 , Todd wrote:
    On 11/02/2013 02:05 AM, Pascal Hambourg wrote:
    Hello,

    Todd a ‚crit :

    I have a Virtual Machine on 192.168.255.0/24
    with an address of 192.168.255.101

    On that network is a tap device (OpenVPN) with is
    192.168.210.0/24. It resides on 192.168.255.10
    The Tap's IP is 192.168.210.50

    IIUC, there is a host with two interfaces :
    - a regular ethernet interface connected to network 192.168.255.0/24
    with address 192.168.255.10 ;
    - a TAP interface connected to network 192.168.210.0/24 with address
    192.168.210.50.

    Am I correct ?

    From 192.168.255.10, I can ping 192.168.210.100

    Actually from 192.168.210.50, I guess.

    From the VM, I can ping 192.168.255.10.
    But, I can not ping 192.168.210.100.

    What happens exactly ?

    What happens if you ping 192.168.210.50 from the VM ?
    If you get a reply, then it means that the VM has the proper route to
    reach 192.168.210.0/24. Otherwise, you need to add one with gateway
    192.168.255.10. Now you should get a reply.

    Then try again to ping 192.168.210.100 from the VM. If you don't get a
    reply, then either the intermediate host is not acting as a router (i.e.
    doing IP forwarding) and you need to enable ip_forward, or the remote
    host 192.168.210.100 does not have a proper route to 192.168.255.0/24
    and you need to add one with gateway 192.168.210.50.

    What is the syntax for the route command that I
    need to add to the VM?

    man route
    man 8 ip


    Hi Pascal,

    Before I waste your time, I think there is a setting in
    my OpenVPN tunnel config file for this. Let me read it over
    really closely first.

    -T


    Are you sure that there is no mix-up with level 2 (Ethernet)
    and level 3 (IP) tunneling?

    You are using the tap interface, which is a level 2 device for
    forwarding Ethernet frames, and the ends of the tunnel are
    in the same logical local network.

    If you want to have the tunnel ends to be in different local
    networks, you need IP tunneling with the tun interface and
    suitable routing for the networks.

    Please note that in a level 3 routed network, there are 4
    IP addresses for the tunnel:

    - 2 for tunnel outside, connecting the tunnel ends via
    the external network (Internet). For OpenVPN, these
    are by default for UDP port 1194.

    - 2 for the tunnel inside, transporting the tunneled traffic.
    These need to be included into the routing tables.

    --

    Tauno Voipio


    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: A noiseless patient Spider (110:110/2002@linuxnet)
  • From Todd@110:110/2002 to All on Mon Nov 4 07:53:24 2013
    On 11/01/2013 11:52 PM, Todd wrote:
    Hi All,

    I have a Virtual Machine on 192.168.255.0/24
    with an address of 192.168.255.101

    On that network is a tap device (OpenVPN) with is
    192.168.210.0/24. It resides on 192.168.255.10
    The Tap's IP is 192.168.210.50

    From 192.168.255.10, I can ping 192.168.210.100

    From the VM, I can ping 192.168.255.10.
    But, I can not ping 192.168.210.100.

    What is the syntax for the route command that I
    need to add to the VM? What am I doing wrong?

    Many thanks,
    -T


    HI Guys,

    I got working what I need on the host, so
    I no longer need to route the VM's. Thank you
    for the help!

    -T


    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    the riddle wrapped in an enigma wrapped
    in a couple slices of baloney
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: A noiseless patient Spider (110:110/2002@linuxnet)