Discussion Locked

Subnetting wireless networks to segregate private and public nets

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm trying to setup a new wireless network to make available for
'public' assess in our church. We currently have the private network
hooked up to a wireless network and encrypted. It is using the
192.168.0.x subnet. I'm trying to setup the other access points as
192.168.1.x (1-5 for the different areas of the building) and a
wireless router that the WAN port is connected back to the wired
network. It is set to use DHCP to acquire an address from our DHCP
server, which it does, and the gateway on the wan port is the cable
modem at 192.168.0.1 . The LAN side of that router is set at
192.168.1.1 and has the DHCP enabled to hand out addresses in the
192.168.1.x range for users that connect to the public network.

My stream of thought on how I expect it to behave;
1) Wireless client connects to the public network access point which
has an IP address of 192.168.1.x and looks for a DHCP server.
2) Since the WAP is on the 1.x network it sees the 192.168.1.1 DHCP
server in the router and gets a 192.168.1.x IP address for the client.
3) Since the subnet mask on that DHCP server is 255.255.255.0 the 1.x
clients do not see our servers on the 0.x subnet.
4) Since the WAP that they are connecting to is on the 1.x subnet, the
can't see the DHCP server we have on the 0.x subnet and will always get
their IP from the 1.x DHCP server on the router.

This doesn't seem to be working out however, so I'm interested to hear
if there is any inherent flaw in my reasoning that I am missing...

It DOES appear that if the public user DOES get the 1.x address, they
can in fact not see the servers, however, for some reason, it seems
that on on occasion they will get a 1.x on the next they will get a 0.x
. Worse still, our internal users have gotten 1.x addresses and found
themselves unable to get to the servers...

Thoughts????

Thanks.

Mick

3 replies

by jmgarvin

I'd do three things for your internal network:
1) MAC Filter. Only allow on specific MAC addresses to the 192.168.0.x network.
2) Don't broadcast your SSID.
3) Create a subnet mask that fits only the number of computer that you have on your internal network (eg if you have 3, only allow 3 computers on)

by anleath1

Set up an ACL list for your internal network, and set the internal PC to only connect to the internal SSID network

by mfahlsin

From what you describe the only scenario I could envision where this would be a problem is: a. only wireless clients are having problems with receiving the wrong subnet IP address and the cause would be b. both networks are using the same SSID. Otherwise what you describe, setting up the public wireless network behind a router and on a separate subnet should not cause clients to swap back and forth between IP ranges. However, if I understand you right, you are routing the public WLAN onto the private LAN in order to reach the internet gateway. If you want to secure your private LAN, you should set it up the other way; where your private LAN routes onto the public one to access the internet or place a firewall/router in front of the gateway that allows you to assign the WLAN to it's own zone (or VLAN) and ensure the firewall blocks traffic from that VLAN to the LAN.

This discussion is closed to new replies.