FortiDeceptor, Monitor IP and Decoy IPs not reachable

Forum|Forum|1 year ago
October 28, 2024
1 reply
1801 views

Hello,

I deployed fortideceptor version 5.3.0. But I don't have access from anotether networks to fortideceptor even though create firewall rule. This issue isnt related vm nic card, vm use vmxnet. Also I configured vmware port group proparties like promiscuous mode, mac address changes and forged transmits. If I try to send ping from fortideceptor mgmt ip to a deployment network monitor ip it fails. But if I open nat in policy, it will be success. Where could I have gone wrong?

FortiDeceptor

AEK

SuperUser

Hi Celik

Since it works with NAT then this is clearly a routing problem, and is not specific to FortiDeceptor.

As you have set the default route through the MGMT interface, that means when you ping the VM on its second port, the VM will try to reply from the MGMT interface, which is blocked by the firewall.

If you set the default gateway through the second interface you will fix the issue, but in that case you will have the same issue on MGMT.

AEK

h_celikAuthor

New Member

I added a new network card to deceptor. This card is tagged to vlan 18 in vmware for example. I selected this port in the deployment network settings. I don't know if it's because I tried a lot, but fortigate had a lot of macs for some ip. I removed the ones I didn't understand, but I couldn't see in the device inventory that any mac address was created in the firewall for the monitor interface.. I pinged the monitor interface from Deceptor and started packet sniffing in the firewall. I saw an arp query coming, but there is no mac address to tell in the firewall

Last time I tried it, I got ping when I turned on nat, but now there is no ping.

Monitor interface ip: 10.10.0.5

Deceptor port3 ip: 10.10.0.4

h_celikAuthor

New Member

I updated from version 5.3.0 to 6.0.1 and it worked

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded