This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
midd:traffic_scheduling:project_log [2009/03/23 23:07] afbarnard added project log entry |
midd:traffic_scheduling:project_log [2009/03/31 20:33] perryk |
||
---|---|---|---|
Line 78: | Line 78: | ||
AB - Worked on project wiki site. Created main page, reorganized existing content, uploaded proposal. | AB - Worked on project wiki site. Created main page, reorganized existing content, uploaded proposal. | ||
+ | |||
+ | ==== 03/29 ==== | ||
+ | |||
+ | PK - Have real time capture on server working. Was a little more difficult than expected as the server doesn't have a complete picture of who is sending to it. It builds a time-based partner dictionary and filters packets based on who is in the dictionary. If no packets have been sent or received with a partner, the partner times out and is removed from the filter dictionary. Next step is to provide a data exchange mechanism between client and server where by one tells the other what it's packet history is. | ||
+ | |||
+ | AB - Looked up useful SNMP variables. Information is on the [[midd:traffic_scheduling:metrics#SNMP|metrics page]]. | ||
+ | |||
+ | ==== 03/30 ==== | ||
+ | |||
+ | Looked for TCP PUSH support in Windows (.NET). There isn't any. Zilch. | ||
+ | |||
+ | ===3/31/2009=== | ||
+ | |||
+ | PK - it looks like SNMP won't be usable by us. a) It is hardware dependent - you must know what hardware you're talking to in order to use it b) it requires a known "community name" which works as a password - since we don't know it, we can't use it. :( | ||
+ | |||