Hi Etienne, You are not supposed to get a PORT_DOWN when you remove the cable, it's when it's when "port is administratevely down". (I think there is a link-down bit in newer versions of the spec that would capture this). To change the status of a port you can send an openflow port-mod message.
What is your use case? Would a topology/host discovery on the controller help here? Regards, Yiannis On Wed, May 15, 2013 at 10:36 AM, Etienne Mula <etiennem...@gmail.com>wrote: > Hi All, sorry for sending another email however i have a strange thing > happening on the WR-1043ND. Basically when disconnecting a client > irrispective if by cable or issuing ifconfig eth0 down, the AP doesnt send > any port down notifications to the controller. I've checked thorugh > wireshark and infact i confirmed that these are not being recieved. Any > ideas why this is happening please ? > > > Regards > Etienne > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
