[opensuse] [slightly OT:] DHCP and Windows (yuck...)
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great. Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files. Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing. I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer said the following on 12/13/2010 08:38 AM:
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Hmm. So you have control over the Windows DHCP server ... If this were me; the first experiment I'd try is cutting it out of the loop altogether. 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. Finally I'd think about using MAC addresses in the configuration, possible with a split subnet. Don't rely on Microsoft being fully compliant with the standard or fully implementing it. -- The quality of a leader is reflected in the standards they set for themselves. -- Ray Kroc, Founder of McDonald's -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-12-13 at 09:04 -0500, Anton Aylward wrote:
Roger Oberholtzer said the following on 12/13/2010 08:38 AM:
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Hmm. So you have control over the Windows DHCP server ...
In so much as we can control what it tells devices on our subnet. But is it subnet-wide, which is causing part of the problem.
If this were me; the first experiment I'd try is cutting it out of the loop altogether.
Not possible. On this network are other windows machines that require the Windows dhcp server. If they were not on this network, then life would be easy. But due to the infrastructure in this building, they need to be on this subnet along with some other equipment.
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...
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. Linux's dhcp server has an option to ignore unknown hosts. We were hoping there could be some option in the Microsoft server to ignore specific MAC addresses. No joy.
Don't rely on Microsoft being fully compliant with the standard or fully implementing it.
I know. This is what bothers me.
-- The quality of a leader is reflected in the standards they set for themselves. -- Ray Kroc, Founder of McDonald's
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-12-13 at 10:22 -0500, Anton Aylward wrote:
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.
In the Linux world I can do this. We set up our dhcp server to ignore unknown hosts. So we do not confuse the Windows PCs on the network. The Windows folk claim there is no equivalent on their server. They are the experts there.
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.
The vlan is set up via a cisco network switch. The locals will not change it. At least not until they can see that window's dhcp server can't be made to behave.
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?
Nope. It is used by a couple of thousand PCs when booting. This includes two that must be on our subnet. Before those arrived, we did not let dhcp packets leave our subnet and all were happy. Now we must allow dhcp activity to leave the subnet. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer said the following on 12/13/2010 10:24 AM:
First: use of MAC address can constrain who responds to what.
In the Linux world I can do this. We set up our dhcp server to ignore unknown hosts. So we do not confuse the Windows PCs on the network. The Windows folk claim there is no equivalent on their server. They are the experts there.
I'm not a Windows expert but I can google and find articles on how to set up the Windows DHCP server to work with specific MAC addresses. Maybe the terminology is different but the function seems to be there.
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 {
The vlan is set up via a cisco network switch. The locals will not change it. At least not until they can see that window's dhcp server can't be made to behave.
I'm sorry; lets try again. This has nothing - ZILCH - to do with "subnetting"in the router sense of the word. It is the DHCP concept of what the server is going to respond to. It is about grouping and response. So you can put, for example, your X-Terminals in a group and assign part of the pool of dynamic addresses to them; you Windows workstations in another group and assign a different part of the pool to them. This is DHCP's idea of dividing up the network addresses. If you can't call that subnetting, then what? The config file uses the term 'subnet'. It has noting to do with routers, vlans or all that.
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?
Nope. It is used by a couple of thousand PCs when booting. This includes two that must be on our subnet.
Well there you are! Use the DHCP concept of subnetting!
Before those arrived, we did not let dhcp packets leave our subnet and all were happy. Now we must allow dhcp activity to leave the subnet.
You mean you have a relay agent through a router? 'Cos that's the only way to do what you seem to be saying. And that also means you can control and filter what goes though. -- Quality is not an act - it is a habit. - Aristotle -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer said the following on 12/13/2010 09:42 AM:
On Mon, 2010-12-13 at 09:04 -0500, Anton Aylward wrote:
Roger Oberholtzer said the following on 12/13/2010 08:38 AM:
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Hmm. So you have control over the Windows DHCP server ...
In so much as we can control what it tells devices on our subnet. But is it subnet-wide, which is causing part of the problem.
If this were me; the first experiment I'd try is cutting it out of the loop altogether.
Not possible. On this network are other windows machines that require the Windows dhcp server.
What is it that they require from the Windows DHCP server that can't be supplied by the Linux DHCP server? I'd point out that Microsoft has a large number of papers on Linux/Windows working together, all the way up to implementing the Windows AD using a Linus MySql-backed Linux based LDAP server; and of course the LDAP server and the database can be mirrored :-) I know of some firms that have implemented their Windows file servers on "Big Iron" *NIX like HP-500s with SAMBA for reliability and performance. You don't have to suck from the Windows-Server teat in order to run Windows desktop. -- People seldom improve when they have no other model but themselves to copy after. - Oliver Goldsmith -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-12-13 at 10:30 -0500, Anton Aylward wrote:
Roger Oberholtzer said the following on 12/13/2010 09:42 AM:
On Mon, 2010-12-13 at 09:04 -0500, Anton Aylward wrote:
Roger Oberholtzer said the following on 12/13/2010 08:38 AM:
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Hmm. So you have control over the Windows DHCP server ...
In so much as we can control what it tells devices on our subnet. But is it subnet-wide, which is causing part of the problem.
If this were me; the first experiment I'd try is cutting it out of the loop altogether.
Not possible. On this network are other windows machines that require the Windows dhcp server.
What is it that they require from the Windows DHCP server that can't be supplied by the Linux DHCP server?
Dynamic IP addresses on their network, and registration of this in the company-wide DNS (and NETBIOS), and a few other things I don't know about I am sure. I doubt they would give us a pool of dynamic addresses for the Windows machines. But this sort of solution is the one I will most likely persue if the server cannot be configured correctly.
I'd point out that Microsoft has a large number of papers on Linux/Windows working together, all the way up to implementing the Windows AD using a Linus MySql-backed Linux based LDAP server; and of course the LDAP server and the database can be mirrored :-)
We have no interest in setting up an AD server for this. But we do have our Linux machines on the company's AD.
I know of some firms that have implemented their Windows file servers on "Big Iron" *NIX like HP-500s with SAMBA for reliability and performance. You don't have to suck from the Windows-Server teat in order to run Windows desktop.
The locals just replaced the Novell file servers with MS file servers. No accounting for taste. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/13/2010 7:29 AM, Roger Oberholtzer wrote:
Dynamic IP addresses on their network, and registration of this in the company-wide DNS (and NETBIOS), and a few other things I don't know about I am sure. I doubt they would give us a pool of dynamic addresses for the Windows machines. But this sort of solution is the one I will most likely persue if the server cannot be configured correctly.
I'd point out that Microsoft has a large number of papers on Linux/Windows working together, all the way up to implementing the Windows AD using a Linus MySql-backed Linux based LDAP server; and of course the LDAP server and the database can be mirrored :-)
We have no interest in setting up an AD server for this. But we do have our Linux machines on the company's AD.
I know of some firms that have implemented their Windows file servers on "Big Iron" *NIX like HP-500s with SAMBA for reliability and performance. You don't have to suck from the Windows-Server teat in order to run Windows desktop.
The locals just replaced the Novell file servers with MS file servers. No accounting for taste.
Ok, so turning the question around, why do you need your own DHCP server on Linux. Just use theirs. I've never met a windows box that cared where its IP came from. Or a linux one either. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
Ok, so turning the question around, why do you need your own DHCP server on Linux. Just use theirs.
That is exactly what Roger is trying to do. -- Per Jessen, Zürich (-4.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 13, 2010, at 8:02 PM, Per Jessen wrote:
John Andersen wrote:
Ok, so turning the question around, why do you need your own DHCP server on Linux. Just use theirs.
That is exactly what Roger is trying to do.
Indeed. But I am only willing to hand over the address assignment. Phase two, the diskless booting, requires not only tftp, but also the Linux vblade stuff as we mount the openSUSE root partition using AoE (ATA over Ethernet). And we must know things are working in the Linux environment where the devices will be deployed.
Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 13, 2010, at 6:16 PM, John Andersen wrote:
Ok, so turning the question around, why do you need your own DHCP server on Linux. Just use theirs.
We make and sell Linux-based measurement systems. Part of these are diskless VME racks and other computers that boot openSUSE (11.2 made locally in KIWI) via dhcp/tftp. The vlan is a staging area for developing, configuring and testing these systems. The devices are not static. They come and do at a fast rate. They will eventually find themselves in a measurement vehicle where the only server is an openSUSE machine. We require in no uncertain terms that our development and configuration happen in the same way they will be used. We have little interest in making things work in some environment other than the one where things will be used. The real thing is to see why we need the interloper Windows PCs on this network. I would like to see if they could be relocated. They are the machines that brought about the problem!
I've never met a windows box that cared where its IP came from. Or a linux one either.
-- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer said the following on 12/13/2010 09:42 AM:
Hmm. So you have control over the Windows DHCP server ...
In so much as we can control what it tells devices on our subnet. But is it subnet-wide, which is causing part of the problem.
Option: Set it to tell the devices nothing aka blank config Option: Set it to tell the devices to ask the Linux server Googling I find entries for using 'next-server' on Windows DHCP http://efreedom.com/Question/3-175643/Windows-Redirect-Dhcp-Traffic-Alternat... which gets back to my idea about suing MAC addresses -- The only freedom which deserves the name, is that of pursuing our own good in our own way, so long as we do not attempt to deprive others of theirs, or impede their efforts to obtain it. --John Stuart Mill (On Liberty, 1859) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 13, 2010, at 4:48 PM, Anton Aylward wrote:
Roger Oberholtzer said the following on 12/13/2010 09:42 AM:
Hmm. So you have control over the Windows DHCP server ...
In so much as we can control what it tells devices on our subnet. But is it subnet-wide, which is causing part of the problem.
Option: Set it to tell the devices nothing aka blank config Option: Set it to tell the devices to ask the Linux server Googling I find entries for using 'next-server' on Windows DHCP
next-server does not pass along the dhcp request. It adds info to the dhcpoffer packer that tells where the client should go AFTER setting up the network interface. This is usually where it will find a tftp server to get a boot image. It is not another place to get an address.
http://efreedom.com/Question/3-175643/Windows-Redirect-Dhcp-Traffic-Alternat... which gets back to my idea about suing MAC addresses
I will look to see if this helps. All info is interesting! Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great.
Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files.
Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing.
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Google is probably a better place to go, this thread sounds promising: http://www.mcseboard.de/windows-forum-lan-wan-32/next-server-bootserver-1457... -- Per Jessen, Zürich (-1.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-12-13 at 15:13 +0100, Per Jessen wrote:
Roger Oberholtzer wrote:
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Google is probably a better place to go, this thread sounds promising:
http://www.mcseboard.de/windows-forum-lan-wan-32/next-server-bootserver-1457...
We did start consult google. But as this is being set up by the local MS wizards, I thought they would 'just know'. You know, it would just be obvious, as is all things in Windows... ;) -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great.
Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files.
Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing.
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Does the Windows server not support the TFTP server option? If not, is there no means of manually specifying DHCP options? TFTP server is option 66. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-12-13 at 10:07 -0500, James Knott wrote:
Roger Oberholtzer wrote:
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great.
Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files.
Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing.
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Does the Windows server not support the TFTP server option? If not, is there no means of manually specifying DHCP options? TFTP server is option 66.
I think this is called the 'boot host' in the Windows server. At least the description is that it tells which tftp server from which to get the boot image. But if we get nowhere, I will see if they will try option 66. I remember that they looked at me like I was crazy when I mentioned 'option domain-name', which is what the 'domain name' is in the Linux config file. The 'option' text was considered suspect. Why it has the 'option' text is indeed a mystery, making for tons o' fun when translation configurations between servers. I thought there would be some handy 'windows settings in one column' and 'linux settings in the other column' table somewhere. It there is, it hides well. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
I think this is called the 'boot host' in the Windows server. At least the description is that it tells which tftp server from which to get the boot image. But if we get nowhere, I will see if they will try option 66. I remember that they looked at me like I was crazy when I mentioned 'option domain-name', which is what the 'domain name' is in the Linux config file. The 'option' text was considered suspect. Why it has the 'option' text is indeed a mystery, making for tons o' fun when translation configurations between servers. I thought there would be some handy 'windows settings in one column' and 'linux settings in the other column' table somewhere. It there is, it hides well.
Here's a link to a list of DHCP options: http://www.networksorcery.com/enp/protocol/bootp/options.htm In the Yast DHCP configuration, it's called option tftp-server-name. I'd expect such an option to be available on Windows, as in addition to tasks such as what you're doing, voice over IP phones often use TFTP to download configuration info. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Op 13-12-10 14:38, Roger Oberholtzer schreef:
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great.
Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files.
Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing.
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Roger, Do you have your answer ? I'm looking at opsi, where you can install OS'es via tftp. They mention 'bootserver' or 'startserver' and 'bootfile' or 'startfile' as the Windows DHCP-configurations. HTH, Koenraad Lelong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-12-16 at 10:15 +0100, Koenraad Lelong wrote:
Op 13-12-10 14:38, Roger Oberholtzer schreef:
I have a dhcp server running on openSUSE. In addition to setting up IP addresses, it instructs the systems where to find the tftp server that will serve up the boot image, as well as the boot image name. It is working great.
Unfortunately, this now needs to co-exist on a network where there is a Windows dhcp server. The problem is that the windows server is faster at responding to the dhcpdiscover request than is the openSUSE server. Not much to do about that - race conditions are a fact of life. So, we thought we would solve this by duplicating the IP address and next-server/filename stuff on the Windows server. The result should be that the system still goes to the openSUSE box to get boot files.
Unfortunately, this seems not to work as expected. We get the IP address. But is is unclear which option in the Windows server corresponds to Linux's next-server. We set one called 'boot host' that is described as pointing to the tftp server. But oddly we get nothing.
I guess I am sending out feelers to see if anyone else has an openSUSE diskless boot sequence (boot images on an openSUSE tftp server) that involves a Windows dhcp server.
Roger,
Do you have your answer ? I'm looking at opsi, where you can install OS'es via tftp. They mention 'bootserver' or 'startserver' and 'bootfile' or 'startfile' as the Windows DHCP-configurations.
We are slowly working through it. I can now get the IP address, next server and boot image name from the Windows server. Then the systems happily boot from the Linux host. The problem is that they only seem to know how to set the windows server up so (A) all machines on our vlan are treated the same (B) only machines with a specified MAC address are configured. What we really need is to have a VLAN default that is overridden for specific MAC addresses. If you are not one of those MAC addresses, you get the defaults. I do not know why this is a problem. We have our Linux dhcp server doing this with no problem. So progress: yes. Solution: No. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anton Aylward -
James Knott -
John Andersen -
Koenraad Lelong -
Per Jessen -
Roger Oberholtzer