-
Notifications
You must be signed in to change notification settings - Fork 266
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
[Bug] Fortigate and tcpreplay #852
Labels
Comments
In this case, I have a little network (ALFA and BETA laptops connected to TAP). The Port Monitor of TAP send the traffic between ALFA and BETA. ALFA send 3 request of ping to BETA and BETA send 3 reply, then the Port Monitor of TAP send 6 paquetes and in port9 of Fortigate I see 6 packets.. What is happening? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From a laptop I am injecting six ICMP packets (three request packets and three response packets) to reach an interface of a Fortigate firewall (port 9).
The problem is that for some unknown reason the request packets do not reach the Fortigate interface (the command diagnose sniffer packet port9 does not display the packets),
If it injects the traffic to another laptop, I do receive both the requests and the replies. This behavior occurs with other protocols (UDP, TCP), outbound traffic does not arrive.
I have opened a case with Fortigate and the blame is placed on tcpreplay.
The fact is that I tried with a TAP to see if it was putting the packets on the cable and it was verified. That could be happening?
If I send the packets of SPAN switch to port9 of Fortigate I see all packets (request and reply) .
What is happenning?
The text was updated successfully, but these errors were encountered: