Jump to content

Network bug on ESET internet security (Win10)


Go to solution Solved by Marcos,

Recommended Posts

Hello,

I could not find other way to report bug I found with default configuration on ESET Internet Security (Windows 10),

straight after activation ESET breaks PMTUD, any packets with don't fragment flag set are being randomly modified and flag cleared so it allows IP fragmentation as a result. I have also noticed that traceroute is broken always pinging destination on first hop (this is due to TTL field being reset to default 128). I don't think it's correct behaviour unless I don't understand something.

Once switched from Internet Security to NOD32 I don't have this problem and PMTUD & traceroute behave as they should.

I can provide more information if needed.

My product version is 17.1.9.0
OS: Win10 64bit

Link to comment
Share on other sites

  • Administrators

Please kindly proceed as follows:
1, Enable advanced network traffic scanner logging (advanced setup -> Tools -> Diagnostics)
2, Start capturing the network communication with Wireshark
3, Reproduce the issue
4, Stop logging and save the Wireshark log.
5, Collect logs with ESET Log Collector
6, Supply us with both ELC and Wireshark logs for perusal.

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...