Results 1 to 1 of 1
Hi All, My home network is connected to the Internet via a Cayman 3397 router with which I have subnetted the usual 192.168.1.0/24 network into eight smaller 192.168.1.0/27 networks (i.e., ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-31-2009 #1
- Join Date
- Aug 2009
Cayman DHCP broadcast problem, or is it ?
My home network is connected to the Internet via a Cayman 3397 router with which I have subnetted the usual 192.168.1.0/24 network into eight smaller 192.168.1.0/27 networks (i.e., .1.0, 1.32, etc.) The documentation is poor for the device I have but it seems that for each subnet I must define an "IP address" (i.e., not the network address) on the basis of which DHCP services can be provided e.g., for the 192.168.1.32/27 network the network address is 192.168.1.32 and the "IP address" is 192.168.1.33 which appears to be an alias of 192.168.1.1
Here is my problem: when I use the Cayman DHCP a typical Linux host gets configured to be on the 192.168.1.0/27 subnet has a broadcast address of 255.255.255.255 and a (correct) netmask of 255.255.255.224 (DNS servers and gateways are also correctly passed to the client by the router.) At this point what I would have expected was that the broadcast address be 192.168.1.31. If I replace the Cayman with a Cisco router this is exactly what I get but unfortunately I must use the Cayman as my access router (owing to local telco contractual requirements)
Am I correct in assuming that there is a problem with the Cayman router DHCP service that is making the broadcast address "too wide" i.e., will an address of 255.255.255.255 cause be broadcast domain collisions and similar ?