Changes between Version 14 and Version 15 of DesignOverview


Ignore:
Timestamp:
Feb 10, 2014 1:04:11 PM (4 years ago)
Author:
ivan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DesignOverview

    v14 v15  
    1414The network model component of !NetCheck simulates syscalls to determine if a given syscall can be added as the next syscall in the global order. The network model treats the network and the application that generated the traces as a blackbox and requires no application-specific information. 
    1515 
    16 To simulate a syscall, the model uses the current network and host states tracked by the model, and network semantics defined by the POSIX API. The network model state includes information related to the observed connections/protocols (e.g., pending or established TCP connections), buffer lengths and their contents, datagrams sent/lost, etc. The details about our simulation can be found [https://netcheck.poly.edu/projects/project/wiki/network_model here]. Simulating a syscall with a model results in one of three determinations: accept the call, reject the call, or permanently reject the call. Call rejections are actually invalid model transitions and you can look at the list of these conditions [https://netcheck.poly.edu/projects/project/wiki/network_model here]. 
     16To simulate a syscall, the model uses the current network and host states tracked by the model, and network semantics defined by the POSIX API. The network model state includes information related to the observed connections/protocols (e.g., pending or established TCP connections), buffer lengths and their contents, datagrams sent/lost, etc. Simulating a syscall with a model results in one of three determinations: accept the call, reject the call, or permanently reject the call. Call rejections are actually invalid model transitions and you can look at the list of these conditions [https://netcheck.poly.edu/projects/project/wiki/network_model here]. 
    1717 
    1818==  Fault diagnoses engine ==