It's been ages (and many, many OS versions ago) since I've had to do this so I'm stumbling. I need to connect two subnets, 192.168.5.0 & 10.168.2.0. I'd also like to have the SonicWall provide a seperate DHCP server for VLAN 2. Please help!
What sonicOS are you running?
Are these subnets in the same zone?
My instructions make use of the sonicwall website rather than using the cli.
To allow access to between the two subnets, you need to create a rule in the firewall allowing access between the two.
If 192.168.5.0 and 10.168.2.0 are both in the same zone then in the firewall access rules select from LAN to LAN and make sure you have a rule allowing traffic to cross. It could be as simple as allowing ANY source ANY destination and ANY service to pass through the firewall.
If 192.168.5.0 is in the LAN zone and 10.168.2.0 are in a LAN2 zone then essentially the same thing applies. Go the firewall access rules and select from LAN to LAN2 and then create a rule allowing traffic through. Now youll need to go back to the access rules and choose the reverse direction - from LAN2 to LAN and then create a rule allowing traffic through. Now both subnets can communicate.
As for the dhcp setup:
I'm going to assume that 192.168.5.0 is tied to X0 interface and that 10.168.2.0 is tied to the X0:V2 interface. I'm just clarifying which subnet is the main lan and which is the vlan.
To setup the dhcp server go to the Network tab and then choose DHCP server.
Ensure that you have the dhcp server enabled. When it is turned on, at the bottom of the page is an add dynamic button. Click this button. It pulls up a new Dynamic Range Configuration window. The key part here is to check the Interface Pre-Populate button and then select X0:V2 and it will pre-populate most of the information needed. At this point you can continue to tweak settings or just click ok.
Now you should see in the DHCP server lease scopes table a new entry.
It should look something like this:
1 Dynamic Range: 10.168.2.2 - 10.168.2.254 X0:V2
and there should also be section displaying the durrent dhcp leases that are out.
Hopefully that should do it. Again if you arent using a version close to the two I listed some parts of the process maybe a little different.
Yes, they are in the same zone. That firewall access rule was already set and enabled. Any other thoughts? One other tidbit...192. is VLAN1, and 10. is VLAN2.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.