On 04/08/2010 11:44, (Ted Harding) wrote:
On 04/08/10 10:44, Adam Bower wrote: In my case, it's just that it makes sense to have my "primary" IP address given to me by the office DHCP server - it means we can change settings (eg DNS, etc) globally nice and easily. But I also need to be able to configure hardware which will come in with known default IP addresses, so I will need to be able to reach, for example, 192.168.10.1, regardless of what the rest of the network looks like.
Coming in late on this (and also no expert on all details of network configuration [conflagration?] ... ).
I recall, in the past, having done this sort of setup, but in a way which depends on configuring the DHCP server to *not* hand out IP addresses in a certain range. Addresses in this range can then be used as fixed IP addresses for machines that want them (these having already been configured to use fixed IP and not request dynamic IP from the DHCP server).
So you might exclude 192.168.10.1-50, say, and allow dynamic IPs above this range.
Doing this depends on configuring the DHCP server, so how to do it depends on what is involved in that. Once done, however, for any other machine it is then simply a matter of either configuring it to use a set fixed IP address, or configuring it to request a dynamic one -- and of course from time to time you can switch between these options if need dictates.
Another option - assuming you have control of the DHCP server - is to tell it to assign permanent or indefinite leases to particular MAC addresses. This is what I do at home to ensure that my laptop (and several other devices) always have the same address whenever they connect to WiFi, even though they still use DHCP to get their addresses. Result: [effectively] static addresses managed by DHCP, and no furtling around with individual ipconfigs, etc, required.
Simon