Il fix the problem, thank you for your help. I gave another IP / physical
interface for the tunnel.
I still have some questions about GRE Tunneling.
For now I have:
On phosphorus (eth0:192.168.93.201 / eth1:172.16.0.201)
br0 (tap0 + gre0 -> 172.16.0.202)
On sulphur: (eth0:192.168.93.202 / eth1:172.16.0.202)
br0 (tap0 + gre0 -> 172.16.0.201)
A VM on phosphorus can ping a Vm on sulphur through the GRE tunnel.
What if I want to make several br (br1, br2 and br3) on phosphorus and I want
them to be connected through their own GRE tunnel on their sulphur counterpart
(br1, br2 and br3) only ?
________________________________
De : Jesse Gross <je...@nicira.com>
À : DarkBls <dark...@yahoo.com>
Cc : Justin Pettit <jpet...@nicira.com>; discuss@openvswitch.org
Envoyé le : Mar 22 juin 2010, 0h 01min 22s
Objet : Re: [ovs-discuss] Re : ip_gre_mod.ko module
On Mon, Jun 21, 2010 at 3:47 AM, DarkBls <dark...@yahoo.com> wrote:
>
>ovs-vsctl --db=tcp:192.168.93.201:1977 create interface name=gre0 type=gre
>options:remote_ip=192.168.93.204
>>e29c391b-2e07-4a2e-95de-99cf6f23158d
>>ovs-vsctl --db=tcp:192.168.93.201:1977 create port name=gre0
>>interfaces=[e29c391b-2e07-4a2e-95de-99cf6f23158d]
>>01c689e2-ecab-4ee6-8902-6aba2efe2deb
>>ovs-vsctl --db=tcp:192.168.93.201:1977 add bridge br0 ports
>>01c689e2-ecab-4ee6-8902-6aba2efe2deb
>
All this looks fine.
>>I must have missed something since I don't see any port 47 opened on any
>>server
>
GRE runs over IP protocol 47, not TCP or UDP port 47 so you won't see it listed
in netstat -l.
Since a flow is being setup that is sending traffic to the GRE port the
configuration should be fine. Can you do a tcpdump on the physical interface
to see if there is GRE traffic? Is it possible that something like iptables is
blocking GRE traffic?
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
