-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Segmentation fault when specify a specific filter with Captagent 6.4.1 #271
Comments
I dont think the problem is the portrange to be honest, as the Anyway if it's generate a corecump you can run |
Hi @tuan-pham-hoiio
Unfortunately I cannot reproduce it. Thank you |
Thanks for the investigation. Sorry for taking so long to generate the core dump file.
|
That occurs if listening on device captagent/src/modules/socket/pcap/socket_pcap.c Lines 468 to 479 in 47f67cc
captagent/src/modules/socket/pcap/socket_pcap.c Lines 504 to 507 in 47f67cc
captagent/src/modules/socket/pcap/socket_pcap.c Lines 522 to 528 in 47f67cc
[1] https://www.tcpdump.org/linktypes/LINKTYPE_LINUX_SLL.html |
Thank you for your info @btriller. So basically, i can overcome this by setting the device part to specific interface? |
Yes, that's always better than left |
Hi @tuan-pham-hoiio I cannot reproduce the issue, to be honest, so it could be something with this particular traffic.. IMHO the thing is that when you put |
Here is a 30-second-traffic pcap file: Thank you so much for your support ^^. |
Hi, I am upgrading from Captagent 6.3.1 to 6.4.1. In the process, I could not get Captagent 6.4.1 to work with this socket_pcap.xml:
It continually throw out error like this
segfault at 0 ip 00007f71deba4ffc sp 00007f71ddcb4e20 error 4 in socket_pcap.so[7f71deba1000+e000]
.When changing to other portrange, Captagent return to normal.
Can you check why this specific portrange is not applicable.
Thank you a lot.
The text was updated successfully, but these errors were encountered: