|
Written by Start a WISP Site Admin
|
|
Monday, 17 July 2006 |
" I hope there is a super simple solution here that I am just failing to see... but here goes:
If I wish to place 2 APs on separate subnets (eg. 192.168.10.x and 192.168.20.x) and my pc is on the 20.x subnet, how do I monitor and manage the client radios on the 10.x subnet without physically travelling to where I can associate with the 10.x subnet?
Can a client pc be on a different subnet than it's CPE and AP?(I just finished trying this with a pfSense box and failed) I am thinking it might be good to have all the monitored devices on one subnet and all the PCs on their own subnet."
IntraLink:
Are you routing?
If you are bridged then you need that all the subnets on your machine that you are using to access the devices.
If you are routed then you need to add a route to get between subnets.
It is a good idea to keep the client machines on a different subnet than the CPE, AP and other devices (which would be to use an internal subnet).
inova (original submitter):
Currently I am bridged, explicitly on Deliberant 23xx radios and without option on CB3s. My failure mentioned in my first post was that the client pc could not obtain a dhcp lease from the pfSense box when the bridging AP and CPE were on a different subnet(I am just testing this arrangement using the clients on one AP as guinea pigs). I assume this is possible and therefore my problem must lie elsewhere. The only router employed normally is at the NOC, many miles from me and the other APs. How do you put multiple subnets on one machine? Do you need multiple NICs? I am at a point where I can see I need to get better organized. I doubt I will ever see 100 clients but it seems like a good number to plan around.
kf6ytc:
do you mean segments or subnets?
192.168.1.x is a segment
255.255.255.0 is a subnet
inova:
I think I mean subnet. I thought that 255.255.255.0 was a subnet mask while a segment was a physical grouping and a subnet was a logical grouping. 2 separate segments of the same network could have the same subnet if they were behind there own routers, correct?
PersComp:
The simplest way to be able to access across the segments, is to loosen the subnet mask to 255.255.0.0 and you are no longer masking the segments from each other.
Original thread location |
Equipment and Network Configuration 
