Skip to main content
SilentDude
New Member
August 26, 2019
Question

Allowing LAN Internal Network To A DMZ Device

Hello People,

 

User asked me to allow lan network to access a dmz device ip: 10.10.10.50

lan ip-range is 192.168.100.110-192.168.100.210 gateway: 192.168.100.99

 

1- i went to addresses > create new> i didnt find a place to create an object for dmz device 10.10.10.50

so the first question question how do i create an object and give it a name and an ip address. what i found is to create subnet and ip range and this is not what i was looking for.

i need to create this dmz object because i want to allow lan only to this dmz machine. how do i do that in forti.

 

2- what i did for now for testing is allowing lan to all dmz network, even this didnt work and i dont know why...

i went to policy and objects > addresses > created 2 new ip range pbjects

name dmz-network and name internal-network ip ranges.

then i went to ipv4 policy > create new

name: lan_to_dmz

incoming interface: internal

outgoing interface: dmz

source: internal network

destination: dmz-network

shedule: always

service: all

action: accept

nat: disabled

 

when i went to a pc in lan tried to ping 10.10.10.50 there was no ping?

how do i go from here? please assist.

    4 replies

    sw2090
    SuperUser
    SuperUser
    August 26, 2019

    what did you put into your ranges?

    you can enter one host as a subnet wih <ipofhost>/255.255.255.255 as a FGT Address object.

    If 10.10.10.50 is the ip of the dmz interface, does the interface allow ping?

    Is that dmz_network connected to the dmz interface?

    SilentDude
    New Member
    August 26, 2019

    Hello,

     

    ok i create the dmz object.

    10.10.10.50  is a device in dmz network listening on port 80

    10.10.10.1/255.255.255.0  dmz interface

     

    i need to allow ALL lan Computers to access one specific device in dmz 10.10.10.50 on port

    when they open a browser lan users type: 10.10.10.50  and they should reach a web interface.

    lan interface is: 192.168.100.99

     

    hope its more clear now.

    sw2090
    SuperUser
    SuperUser
    August 26, 2019

    hm ok

    your policy seems to be correct so far. 

    If you enable ping access on your dmz interface and then try to piing 10.10.10.1 from out of you lan ip range - does that work?

    Do you have any other policy that matches that traffic and comes before this one?

     

    For further debug you might use the debug package flow feature on cli:

     

    diag debug enable

    diag debug flow show console enable

    diag debug flow filter clear

    diag debug flow filter daddr 10.10.10.50

    diag debug flow trace start <numberofpackets>

     

    then ping 10.10.10.50 and watch the console. You will see the incoming ping (ICMP Echo) and you will see what happens to it.

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT