IP Range 1

[scmiller]

Hello! I am relatively new to network administration and I am setting up a Checkpoint Edge device. I am trying to setup the device to doll out IP addresses based on whether it is connecting via a hardwire or wireless.

If the PC is connected via a hardwire, I would like to assign the following range:

192.168.16.3 to 192.168.16.59

If a Pc connects wirelessly, I would like to assign the following range:

192.168.16.60 to 192.168.16.100

Both subnet masks are 255.255.255.0.

I can setup the hardwire portion, but when I go to setup the wireless portion it tells me the range is in use. Sorry for the lack of info, but I'm not sure what I am doing wrong...

Steve

 

[John Lewis]

I am not specifically familiar with this device, but I can give you an educated guess.

It appears that the wireless and wired networks are two distinct interfaces and must have two distinct network addresses. You are trying to assign portions of a single network to the two interfaces, which simply will not work.

Your options would be to use 192.168.17 (or similar) for one of the networks or change your network mask to 255.255.255.128 to split the network into two parts. The first solution would be preferred, as some network gear tends to ingore the netmask when you are using 192.168 addresses, so you may end up with a real mess if you try to deviate from the standard 255.255.255.0.

 

[LawnBoy]

...some network gear tends to ingore the netmask when you are using 192.168 addresses...

Oh really! Care to say which gear, so I can avoid them?

 

[John Lewis]

Mostly early, cheap gear. Older Liknsys products were offenders. I also recall an Allied Telesyn router (which was not cheap) having the problem.

The term "gear" is probably a bit too narrow, as Microsoft Windows NT (pre 4.0 SP2) also had the problem under certain circumstances.

 

[fartingfrog]

Anything running RIP version 1 or IGRP as the routing protocols (unless it's an AppleTalk network) will only route in classful boundaries, because subnet mask information is not passed along in the routing tables. These are the routers/devices that will not differentiate between different subnetted addresses. So there.

Tim

 

[Frank4d]

We had some Agilent JTAG emulator probes that could not be connected to any computers on our network unless the Agilent JTAG emulator probe subnet mask was 0.0.0.0.