On Wed, Mar 13, 2013 at 01:54:11PM -0700, Gurucharan Shetty wrote:
> For anyone else interested in the reason for the error, it looks like
> the error comes from trying to add zeroconf route twice in
> /etc/sysconfig/network-scripts/ifup-eth. If someone does not want this
> error show up (and don't
On Wed, Mar 13, 2013 at 9:54 AM, Gurucharan Shetty wrote:
> On Wed, Mar 13, 2013 at 7:33 AM, Denis Iskandarov
> wrote:
>> Again occurred warning from CentOS 6.3, reported here:
>> http://openvswitch.org/pipermail/discuss/2012-October/008322.html
>>
>> Everything works. No ip disconnects.
>> In my
I'm trying.
It's not error of OVS but as well not problem of system only.
RTNETLINK is like bridge between kernel and userspace which notifies and
controls network aspects of systems.
http://www.linuxjournal.com/article/8498
System giving warning because scripts on which ovs depends ifup-ovs
ifdown
On Wed, Mar 13, 2013 at 09:29:52PM +0400, Denis Iskandarov wrote:
> I've tried your suggestion and renamed ovs0 to br0.
> But still same.
> I knew that it's not problem but anyways tried. Anything could happen.
> I knew because it's giving this warning not on bridge creation but on both
> ethernets
I've tried your suggestion and renamed ovs0 to br0.
But still same.
I knew that it's not problem but anyways tried. Anything could happen.
I knew because it's giving this warning not on bridge creation but on both
ethernets i added to this bridge.
Here is output of "service network restart" with br
On Wed, Mar 13, 2013 at 09:15:35PM +0400, Denis Iskandarov wrote:
> You are so predictable :)
If you ask me the same question twice, it should not surprise you that
you get the same answer both times.
> I think we talked about this once... about "producing command"...
> I have attached all output
Hi, Ben ...
You are so predictable :)
I think we talked about this once... about "producing command"...
I have attached all outputs i could gather. log messages sh -vx output.
This is all i can do.
You can see all info i have included and maybe understand much more as you
are developer of this
On Wed, Mar 13, 2013 at 7:33 AM, Denis Iskandarov
wrote:
> Again occurred warning from CentOS 6.3, reported here:
> http://openvswitch.org/pipermail/discuss/2012-October/008322.html
>
> Everything works. No ip disconnects.
> In my opinion it's seems to be like warning message that device with such
On Wed, Mar 13, 2013 at 06:33:41PM +0400, Denis Iskandarov wrote:
> service network restart
> Shutting down interface eth0: [ OK ]
> Shutting down interface ovs0: [ OK ]
> Shutting down loopback interface: [ OK
On Wed, Mar 13, 2013 at 3:49 AM, Liran Schour wrote:
>
> Jesse Gross wrote on 11/03/2013 06:31:12 PM:
>
>> On Mon, Mar 11, 2013 at 9:15 AM, Liran Schour wrote:
>> >
>> > Hi,
>> >
>> > I wanted to know what is the current status of flow based tunneling,
> is it
>> > available on 1.9.0 release?
>
On Tue, Mar 12, 2013 at 8:56 PM, Guangvy <1965837...@qq.com> wrote:
> Hi,
> There are the following descriptions in the file vswitchd/vswitch.xml
> 'master' branch
>
>
> Required. The tunnel endpoint. Unicast and multicast endpoints
> are
> both supported.
>
Jesse Gross wrote on 11/03/2013 06:31:12 PM:
> On Mon, Mar 11, 2013 at 9:15 AM, Liran Schour wrote:
> >
> > Hi,
> >
> > I wanted to know what is the current status of flow based tunneling,
is it
> > available on 1.9.0 release?
> > Is there any documentation about how to use this feature? Any
s
Tried to add additional guest-os network interface(eth1) which is not
connected to any host-os interface.
Resides and connected only in OS where OVS is installed: centOS 6.4
Maybe something wrong with ifup ifdown scripts with pre up or pre down
function like some excess statement check in scripts.
Again occurred warning from CentOS 6.3, reported here:
http://openvswitch.org/pipermail/discuss/2012-October/008322.html
Everything works. No ip disconnects.
In my opinion it's seems to be like warning message that device with such
MAC address.
But if systems saying me something i want to understa
I think there is some misunderstanding of my topology.
controller(10.0.0.11)
openvswitch(10.0.0.12)<--Install at the host.connecting to the
controller
vm1(10.0.0.13) vm2(10.0.0.14)< Two vm on the host.Connecting to the
vswitch
Gateway maybe 10.0.0.254.
Sorry about my un-precise words.
> tcpdump runs before Open vSwitch so it's not being discarded by OVS.
> You mentioned that that this is a vlan, are tagged packets being
> delivered directly to the host? Some versions of the Linux kernel
> have problems with vlans when used with OVS.
Thx, I'm currently thinking it is hardware r
Sorry, maybe it was my mistakeI copy what we told before to keep
everything on the mailing list...
Anyway...I told you that because it seems an error of interfaces
configurationthis doesn't necessary means that it can't work at all
What do you mean with gateway? Are you talking abou
Hi,
I am trying to use floodlight controller to control the openvswitch(1.7.3).
And I did not change the configuration in floodlight.
controller(10.0.0.11)<->openvswitch(10.0.0.12) --->VM1(10.0.0.13)
L--->VM2(10.0.0.14)
This is my topology.
I know controller will push packe
The Beacon mailing list is probably the best place to ask that question.
--Justin
On Mar 12, 2013, at 7:30 PM, Ashwini Pugazhendhi
wrote:
> Hello,
>
> How can I send flows to an OVS from Beacon controller?
> --
> Yours,
> Ashwini Kshathriya.
> ___
19 matches
Mail list logo
