Skip to main content
Contributor
November 23, 2007
Question

putting wireless router on dmz

  • November 23, 2007
  • 14 replies
  • 8536 views
I know you should always try something before asking, but I am not on site yet. I have a new FG60B going in on a network this weekend. internal interface is 192.168.0.99 DHCP enabled on my FG60 Internal interface. We have some wireless laptops we want to access the internet but nothing else. We have an d-ling DI-624 wireless router, I wanted to put on the DMZ port of my FG60B. network/interface/dmz enabled but no values assigned. Any assistance greatly appreciated to get ths going.

    14 replies

    FortiRack_Eric
    New Member
    November 25, 2007
    This should be pretty straighforward. Configure a seperate network segment on the DMZ like 172.16.0.1/24 disable DHCP on the wireless router. Enable DHCP on the DMZ port. range 172.16.0.20 - 172.16.0.99. Gateway and DNS server 172.16.0.1 Enable DNS forwarding from DMZ Add fw rule from DMZ to Wan1. configure the services you want to allow and attach protection profile. If you allow anybody to access your access point with no security it would seriously recommend to have strict protection profile and disallow SMTP. Cheers, Eric
    Contributor
    December 19, 2007
    I have followed the steps as outlined by Eric. I set the lan of the D-Link to 172.16.0.10 My laptop gets an IP. but no web surfing?
    rwpatterson
    New Member
    December 19, 2007
    Check that the policy from the DMZ to external has NAT enabled. Run a trace from the laptop to see how far traffic gets before it fails.
    Contributor
    December 19, 2007
    Thank you Bob, that sorted it all out!
    Check that the policy from the DMZ to external has NAT enabled.
    Contributor
    January 16, 2008
    Trying to do the same thing and I just cannot figure this out. Maybe I just don' t understand this router well enough. It' s a Fortigate 60, which I love. This thing has been rock steady. I have everything else setup just fine, though, and has been for more then a year. Never used a DMZ before, although I certainly understand what it is and what it' s used for. Help?!? This is what I' ve done. System > Network > dmz Bring Up > Edit Set ADDRESSING MODE > Manual - IP/Netmask This should be set to whatever the router is, no? or is this the " Separate Network Segment" Eric was referring to? Firewall > Virtual IP Create New > Name - DMZ Static NAT External IP is 66.*.*.* - an external ip addy that I own Mapped IP is set to the IP of the router. " Enable DHCP on the DMZ port" . No idea where to do this. System > DHCP > dmz > Relay ... but it wants an address? Can' t I just use the DHCP server from the Linksys wifi router I am trying to set up? Then I went to System > Firewall > Policy Create New & Enable. Source - dmz - all Destination - wan1 - all, always, any, accept NAT - checked My apologies for asking what should be a simple question, but I' ve spent far to much time trying to figure this out now, and I give up. Any help sincerely appreciated. Thanks for your time. Tony
    rwpatterson
    New Member
    January 16, 2008
    Jeeez, there are a bunch of questions here.[ul]
  • Is the IP address on the FGT DMZ on the same subnet as that of the wireless device? (192.168.x.y/255.255.255.0 The x must be the same on the FGT and the wireless router)
  • Is the IP address on the wireless router a DHCP address or a hard coded one?
  • Who will be serving DHCP addresses? [/ul]On to the debugging... Can you ping the wireless device from the FGT? Can wireless devices ping the FGT? If the wireless router is serving DHCP addresses to it' s clients, you do not need to use the DHCP server on the FGT. That would be a good thing. Less complicated. Just make sure that you allow the address range that is being served access to the Internet. The VIP you created is only good for letting public entities into your network to the private server. Get rid of that. My suggestion: Let the Linksys serve out the DHCP addresses. Configure the Linksys to 192.168.x.1(/255.255.255.0). Configure the DMZ port on the FGT to 192.168.x.255(/255.255.255.0). Set the default gateway in the DHCP server on the Linksys to match the IP address on the FGT DMZ port. Plug the INSIDE port on the Linksys to the DMZ port, and you should be good to go. As far as DNS goes, I believe you could point it to the FGT as well, and the FGT will pass the traffic on to it' s defined DNS servers. That you' ll have to try out for yourself. If you kow your ISP' s DNS servers, insert them manually into the Linksys DHCP server. Good luck
  • Contributor
    January 29, 2008
    Just wanted to say thanks for trying to help. Have been really sidetracked by some other stuff and haven' t been able to get back to this. I appreciate the time you gave to help me, and I will revisit this very soon. Thanks again!
    Contributor
    January 29, 2008
    Let the Linksys serve out the DHCP addresses. -Done. That' s what I intended. Configure the Linksys to 192.168.x.1(/255.255.255.0). - I used 172.168.1.1 My internal network is using 192 so I want completely different ip' s for the wifi. Configure the DMZ port on the FGT to 192.168.x.255(/255.255.255.0). - Do you mean 192.168.1.1? Didn' t think I could use .255? In fact, I try and it tells me I cannot. INVALID IP. System > Network > Edit DMZ > Addressing Mode = Manual and enter ip there. Again I used 172.168.1.1/255.255.255.0 Set the default gateway in the DHCP server on the Linksys to match the IP address on the FGT DMZ port. - Done Plug the INSIDE port on the Linksys to the DMZ port, and you should be good to go. - No joy. If you kow your ISP' s DNS servers, insert them manually into the Linksys DHCP server. - I did indeed use my ISP' s DNS servers. Got to be something simple I am missing here.
    rwpatterson
    New Member
    January 29, 2008
    Yes, I meant ...254. The Fortigate and the Linksys cannot both have 172.168.1.1. This is why I said set the FGT to ....254. The default GW on the Linksys should be ....254 as well as the DHCP server config. Away you go.
    Contributor
    January 29, 2008
    No joy. I think I know what the issue is. The router I am using is basically your average home-use type Linksys router. Mine. Wanted to make sure I could get this to work before I actually purchase a router for the office. I set the Def GW for the router, but there is no way for me to set the Def GW for the Lnksys DHCP server. These are my choices under DHCP: Local DHCP Server: Enable, Disable Starting Addy # of addys Lease time. WINS That' s it. So I need a REAL router. Need to use the Def #' s. Or need to set the FGT to do all this as mentioned at the top of this thread. Sound right?
    Contributor
    January 29, 2008
    Well, wait... the OP is using a DI-614. That' s the same kind of router. Tried Eric' s method, too. Laptop connects with LIMITED OR NO CONNECTIVITY and a 169.254.. address. - Configure a seperate network segment on the DMZ like 172.16.0.1/24 What is the /24 at the end of that? I used .1.
    rwpatterson
    New Member
    January 29, 2008
    The DI-614 is a very good router. I have a DI-604, and am very happy with it. I do see your issue though. It forces itself to be the gateway. The only other way which may complicate things a bit, would be to turn on DHCP on the DMZ interface (or just hard code the two IP addresses!), and plug the WAN port of the DI-614 into that. This way, the DI-614 will think it' s connected to your ISP, and there will be an interim route betwen your Fotrtigate and the DI. Make sure that the DHCP on the DMZ port is not the same subnet as the one on the inside port of the DI. This should work with a small bit of complictaion due to the new hop in between the two.
    FortiRack_Eric
    New Member
    January 29, 2008
    the /24 is the subnet mask. 255.255.255.0
    rwpatterson
    New Member
    January 30, 2008
    Forgot to mention that. Doh!
    Contributor
    January 30, 2008
    Really feeling like an idiot here. I am trying to set it up as Eric said. This is all correct, yes??
    rwpatterson
    New Member
    January 31, 2008
    Looks 100% to me. Make sure that the D-link is in that same subnet, but outside the range of DHCP address leases.