Create data table for idle timeout allocation about spacedancers HOT 5 CLOSED

We should save the flow info to use it on later.

from spacedancers.

This is the data table for the flow table statistics below:

Data table:

Flow table:

Some flows have only last_packet_in and last_removed time; they are the ones we see being timeouted in a batch manner when we use the command pingall. Since they dont seem in the flow table and i update the other fields at the flow table stat request; those information is missing for them. Thus before or while constructing our algorithm, we should do the necessary checks.

from spacedancers.

The last duration must be of the type seconds, but it seems like there is problem in there, i will fix it.

from spacedancers.

In this version of the code, another coming of the same flow is treated as if it is a new flow since we are always increasing the cookie value at flow addition and I'm using the cookie value to hold the flow in the data table.

Instead, I will use another unique identifier to fix this problem.

from spacedancers.

Data table is created and working like this:

When i say pingall, the data table was like this at first:

Then was like this:

It works. Table size is limited to 5.

from spacedancers.