[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 589
  • Last Modified:

How to create a WLAN that will not see my wired Lan

My network work is laid out like this

T1 Router going into WAN Port on Sonicwall NSA240 and my Server going into the LAN port. I use my server as my DHCP and DNS and have it pointed to the NSA240 as the gateway. I would like to implatment a wireless LAN with Cisco Aeronet 1140 within my building but dont want it to have the same IP Scheme as my wired lan. CAn I setup another network inferface to connect to a switch and provide DHCP on it that interace? If so, how would i do that? If not, what would you recommend the best way to set up the WLAN with it see my wired lan?

wired lan IP is 192.168.XXX.XXX
Want wireless lan IP to be 10.10.XXX.XXX
0
miamitech305
Asked:
miamitech305
2 Solutions
 
Aaron TomoskyTechnology ConsultantCommented:
You can use anther port on the sonicwall and set it up as not Bridged to the LAN. Call it lan2 or WLAN.  Then you can add a dhcp range to the sonicwall for it. It will have firewall rules you can set to get to the LAN if you need to.
0
 
miamitech305Author Commented:
If i set the DCHP range for that port, it wont affect my lan port to my server that is my DHCP?
0
 
Aaron TomoskyTechnology ConsultantCommented:
Nope, it's completely separate from the LAN just like the wan. In fact this is the default behavior for the tz series that has wifi built in.
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
miamitech305Author Commented:
It isnt a TZ series, Its the NSA series.
0
 
Aaron TomoskyTechnology ConsultantCommented:
I know it's an NSA, By telling you that the default for a tz series with wifi is this type of setup I'm just trying to exemplify that this is a common and well supported setup.
0
 
miamitech305Author Commented:
Ok, will my filters that blocks sites be applied to the new port as well? for example, I have facebook.com blocked. Will this site be blocked as well on the new port?
0
 
Aaron TomoskyTechnology ConsultantCommented:
No. Those firewall rules are for LAN->wan. You need to make rules for your WLAN->wan
0
 
Syed_M_UsmanCommented:
why dont you assign one ip @ any free interface of firewall,,, eg x3: 10.10.10.x and assign same range ip to your AP or simply connect your AP directly to SNA-X3...
First check internet once done, go to firewall and create one rule as deny from X3 to LAN.
0
 
miamitech305Author Commented:
If i setup a new port eg x3 with 10.10.10.XXX can port x3 and the lan port both have access to the wan port? If yes do i create a rule that allows X3 to WAN.
0
 
KonsultantCommented:
Hi,

Sonicwall offers their own wireless solution based on SonicPoints. The beauty of this solution is based on the fact that your sonicwall firewall manages all access points (policy, firmware upgrades, etc.) It will deal with wireless VLANs and handle multiple SSIDs. As well as offer IPSec security over wireless with user authentication.

In our case you want to use Cisco wireless as a separate network connected to the firewall as sort of DMZ. This is very simple to do:

1. Create your custom security ZONE line: Cisco_WLAN (I would not use predefined WLAN - as it comes with settings relating to Sonicwall wireless. You may not have best luck with it)

2. I would configure one of the interfaces as dedicated wireless one e.g. X3 could be ours 10.10.10.1 (this will be the default gateway for your wireless)

3. The default NAT policy will take care of the NATing while accessing internet from the wireless network.

4. I would look at the firewall rules and I would mane sure that the default rule Cisco_WLAN to LAN says Deny.

5, You do not need to create any "Allow" type rule from Cisco_WLAN to WAN by default the rule there will be Allow Any to Any.

Honestly there is very little to do. The entire configuration should take you about 5min.

This is pretty much all you have to do.  I have done it many times and it always works.
Keep an eye on the DNS settings while configuring DHPC on the sonicwall. Clients call about problems with wrong DNS all the time. They block access to LAN and at the same time they want to use DNS on the LAN.  Also, keep your DHCP lease short.

Good luck!

P.S. It is not not possible to create rule "from X3 to LAN" X3 will be just one interface with its IP address. Most likely you will need to say X3 Subnet to LAN. If you decide to use dedicated ZONE you will avoid this issue and firewall rules will be more transparent.

Also, make sure that your wireless Cisco uses sonicwall as its default gateway.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now