Link to home
Start Free TrialLog in
Avatar of Rupert Eghardt
Rupert EghardtFlag for South Africa

asked on

Configuring the Dell Sonic Wall TZ400 W

Hi Guys,

I am in the process of setting up a Dell Sonic Wall router TZ400 W

On our LAN, we are using a 10.0.0.x /24 range.
And I've added the router's X0 interface to our LAN range.

If I want to include W0 (wireless interface) on the same range, it tells me Subnet on this interface overlaps ...

It allows me to put W0 on a completely different range, (example 172.16.1.1)
Does this mean W0 will automatically use a different DHCP range - provided if it matches 172.168.1.x?

I have a DHCP range 10.0.1.100 - 10.0.1.150 /16 and I would ideally like to use this range for the wireless clients?
Avatar of Rupert Eghardt
Rupert Eghardt
Flag of South Africa image

ASKER

I've changed the W0 interface to Layer 2 Bridged Mode,
It now uses the same range of the X0 interface.

I've changed X0 IP range to 10.0.1.1 /16
However, the DCHP address (connecting to the W0 interface) is now being provided by our main DHCP server on 10.0.0.22 /24

Although a DHCP range of 10.0.1.100 - 10.0.1.150/16 is available from the router, it is not being used.
Avatar of Blue Street Tech
Hi Rupert,

Yes, you are correct here, it will have a different DHCP scope:
It allows me to put W0 on a completely different range, (example 172.16.1.1)
Does this mean W0 will automatically use a different DHCP range - provided if it matches 172.168.1.x?
. SonicWALL sets up the wireless in a separate network because it is a better security model to do so. The LAN is trusted the WLAN is not. Unless you have a requirement to bridge them I'd keep them separated. You'll have better security controls with them segregated.

Layer 2 Bridge is the only way to achieve having the LAN and WLAN in the same network/subnet.

have a DHCP range 10.0.1.100 - 10.0.1.150 /16 and I would ideally like to use this range for the wireless clients?
Does this mean you only want the Wireless to have 110-150 and the rest of the LAN to have a scope beyond that?

I've changed X0 IP range to 10.0.1.1 /16
However, the DCHP address (connecting to the W0 interface) is now being provided by our main DHCP server on 10.0.0.22 /24

Although a DHCP range of 10.0.1.100 - 10.0.1.150/16 is available from the router, it is not being used.
In bridge mode you are treating two network like one so you will only have one DHCP scope for the entire range. I don't understand the question or the problem here. You have to pick which DHCP server is going to provide the scope either your Windows Server or SonicWALL and then make the appropriate configuration therein.

Let me know how it goes!
Thank you Diverseit,

The DHCP LAN scope has been 10.0.0.100 - 150/24.
I've setup the new DCHP scope of 10.0.1.100 - 150/16

... in the hope that the router will use it's own DHCP scope, but I realise that it is likely not possible, as it is one network.

I agree that a better approach is to have the wireless network on a seperate range, such as 172.16.1.1 /16
However, how will this impact on the network resources, such as shared folders and printers?
ASKER CERTIFIED SOLUTION
Avatar of Blue Street Tech
Blue Street Tech
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've setup W0 (WLAN) on IP range 172.16.1.1/16
Created an access rule WLAN -> LAN
However, wireless clients unable to access any network resources from LAN

Wireless clients can access the internet from WAN = OK

There is no NAT rule in NAT table for W0 (WLAN) -> X0 (LAN)
I am unable to create a new NAT rule, it says "A duplicate policy exists"
There is not policy for W0 -> X0?