Conflict: Nod32 & Aventail Connect 4.12 (2)

Discussion in 'NOD32 version 2 Forum' started by acue, Oct 26, 2006.

Thread Status:
Not open for further replies.
  1. acue

    acue Registered Member

    Joined:
    Jul 19, 2006
    Posts:
    5
    The original thread is very old, so I create this one.
    I have found the reason and the decision.

    After installing Aventail and Nod32 I'v got the following important LSP chains:
    1. Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP]:
    chains 2 elements: > AutoSocks LSP Dummy Entry > MSAFD Tcpip [UDP/IP]
    2. Aventail AutoSocks LSP over MSAFD Tcpip [TCP/IP]:
    chains 2 elements: > AutoSocks LSP Dummy Entry > MSAFD Tcpip [TCP/IP]
    3. NOD32 protected [Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP]]:
    chains 3 elements: > NOD32 > Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP] > MSAFD Tcpip [UDP/IP]
    4. NOD32 protected [Aventail AutoSocks LSP over MSAFD Tcpip [TCP/IP]]:
    chains 3 elements: > NOD32 > Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP] > MSAFD Tcpip [TCP/IP]

    The system is not working such a way. I'v corrected 3 and 4:
    3. NOD32 protected [Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP]]:
    chains 4 elements: > NOD32 > Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP] > AutoSocks LSP Dummy Entry > MSAFD Tcpip [UDP/IP]
    4. NOD32 protected [Aventail AutoSocks LSP over MSAFD Tcpip [TCP/IP]]:
    chains 4 elements: > NOD32 > Aventail AutoSocks LSP over MSAFD Tcpip [UDP/IP] > AutoSocks LSP Dummy Entry > MSAFD Tcpip [TCP/IP]
    This variant works fine!

    Conclusion: it seems nod32 imon have a bug at algorithm assigned for installing it in winsocks when there is another LSP elements.
     
  2. acue

    acue Registered Member

    Joined:
    Jul 19, 2006
    Posts:
    5
    Are there any comments from developers?

    Sorry, for flood.
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    IMON was designed to work properly with any LSP, it can receive data and forward it to the next LSP fine. Unfortunately, often the other LSPs are not designed to work in conjunction with the others and do not forward the data as supposed.
     
  4. acue

    acue Registered Member

    Joined:
    Jul 19, 2006
    Posts:
    5
    Yes, IMON is working properly with Aventail LSP too, but only after I'v manually corrected a chain created by NOD.

    Don't you see that NOD is responsible for building wrong LSP chain at the example?
    Or do you think that Aventail LSP has incorrect or missing parameters that prevent NOD from making well-working LSP chain?
     
Thread Status:
Not open for further replies.