Hi All,
I have trouble debugging my FG200E. Maybe someone here can open my eyes... I have a Virtual Server: IP: 192.168.60.100 Virtual Server Port: 443 Round Robin Real Servers: 192.168.60.11:5601, 192.168.60.12:5601
The Subnet 192.168.60.0/24 exists and is bound to a VLAN-Interface (VLAN60) on my Fortigate (192.168.60.1).
I wan't to access this Virtual Server from another subnet (192.168.102.0/24) which is on a VLAN-Interface (VLAN102) of my Fortigate (192.168.102.1).
I created a rule
from Interface VLAN102 Source 192.168.102.0/24
to Interface VLAN60 Destination VirtualServer 192.168.60.100
Service 443
But theFortigate keeps on telling there is no Rule matching. I played around with the rule but it always ends up telling me there is no rule matching. How does the rule have to look like?
Thanks a lot!
hmmm sounds correct so far (alas you have not posted the exact configuration).
Where does it say no rule matched? This is not possible because there is always but one route that matches any packet - namely policy #1 which blocks everything. So if none of the other policies matched #1 will and you get blocked then.
Did you try a flow trace to debug it on cli?
If your policy did not match you have to find out why. Is the port not corret? Did it start with 443 but then use something else?
Probably remove the service limitation from your policy to see if it matches without...
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
Hi and thanks for your answer!
I played around again but no changes... And of course you are right, there is a policy matching: The default deny rule.
Here are some details:
config system interface
edit "VLAN60"
set vdom "root"
set ip 192.168.60.1 255.255.255.0
set allowaccess ping
set role lan
set snmp-index 23
set interface "VLAN Trunk"
set vlanid 60
next
end
config system interface
edit "VLAN104"
set vdom "root"
set ip 192.168.104.1 255.255.254.0
set allowaccess ping
set device-identification enable
set role lan
set snmp-index 53
set interface "VLAN Trunk"
set vlanid 104
next
end
config system interface
edit "VLAN102"
set vdom "root"
set ip 192.168.102.1 255.255.255.0
set allowaccess ping
set device-identification enable
set role lan
set snmp-index 51
set interface "VLAN Trunk"
set vlanid 102
next
end
config firewall vip
edit "Kibana"
set uuid 490c11e2-4fb4-51e8-23bd-d2f8d97339b4
set type server-load-balance
set extip 192.168.60.100
set extintf "any"
set server-type https
set monitor "Kibana_HealthCheck"
set ldb-method round-robin
set extport 443
config realservers
edit 1
set ip 192.168.60.11
set port 5601
next
edit 2
set ip 192.168.60.12
set port 5601
next
end
set http-multiplex enable
set ssl-mode full
set ssl-certificate "star.mydomain.com"
next
end
config firewall vip
edit "anchoreEngine"
set uuid 78fa9c8e-72fa-51e8-5c63-96f28400ceb6
set type server-load-balance
set extip 192.168.60.101
set extintf "any"
set server-type https
set ldb-method round-robin
set extport 443
config realservers
edit 1
set ip 192.168.60.11
set port 8228
next
end
set http-multiplex enable
set ssl-mode full
set ssl-certificate "star.mydomain.com"
next
end
config firewall policy
edit 100
set name "LAN to Kiba"
set uuid 4e477c1e-4fb4-51e8-b23a-1dd609fc1c3b
set srcintf "VLAN102" "VLAN104"
set dstintf "any"
set srcaddr "Office: VLAN104 Subnet" "Office: VLAN102 Subnet"
set dstaddr "anchoreEngine" "Kibana"
set action accept
set schedule "always"
set service "HTTPS"
next
end
2018-10-10 11:30:47 id=20085 trace_id=4096 func=print_pkt_detail line=5320 msg="vd-root:0 received a packet(proto=6, 192.168.102.12:54318->192.168.60.100:443) from VLAN102. flag , seq 2492908065, ack 0, win 29200"
2018-10-10 11:30:47 id=20085 trace_id=4096 func=init_ip_session_common line=5480 msg="allocate a new session-1747743c"
2018-10-10 11:30:47 id=20085 trace_id=4096 func=fw_pre_route_handler line=182 msg="VIP-192.168.60.11:5601, outdev-unkown"
2018-10-10 11:30:47 id=20085 trace_id=4096 func=__ip_session_run_tuple line=3240 msg="DNAT 192.168.60.100:443->192.168.60.11:5601"
2018-10-10 11:30:47 id=20085 trace_id=4096 func=vf_ip_route_input_common line=2590 msg="find a route: flag=04000000 gw-192.168.60.11 via VLAN60"
2018-10-10 11:30:47 id=20085 trace_id=4096 func=fw_forward_handler line=597 msg="Denied by forward policy check (policy 0)"
Thanks for your Help!
hmm looks good so far.
You packet trace says it got the packet and it got where to go so your interface configs should be correct.
Could you please additionaly post the config of your vlan trunk interface and the address objects?
"Office: VLAN104 Subnet" "Office: VLAN102 Subnet"
"anchoreEngine" "Kibana"
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
Sure, here you are:
config system interface
edit "VLAN Trunk"
set vdom "root"
set type aggregate
set sample-rate 500
set polling-interval 30
set member "port2" "port3"
set snmp-index 29
next
end
config firewall address
edit "Office: VLAN104 Subnet"
set uuid da29c7c4-c35d-51e8-5330-f2b884396bcd
set subnet 192.168.104.0 255.255.254.0
next
end
config firewall address
edit "Office: VLAN102 Subnet"
set uuid 8ff305d2-c365-51e8-67c5-4ed1be129901
set subnet 192.168.102.0 255.255.255.0
next
end
These are no address objects, but Virtual Servers:
config firewall vip
edit "anchoreEngine"
set uuid 78fa9c8e-72fa-51e8-5c63-96f28400ceb6
set type server-load-balance
set extip 192.168.60.101
set extintf "any"
set server-type https
set ldb-method round-robin
set extport 443
config realservers
edit 1
set ip 192.168.60.11
set port 8228
next
end
set http-multiplex enable
set ssl-mode full
set ssl-certificate "star.mydomain.com"
next
end
config firewall vip
edit "Kibana"
set uuid 490c11e2-4fb4-51e8-23bd-d2f8d97339b4
set type server-load-balance
set extip 192.168.60.100
set extintf "any"
set server-type https
set monitor "Kibana_HealthCheck"
set ldb-method round-robin
set extport 443
config realservers
edit 1
set ip 192.168.60.11
set port 5601
next
edit 2
set ip 192.168.60.12
set port 5601
next
end
set http-multiplex enable
set ssl-mode full
set ssl-certificate "star.mydomain.com"
next
end
Thanks for your help!
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1737 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.