Thanks Jesse,
With your inputs, have been able to resolve this issue now.
Thanks
Rashmi
On Wed, Dec 18, 2013 at 12:39 AM, Jesse Gross wrote:
> You shouldn't include eth0 on M2 and M3 in the bridges. I guess those
> are the interfaces that the GRE tunnel is configured over but that's
> not nec
You shouldn't include eth0 on M2 and M3 in the bridges. I guess those
are the interfaces that the GRE tunnel is configured over but that's
not necessary since the packets will find the correct interface using
the routing table. If it's another set of interfaces then it will form
a loop.
On Tue, De
Jesse,
M2/eth0 is physically connected to M3/eth0. Both these machines are running
OVS, and have a GRE tunnel configured between them.
M2/eth1 is physically connected to M1/eth0. Here M1 is a client machine,
whose ping req./resp. are expected to be GRE encapsulated (between M2 &
M3).
For this
On Tue, Dec 17, 2013 at 1:00 AM, Rashmi Rashmi wrote:
> Hello,
>
>
>
> I am using a GRE tunnel with OVS. Here is the setup detail:
>
>
>
>
>
> +--+ eth0 (11.0.0.2) eth1 ++ eth0
> eth0 ++
>
> | M1 (Linux) |-|
Hello,
I am using a GRE tunnel with OVS. Here is the setup detail:
+--+ eth0 (11.0.0.2) eth1 ++ eth0
eth0 ++
| M1 (Linux) |-| M2 (Linux)
|
