vsdb-server listen()'s to /ovsdb-server.$PID.ctl as
default. So I had to set
ovsdb-server --remote=punix:/db.sock
to both ovs-vsctl and ovs-vswitchd communicate with ovsdb-server.
That's why I asked, 'cause seems to me that
all three should default to the same unix
Hi
ovsdb-server uses $PREFIX/var/run/openvswitch/ovsdb-server.$PID.ctl as
its default
unix domain socket (maybe default file name on Linux), while ovs-vsctl
and ovs-vswitchd
uses $PREFIX/var/run/openvswitch/db.sock.
Any special reason for that ?
Att
Lucas Brasilino
MSc Student @ Federal
t, anyway,
If I recall, the patch just comments out the duplicated function
declaration. You can
find those functions and comments it out too, and maybe generate a
patch (with diff) and
configure SPECS file to apply this patch.
regards
Lucas Brasilino
_
ke
some search on mailing list archives.
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
dge. What
you are setting is that traffic which origins or targets br0 interface
IP will be at VLAN 100. So, yes... multiple VLAN tags may exist.
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman
> Is this trivial issue only on Open vSwitch v1.6.1?
I think not. I think this is the expected behaviour.
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
r}' ?
I think so, since NORMAL port instruct OVS to use the traditional
switching/routing
behaviour (I mean, non-OpenFlow pipeline) and doing so you should have a route
between both L3 networks. Adding this more specific flow (higher
priority), it'll be used to send data to
other ne
ins)
the Linux 3.8.0 source tree, or if at least /lib/modules/3.8.0/build/include
is linked (or contains) the kernel headers.
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
dle_age=0, priority=0 actions=NORMAL
I'm using OVS from git repository with datapath kernel module:
openvswitch: Open vSwitch switching datapath 1.10.90, built Feb 16 2013 15:45:10
Attached to this email goes the ovsdb-server's conf.db I created.
regards
Lucas Brasilino
conf.db
Description: Binary data
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
r. And Openflow pipeline +
> flow entries must be implemented for in-band port.
>
> Am I right?
Sounds good for me.
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
ntrol of OVS
? If the answer is positive, how would you like to do so ?
regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
haven't touched
it for more than 3 years... :)
regards
Lucas Brasilino
> Yes, moving the IP address to the bridge is covered in the FAQ:
>
> http://openvswitch.org/faq/
>
> If you want to bridge the traffic, I imagine you want to attach something
> else to t
rnel
on the VM, the CentOS 6.2 one.
Regards
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
sponse frames having it's VLAN tag stripped).
I´m moving forward... any news I'll post here.
thanks!
Lucas Brasilino
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
ed!!! I mean, there's an unwanted tagging to
untagging conversion
I also tried to configure 'sw0p8' as following:
$ ovs-vsctl add-port sw0 sw0p8 -- set Port sw0p8 trunks=10,20 vlan_mode=trunk
with no success (although I know trunk mode is default).
I'm trying to discove
15 matches
Mail list logo
