Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
theoleek
New Contributor

Load test packet loss

I am try to load test FortiGate VM using cisco Trex. While this works perfectly on the current pfsense setup, I cannot get it to work on FortiGate.

 

Simple routing and firewall rules have been set up the same as pfsense and  can see that the one firewall rule is beng used based on the bandwidth usage. When looking at foward traffic logs it seems that some traffic is getting through fine but the majority of traffic does not seem to be accepted as is mostly droppped.

 

I have tried the following so far;

 

  • Using Policy routes rather than static routes produces the same result
  • Change the interface types from unspesified to WAN or LAN
  • Added DoS policy, no change
  • Changed NAT settings in firewall rules
  • Changed protocol options in firewall rules

 

Looking at forward traffic it seems that traffic that is having issues is the following

Duration5
Session ID63,877
VDOMroot
NAT Translationnoop
 
Source
Source16.0.0.14
Source Port5,796
Source Country/RegionUnited States
Primary Source Mac00:0c:29:93:42:f3
Source Interface
 
port1
 
Destination
Destination48.0.7.7
Destination Port80
Destination Country/RegionUnited States
Destination Interface
 
port2
 
Application Control
Application NameHTTP
Categoryunscanned
Protocol6
ServiceHTTP
 
Data
Received Bytes33.02 kB
Received Packets23
Sent Bytes813 B
Sent Packets14
 
Action
Actionclient-rst
Security Action 
Policy ID
0to1
Policy UUID57417294-aca1-51ed-d32e-e59d083a0abd
Policy TypeFirewall
 
Security
Levelnotice
 
Cellular
ServiceHTTP
 
Other
Log event original timestamp1676410894150044700
Timezone+0000
Log ID0000000013
Typetraffic
Sub Typeforward
Source Interface Rolewan
Destination Interface Rolelan
Policy Name0to1
Source Server0

 

 

30 REPLIES 30
adambomb1219
SuperUser
SuperUser

Is the VM licensed?  Any Inspection profile configured in the firewall policy?

theoleek

The VM has a free lisence and is registered yes. Here is the fireall rules and not inspection or security rules are used.

 

port1 →port2

 

1to0
 
all
 
all
 
Disabled
 
ACCEPT
 
All
 
always
 
ALL
 
no-inspection
 
18.64 MB
 
 

 

port2 →port1

 

0to1
 
all
 
all
 
Disabled
 
ACCEPT
 
All
 
always
 
ALL
 
no-inspection
 
0 B
 
gfleming
Staff
Staff

Source IP 16.0.0.14. Do you own this address? If not it might not get routed back to you properly.

 

Can you further explain the actual flows you are trying to get working. Does the FortiGate connect to an actual ISP or is this all internal testing? What kind of traffic does trex generate? Does it all go to the same destination or multiple?

Cheers,
Graham
theoleek

Thank you for having a look Graham. So the setup is as follows.

 

TREX port0-------->FortiGate port1         FortiGate port2 -------->TREX port1

11.11.11.10/24                 11.11.11.20/24              12.12.12.20/24                   12.12.12.10/24

 

 

Routes are

16.0.0.0/8
11.11.11.10
port1
 
Enabled
48.0.0.0/8
12.12.12.10
port2
 

Trex sends packets with Source IP 16.0.0.0/8 and destination 48.0.0.0/8 out of port0

It then sends Source IP 48.0.0.0/8 and destination 16.0.0.0/8 out of port1

 

Cheers

 

gfleming

Are all of the log messages showing action of "client-rst"?


This implies there is a TCP Reset being sent by the client, or the source, for that TCP session.

 

Can you check your logs and see if you see any other actions?

Cheers,
Graham
theoleek

Some packets seem to be fine, for example

 

Source
Source16.0.0.13
Source Port53,921
Source Country/RegionUnited States
Primary Source Mac00:0c:29:93:42:f3
Source Interface
 
port1
OS NameWindows
 
Destination
Destination48.0.1.12
Destination Port80
Destination Country/RegionUnited States
Destination Interface
 

port2

 

which comes back as

Actionip-conn

 

 

gfleming

Considering this is a VM, have you ensured your VM Guest config is accurate and properly set up for the FortiGate-VM? 

 

Have you confirmed connectivity from the FortiGate to both sides of the Trex appliance?

 

From FortiGate CLI can you ping out from both port1 and port2 to either port on the Trex?

 

"execute ping <IP address>" is the CLI command to run.

Cheers,
Graham
theoleek

No, the FortiGate is unable to ping the TREX ports and TREX is unable to ping the FortiGate ports. This is the same behaviour with pfsense. When TREX first starts it sends ARP packets to the FortiGate ports which works as TREX then starts sending traffic.


This is setup on ESXi 6.5 using VMXNET3 adaptors and is using 2 seperate virtual switches for the connections between them, promisucous mode enabled.

 

I have reinstalled a fresh copy of FoirtGate and simply added interface IP's, added static routes, and added the firewall policy and still getting the same result. TREX reports packets drop after 10 seconds of test traffic.

gfleming

What version of FortiOS are you running?

 

And you've confirmed compatibiliy? https://docs.fortinet.com/document/fortigate-private-cloud/7.2.0/vmware-esxi-administration-guide/23...

Cheers,
Graham
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors