Basically this is what is happening when i'm connecting the PC to the AP then disconnecting it and connecting it to the Mirkotik .
Switch ports are shown for both the old and the new connection points. Thanks again! Etienne On 15 May 2013 20:45, Etienne Mula <etiennem...@gmail.com> wrote: > The mikrotik uses spec 1.0 as referenced in their website > http://wiki.mikrotik.com/wiki/Manual:OpenFlow. hmmm if you tell me that > its normal then i dont have to worry then. Sorry for the stupid question > but how do i configure port-mod openflow message ? is this done directly > from the controller ? > > What i'm trying to do is to bi-casting using floodlight controller. > Therefore i need that the client which roams from AP1 to AP2 must be > deleted from AP1 therefore it should not be shown as connected with AP1. > > > On 15 May 2013 20:36, Yiannis Yiakoumis <yiann...@stanford.edu> wrote: > >> What version and implementation does the microtik switch uses? The way I >> read the 1.0 spec, you are not supposed to send a PORT_DOWN message when >> you disconnect the cable. It is to be sent when you explicitly configure >> the port status "down" (using the port-mod openflow message). >> >> >> On Wed, May 15, 2013 at 11:07 AM, Etienne Mula <etiennem...@gmail.com>wrote: >> >>> Hi Yiannis, >>> >>> Thanks for your reply . sorry but didnt really understand here. I have >>> a TP-Link AP and i connected my laptop to it, till here fine the port is >>> added and it is shown to the controller. However if i disconnect the port >>> from the AP , the OF protocol doesnt sends an Port Status notifications to >>> the controller . I want to check if this is normal when using Pantou on >>> OpenWRT. On the other hand using a mikrotik switch if i disconnect the >>> client it sends the Port status notification to the controller. >>> >>> Many thanks :) >>> Etienne >>> >>> >>> On 15 May 2013 19:58, Yiannis Yiakoumis <yiann...@stanford.edu> wrote: >>> >>>> 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 >>>>> >>>>> >>>> >>> >>> >>> -- >>> Thanks and Regards >>> Etienne Mula >>> >> >> > > > -- > Thanks and Regards > Etienne Mula > -- Thanks and Regards Etienne Mula
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
