SD-WAN

can anyone explain why i could be getting a permission error. could it be because of LLDP i am doing an experiment and i am using LLDP packet to calculate delay. but it wont work. here is the debug output below. 

OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137980):

0000:01:14:17.47 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 19: vid 1
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.47 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137980): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 80 ff ff ff ff ff ff ff fd
|...h*.y......
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137981):

0000:01:14:17.47 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 20: vid 1
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.47 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137981): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 81 ff ff ff ff ff ff ff fd
|...h*.y......
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137982):

0000:01:14:17.47 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 21: vid 1
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.47 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137982): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 82 ff ff ff ff ff ff ff fd
|...h*.y......
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137983):

0000:01:14:17.47 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 22: vid 1
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.47 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137983): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 83 ff ff ff ff ff ff ff fd
|...h*.y......
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137984):

0000:01:14:17.47 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 23: vid 1
0000:01:14:17.47 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.48 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137984): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 84 ff ff ff ff ff ff ff fd
|...h*.y......
0000:01:14:17.48 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
OFPT_PACKET_OUT (OF 0x04) (xid=0x2a137985):

0000:01:14:17.48 OPFL eOFNetTask:Instance:aggregate, Attempt to send pkt out
port 24: vid 1
0000:01:14:17.48 OPFL eOFNetTask:RX from tcp:192.168.1.253:6633: 0:
"error_code":"OFPBRC_EPERM","error_reason":"Reason for failure not recorded",
0000:01:14:17.48 OPFL eOFNetTask:TX to tcp:192.168.1.253:6633: 0 : OFPT_ERROR
(OF 0x04) (xid=0x2a137985): OFPBRC_EPERM
(***truncated to 64 bytes from
104***)
00000000 04 0d 00 68 2a 13 79 85 ff ff ff ff ff ff ff fd

just to add i am using ryu controller

I see that you're sending packets out of multiple ports on VID 1. Is this VID a member of the OpenFlow instance you're sending PACKET-OUT messages to?

If you could post the switch configuration and firmware version, it would be helpful in diagnosing this behavior.

Shaun

thanks for response this problem seem to happen because openflow was configured in aggregate mode its okay when i configure using a member vlan

Thanks for the follow-up, although the functionality should work in either mode. Essentially an aggregate instance is just a vlan-based instance with all vlans (except the control-plane) in the instance. I wonder the aggregate instance was configured with VLAN 1 as the control-plane?