Hey all,
Currently I'm strugging with the other way around and after some research I
just decided to write here because I cannot make it work.
How is a port that was changed e.g. by
msg = of.ofp_port_mod( port_no=p,
hw_addr = self.connection.ports[p].hw_addr,
config = of.OFPPC_NO_RECV,
mask = of.OFPPC_NO_RECV )
self.connection.send(msg)
up again, meaning making it behave like a "normal" port that can receive
and forward frames?
Thanks in advance!
Regards,
Julius
On Tue, Jan 22, 2013 at 1:17 PM, Julius Bachnick
<[email protected]>wrote:
> Works like a charm with the betta branch and your suggestion ;).
>
> Thank you!
>
>
> On Tue, Jan 22, 2013 at 12:49 PM, Murphy McCauley <
> [email protected]> wrote:
>
>> Connection is in openflow.of_01. (grep "class Connection")
>>
>> I am pretty sure the ports attribute isn't in master. ports is initially
>> populated from the features message we get when the switch connected, and
>> is then updated by port update messages.
>>
>> The features message is also saved on the Connection object (even in
>> master, I believe). I think it's connection.features -- you can walk
>> through its port list to find the hardware addresses. (This is slightly
>> annoying because port numbers don't relate to position in the list, and
>> it's not kept up to date, of course... this is why the ports attribute was
>> added in betta -- it makes this all easy.)
>>
>> -- Murphy
>>
>> On Jan 22, 2013, at 3:32 AM, Julius Bachnick wrote:
>>
>> > I'm currently a bit lacking of finding the Connection code within the
>> code. I would like to check first, whether that is possible with the master
>> branch as well but I don't seem able to finde the Connection code/spec.
>> >
>> > Where did you gather the provided information?
>> >
>> >
>> > Regards,
>> >
>> > Julius
>>
>>
>
