It sounds like this is a controller configuration problem. If you want
the controller to behave differently, then I guess you should configure
it differently.
On Mon, Mar 19, 2018 at 01:21:06PM -0400, Sh j wrote:
> Thank you for your reply.
>
> The problem is that if I do not assign IP addresses
Thank you for your reply.
The problem is that if I do not assign IP addresses to bridges, these two
OVSs can not ping each other.
There are some papers that they use OVSs to connect each other without any
hosts connected to them (wmSDN).
In that case, is it possible to configure OVS to avoid the c
On Sat, Mar 17, 2018 at 08:11:48PM -0400, Sh j wrote:
> Hello everyone,
>
> I configured two OVSs as follows,
>
> OVS1(eth0) --- (eth0)OVS2
>
> ovs-vsctl add-br brx
> ovs-vsctl add-port brx ethx
> ip addr flush dev ethx
> ip addr add 10.0.0.x/16 dev brx
> ip link set brx up
>
> Then I set t
Hello everyone,
I configured two OVSs as follows,
OVS1(eth0) --- (eth0)OVS2
ovs-vsctl add-br brx
ovs-vsctl add-port brx ethx
ip addr flush dev ethx
ip addr add 10.0.0.x/16 dev brx
ip link set brx up
Then I set them to connect to a controller as follows,
ovs-vsctl set-controller brx tcp:
