Thanks Ben
-David
On 09/08/2011 12:38 PM, Ben Pfaff wrote:
I sent out a patch that makes OFPP_NONE work for me:
http://openvswitch.org/pipermail/dev/2011-September/011038.html
After it's in, I'll port it to branch-1.2.
On Mon, Sep 05, 2011 at 12:01:16PM -0400, Aaron Rosen wrote:
Thank
I sent out a patch that makes OFPP_NONE work for me:
http://openvswitch.org/pipermail/dev/2011-September/011038.html
After it's in, I'll port it to branch-1.2.
On Mon, Sep 05, 2011 at 12:01:16PM -0400, Aaron Rosen wrote:
> Thanks guys,
>
> I switched to OFPP_LOCAL and it works.
>
> Aaron
Thanks guys,
I switched to OFPP_LOCAL and it works.
Aaron
On Fri, Sep 2, 2011 at 11:43 PM, Nicholas Bastin wrote:
> On Fri, Sep 2, 2011 at 16:46, Jesse Gross wrote:
>>
>> Even before when OVS was less picky about the input port, it didn't
>> implement the behavior that you're describing in ter
On Fri, Sep 2, 2011 at 16:46, Jesse Gross wrote:
> Even before when OVS was less picky about the input port, it didn't
> implement the behavior that you're describing in terms self forwarding
> checks on virtual ports. For most of the virtual ports, it's fairly
> non-nonsensical and spec actuall
On Fri, Sep 2, 2011 at 10:56 AM, Nicholas Bastin wrote:
> On Thu, Sep 1, 2011 at 20:02, Jesse Gross wrote:
>>
>> That's the cause of the problem. OVS is rejecting the packet out
>> because it is being sent from an out-of-range port. It's not entirely
>> clear to me whether this is allowed by th
On Thu, Sep 1, 2011 at 20:02, Jesse Gross wrote:
> That's the cause of the problem. OVS is rejecting the packet out
> because it is being sent from an out-of-range port. It's not entirely
> clear to me whether this is allowed by the OpenFlow spec and should be
> supported. In this case, I beli
On Fri, Sep 2, 2011 at 8:24 AM, Ben Pfaff wrote:
> The in_port is also important when the packet_out's actions include an
> output to OFPP_FLOOD.
[Apologies if I'm being pedantic, but some of this is a little subtle.]
Fwiw, the in_port is actually used as a parameter to all output port
actions.
The in_port is also important when the packet_out's actions include an
output to OFPP_FLOOD.
On Thu, Sep 01, 2011 at 06:54:55PM -0700, Jesse Gross wrote:
> In the case of Open vSwitch some things, such as sFlow, want to do
> accounting based on the input port. The same mechanism is used by OVS
>
In the case of Open vSwitch some things, such as sFlow, want to do
accounting based on the input port. The same mechanism is used by OVS
internally for packets that traverse userspace so it is important that
they get counted but it is possible for the controller to do this as
well.
The OpenFlow s
Sorry could you clarify what the the roll of in_port is for a packet out?
Also the default value for inport for sending a packet in nox is
OFPP_CONTROLLER fwiw.
Thanks
def send_openflow_packet(self, dp_id, packet, actions,
inport=openflow.OFPP_CONTROLLER):
That's the cause of the problem. OVS is rejecting the packet out
because it is being sent from an out-of-range port. It's not entirely
clear to me whether this is allowed by the OpenFlow spec and should be
supported. In this case, I believe that OFPP_NONE is the correct port
to use, although OVS
Opps, I mean:
inport=openflow.OFPP_CONTROLLER
I was talking about outport.
Aaron
On Thu, Sep 1, 2011 at 7:19 PM, Aaron Rosen wrote:
> I tried both OFPP_FLOOD, in addition to OFPAT_OUTPUT 1 and 65534
>
> Thanks,
>
> Aaron
>
> P.S: attached in the first message is a dump of the OF packets tha
I tried both OFPP_FLOOD, in addition to OFPAT_OUTPUT 1 and 65534
Thanks,
Aaron
P.S: attached in the first message is a dump of the OF packets that
are causing this.
On Thu, Sep 1, 2011 at 7:15 PM, Jesse Gross wrote:
> What in_port are you supplying in the packet out message? Is it OFPP_NONE
What in_port are you supplying in the packet out message? Is it OFPP_NONE?
On Thu, Sep 1, 2011 at 8:29 AM, Aaron Rosen wrote:
> No problem:
>
> It says,
>
> Sep 1 15:28:56 planetlab4 ovs-vswitchd: 00192|dpif|WARN|system@dp0:
> execute 0,1 failed (Invalid argument) on packet 66:f3:43:38:f4:a2 >
No problem:
It says,
Sep 1 15:28:56 planetlab4 ovs-vswitchd: 00192|dpif|WARN|system@dp0:
execute 0,1 failed (Invalid argument) on packet 66:f3:43:38:f4:a2 >
Broadcast, ethertype ARP (0x0806), length 56: Request who-has
10.43.100.104 tell 10.43.100.54, length 42
Sep 1 15:28:56 planetlab4 kernel:
It does seem to be the same as the message on the mailing list, which
I don't think was ever understood. I tried and failed to reproduce
this with packet outs and I think that Ben was previously unsuccessful
with LLDP packets.
Can you try the attached patch? It just breaks out the various causes
Yup the same,
[root@planetlab4 ~]# dmesg | grep "Open vSwitch"
Open vSwitch 1.2.90, built Aug 29 2011 15:49:49
[root@planetlab4 utilities]# ./ovs-appctl version
ovs-vswitchd (Open vSwitch) 1.2.90
Compiled Aug 29 2011 15:50:36
Thanks,
Aaron
On Tue, Aug 30, 2011 at 1:07 AM, Justin Pettit wrot
Can you confirm there's no mismatch? If you're running the latest from git,
try running:
./ovs-appctl version
and:
dmesg | grep "Open vSwitch"
to make sure they match.
--Justin
On Aug 29, 2011, at 7:22 PM, Aaron Rosen wrote:
> I'm using the kernel version not the userspace
I'm using the kernel version not the userspace ( unless my understanding of
this is unclear) Also, I'm near positive I'm not mixing versions.
Aaron
On Mon, Aug 29, 2011 at 10:16 PM, Jesse Gross wrote:
> On Tue, Aug 30, 2011 at 12:30 AM, Aaron Rosen wrote:
> > Hello,
> > I'm sending ARP packet
On Tue, Aug 30, 2011 at 12:30 AM, Aaron Rosen wrote:
> Hello,
> I'm sending ARP packets from my openflow controller and everything seems to
> be working on hardware switches though on OVS I'm getting the following
> error in /var/log/messages.
> ovs-vswitchd: 70867|dpif|WARN|Dropped 1 log messages
BTW: this is occurring on the latest source from git.
Also, I'm sending out lldp packets from my controller to do discovery using
ethertype 0x27a0 but these also seem to be getting dropped at ovs with:
Aug 29 15:56:58 planetlab4 ovs-vswitchd: 00180|dpif|WARN|system@dp0: execute
1 failed (Invalid
Hello,
I'm sending ARP packets from my openflow controller and everything seems to
be working on hardware switches though on OVS I'm getting the following
error in /var/log/messages.
ovs-vswitchd: 70867|dpif|WARN|Dropped 1 log messages in last 1 seconds (most
recently, 1 seconds ago) due to exces
22 matches
Mail list logo
