-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ERROR] Parsing field: ipv6.addr #20
Comments
Hi @dragonxtek, This error seems to be related with the permissions with which you execute the capture. Run Polymorph with the administration user, without using sudo, as there are several processes that run the tool that require high privileges, including the capture through pyshark and tshark. |
Hi @dragonxtek, I cannot reproduce the error in my test environment. Can you tell me more details about the environment in which you are running Polymorph? Additionally, could you attach in the comment the .tmp.pcap file that is in path Thanks! |
Hi @shramos, |
UPDATE:
|
Hi @dragonxtek, Thank you for your response. I tried to reproduce the error in the same environment you have and I can't. Importing a template and performing network packet interception works well because it does not involve the external pyshark library. The error seems not to be related to Polymorph but to this library (Pyshark) used during the initial capture process. We will continue to perform some additional testing to see if we can find the error. On the same operating system where the error occurs, run the following commands to see if we can isolate the error:
|
Here is the output:
|
Now, I have tshark 3.3 and I can't capture any packets
Can you fix it to do it compatible with recent tshark versions? |
I have tshark 2.64 and the same problem. Can you give me any hint where to search in the code to fix it? |
I added some prints to _traverse_fields and I would bet the problem lies in a format change of pyshark in the ip.addr field. Maybee this helps. Has anyone a working version and can help me? |
Hi again,
I installed the last version 2.0.5 but the error still appears, is not solved as you said in #17
The text was updated successfully, but these errors were encountered: