Mailinglist Archive: opensuse (882 mails)

< Previous Next >
Re: [opensuse] [slightly OT:] DHCP and Windows (yuck...)
  • From: Anton Aylward <anton.aylward@xxxxxxxxxx>
  • Date: Mon, 13 Dec 2010 10:22:42 -0500
  • Message-id: <4D063A42.1030804@xxxxxxxxxx>
Roger Oberholtzer said the following on 12/13/2010 09:42 AM:

Then I'd try configuring it as a relay agent -- yes I know its on the
same segment and isn't a router -- to the Linux server.

Interesting. Go on...

Plenty there if you google -- better than I can explain in a few words


Finally I'd think about using MAC addresses in the configuration,
possible with a split subnet.

It is a subnet. It cannot be divided any more. At least not without
making more and different problems. It is a VLAN between two offices and
some equipment in the main server room.

Yes it can.
First: use of MAC address can constrain who responds to what.
Second you can have things like the following to restrict the range of
the DHCP server and thereby 'subnetting' further

#
subnet 192.168.1.0 netmask 255.255.255.192 {
range dynamic-bootp 192.168.1.20 192.168.1.32 ;
group {
# PXE-specific configuration directives...
# option dhcp-class-identifier "PXEClient";
filename "pxelinux.0";
next-server 192.168.2.18;

host BB0001 {
hardware ethernet 00:00:00:XX:XX:01 ;
fixed-address 192.168.1.15 ;
option domain-name-servers 192.168.1.1, 192.168.2.1;
}
........
}
......
}


How you get that, or the other half of the 'subnet'
into the Microsoft server I don't know.

But then again, since I use Linux to run things, even with SAMBA when I
am forced top have Windows machines on the LAN, I find I can run even
the Windows need for DHCP from Linux. Are you sure you can't just turn
the Windows DHCP off?

--
Never forget: The road to Hell is paved with good intentions.
So tread hard on good intentions. -- rjd4
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups