blocks|key|683359|text|您所需要的正是这里询问和描述的内容：如果不能更改dhcp服务器，如何使用PXE安装Cobbler？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|683360|在这里您可以看到，在企业环境中设置ProxyDHCP服务器是非常可能的。这实际上只服务于PXE引导信息，而不是IP/子网/网关/etc信息。|683361|为了记录在案，如果做的正确，这不是一个DHCP服务器。|entityMap|0|LINK|mutability|MUTABLE|url|https://serverfault.com/questions/53116/howto-setup-cobbler-with-pxe-if-you-cant-change-the-dhcp-server^0|I|V|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|C|$]]]|H|$I|$5|J|K|L|C|$M|N]]]]

What you need is exactly what has been asked and described here:
<a href="https://serverfault.com/questions/53116/howto-setup-cobbler-with-pxe-if-you-cant-change-the-dhcp-server">Howto setup Cobbler with PXE if you can&#39;t change the dhcp server?</a>

There you see that it is very well possible to setup a ProxyDHCP server in a corporate environment. This essentially ONLY serves the PXE boot information and NOT the IP/subnet/gateway/etc information.

And just for the record, when done right this isn't a DHCP server.

blocks|key|682858|text|虽然您可以在网络上设置第二个DHCP服务器，但是没有可靠的方法可以让计算机更喜欢它的响应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|682859|更重要的是，你不应该试图规避公司的政策。这不专业。如果需要访问DHCP服务器，请向经理说明情况。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

While you can set up a second DHCP server on a network, there is no reliable way to get a computer to prefer its responses.

More importantly, though, you should not be trying to circumvent your company's policy. This is unprofessional. If you need access to the DHCP server, make a case for it to your manager.

blocks|key|682899|text|未经网络和系统管理员的许可，您根本不应该创建自己的DHCP服务，事实上，未经他们的允许，这样做应该是违法的。正是这种行为强调了为什么DHCP在只有客户的环境中是危险的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|682900|所以重申-不要这样做，这是错误的。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

You shouldn't be creating your own DHCP service at all without the permission of the network and system administrators, in fact doing so without their permission should be a firing offence. It's exactly this kind of behaviour which underlines why DHCP in anything but a client-only environment is dangerous.

So to reiterate - don't do this, it's wrong.

blocks|key|3287553|text|我使用内部VM网络完成了这种设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3287554|📷|atomic|offset|length|3287555|通过这种方式，您可以测试您的配置，而不会中断公司网络。确保DHCP服务器仅在连接到内部VSwitch的接口上侦听。|3287556|VM1运行PXE堆栈(DHCP，TFTP.)。在这个配置中，您可以使用这个VM作为路由器，让VM2访问您公司的网络。VM2是将从网络引导的VM。|3287557|如果您想要保存，只使用内部VSwitch，不要将VM1连接到物理局域网。|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://i.stack.imgur.com/entuj.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@$E|W|F|X|1|Y]]|A|$]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

I did this kind of setup using an internal VM network.<img src="https://i.stack.imgur.com/entuj.png" alt="Internal VSwitch used for a DHCP/PXE">

In this way you can test you configuration without disrupting the company network.
Make sure that the DHCP server is listening only on the interface connected to the internal VSwitch.

VM1 runs the PXE stack (DHCP, TFTP...). In this configuration you can use this VM as a router to give access for VM2 to your company's network.
VM2 is the VM that will boot from network.

If you want to be save use only the internal VSwitch and do not connect VM1 to the physical LAN.

blocks|key|683164|text|有一种不涉及触及现有DHCP服务器配置的合法方法。事实上，你甚至不需要DHCP。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|683165|虽然这看起来不太理想--在引导时只点击F8/F12/等，直接通过网络进入菜单系统--但是您可以使用非常小(<1MB)的iPXE+ISO+CD映像来使用任何现有的DHCP服务器启动。如果您正在引导正在使用DHCP的VMs例如VirtualBox、VMware工作站、VMware+ESXi等--那就更容易了，因为您可以简单地挂载iPXE+ISO并更改引导顺序以启动ISO。|683166|步骤如下：|683167|从安装了gcc和git的Linux盒中，获取iPXE源代码:+git克隆git://git.ipxe.org/ipxe.git|ordered-list-item|683168|创建一个嵌入式iPXE脚本，指向现有的pxelinux.0：|683169|下面是一个示例脚本：|683170|#!ipxe
dhcp+%7C%7C+goto+enterip
goto+bootit

:enterip
echo+-n+IP+address:+&&+read+net0/ip
echo+-n+Subnet+mask:+&&+read+net0/netmask
echo+-n+Gateway:+&&+read+net0/gateway
echo+-n+DNS+server:+&&+read+net0/dns
goto+bootit

:bootit
chain+http://servernameoripaddress/pxelinux.0+|code-block|syntax|javascript|683171|我相信，如果您已经拥有pxelinux.0的服务器上没有ftp://“服务器，那么”链t+web+URI“也会工作。您可能需要考虑使用http，因为它通常比tftp快得多。只需cp+-R+*您当前tftpboot文件夹中的任何内容都可以进入您的web服务器的DocumentRoot中，您最好使用http来通过iPXE进行网络引导，而不是使用tftp。|683172|将此脚本文件保存在某个地方，然后使用您刚刚创建的嵌入式脚本构建iPXE+ISO：|683173|cd+~/ipxe/src
make+clean
make+bin/ipxe.iso+EMBEDDED_IMAGE=yourscript.ipxe|683174|现在，在安装ipxe.iso文件的情况下，通过VM启动ISO文件，或者将其写入空白CD，然后用该CD启动物理盒。|683175|这是一种享受。在iPXE中有这么多的力量，我一直在开发一个围绕它的服务。许多脚本和构建信息代表了这个开发过程中来之不易的信息，因此希望它能很好地为您服务。您可以看看netboot.me或以前的boot.kernel.org+(我相信，由于kernel.org在一段时间前就被黑客攻击)，您可以看看它是如何在互联网或本地网络上运行的。|683176|如果您可以让DHCP服务器的管理员最终将其配置为支持网络引导(PXE引导-+DHCP+66和67)，那么相同的iPXE构建过程可以生成一个引导文件，该文件将避免对pxelinux.0的需求。这看起来像是：|683177|make+bin/undionly.kpxe+EMBEDDED_IMAGE=yourscript.ipxe+
cp+~/ipxe/src/bin/undionly.kpxe+/webserverdocumentroot/ipxe.0|683178|然后，您可以通过普通的PXE引导过程直接引导到这个iPXE文件--同样，假设您的DHCP最终启用了network+-它将允许您在网络上执行各种漂亮的网络引导操作，而不需要任何ISO文件。|683179|如果你有问题，请告诉我。|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|1E|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1F|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1G|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|1H|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1I|8|@]|9|@]|A|$]]|$1|V|3|W|5|O|7|1J|8|@]|9|@]|A|$P|Q]]|$1|X|3|Y|5|H|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1L|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1M|8|@]|9|@]|A|$]]|$1|13|3|14|5|O|7|1N|8|@]|9|@]|A|$P|Q]]|$1|15|3|16|5|6|7|1O|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|1P|8|@]|9|@]|A|$]]]|19|$]]

There is a legitimate way to do this that does not involve touching your existing DHCP server configuration. In fact, you don't even need DHCP.

Though it may seem less than ideal - vs simply hitting F8/F12/etc. on boot and getting to a menu system directly over the network - you can use a very small (&lt;1MB) iPXE ISO CD image to boot using any existing DHCP server. If you're booting VMs that are using DHCP - e.g., VirtualBox, VMware Workstation, VMware ESXi, etc. - it's even easier as you can simply mount the iPXE ISO and change your boot order to boot off the ISO. 

Steps are as follows:

<ol>
<li>From a Linux box with gcc and git installed, grab the iPXE source code: 

git clone git://git.ipxe.org/ipxe.git</li>
<li>Create an embedded iPXE script that points to say your existing pxelinux.0:</li>
</ol>

Here is an example script:

<pre><code>#!ipxe
dhcp || goto enterip
goto bootit

:enterip
echo -n IP address: &amp;&amp; read net0/ip
echo -n Subnet mask: &amp;&amp; read net0/netmask
echo -n Gateway: &amp;&amp; read net0/gateway
echo -n DNS server: &amp;&amp; read net0/dns
goto bootit

:bootit
chain http://servernameoripaddress/pxelinux.0 
</code></pre>

I believe a "chain tftp://" URI will also work if the server you already have pxelinux.0 on does not have a web server on it. You may want to consider using http as it's generally much faster than tftp. Just cp -R * whatever is in your current tftpboot folder into the DocumentRoot for your web server and you should be good to go using http for network bootstrapping via iPXE instead of tftp. 

Save this script file off somewhere then build the iPXE ISO with the embedded script you just created: 

<pre><code>cd ~/ipxe/src
make clean
make bin/ipxe.iso EMBEDDED_IMAGE=yourscript.ipxe
</code></pre>

<ol start="3">
<li>Now boot off the ISO file - via VM with the ipxe.iso file mounted or write it to a blank CD and boot off the physical box with that CD. </li>
</ol>

This works a treat. There's so much power in iPXE I've been developing a service around it. Much of the scripting and build information represents hard-won information around this development process so hopefully it serves you well. You can look at netboot.me or the former boot.kernel.org (defunct now I believe since kernel.org was hacked a while back) to get a taste for how this might work over the Internet or your local network for that matter.

If you can get the admin of your DHCP server to eventually configure it to support network bootstrapping (PXE booting - DHCP options 66 and 67) then the same iPXE build process can generate a bootstrap file that will obviate the need for pxelinux.0. This looks like:

<pre><code>make bin/undionly.kpxe EMBEDDED_IMAGE=yourscript.ipxe 
cp ~/ipxe/src/bin/undionly.kpxe /webserverdocumentroot/ipxe.0
</code></pre>

You can then bootstrap directly to this iPXE file over the normal PXE boot process - again, assuming your DHCP admin has finally enabled netbooting - and it will allow you to do all sorts of nifty network boot things on your network, no ISO file required.

Don't hesitate to let me know if you have questions.

blocks|key|3287502|text|完全同意其他人，建立自己的DHCP服务器几乎总是一个坏主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3287503|这么说，你为什么要这么做？如果它用于软件的可重复安装(而不是无盘客户端)，则可以设置一个引导程序(或为每个服务器设置一个引导程序)并模拟DHCP/tftpboot阶段。|3287504|例如，我们将Red部署到整个企业，并有一个标准的启动脚本，用于配置新机器。当我们从一个DHCP服务器远程部署时，我们从CD启动，并告诉anaconda从http服务器中提取适当的启动器和包。|3287505|当然，如果您正在查看瘦客户端解决方案，这是没有用的。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Totally agree with the other guys, setting up your own DHCP server is almost always a bad idea.

Saying that, why do you want to do it? If it's for repeatable installs of software (and not diskless clients), you could setup a bootcd (or one for each server) and simulate the DHCP/tftpboot phase.

For example, we deploy Red Hat all over the enterprise and have a standard kickstart script which is run to configure new machines. When we're deploying somewhere remote from one of our DHCP servers, we boot from CD and tell anaconda to pull the appropriate kickstart and packages from a http server.

Of course this is no use if you're looking at a thin client solution.

blocks|key|3287597|text|我不建议设置一个“红色”DHCP服务器.即使我们都不能列出所有可能出错的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3287598|但是，有两个(可能更多)可能的解决办法：|3287599|1.)制作一台与公司网络断开连接的便携式pc/膝上型计算机，带有引导映像、dhcp服务器和所需的一切。当您需要进行OS安装时，物理上将PC与公司网络断开，将其连接到“install+box”，然后进行安装，然后将PC重新连接回公司网络。即使是在较旧的膝上型计算机上，这种设置也可以很容易地完成，并且是可移植的，而且相当安全(只是不要将与dhcpcd运行的接口连接到内部网络)。|3287600|2.)联系您的网络管理员，并为OS安装设置一个特殊的VLAN，然后在那里运行您的安装程序。当您需要安装OS+(可能不太频繁)时，请与他们联系，将所需的端口切换到您的VLAN并运行安装。安装完毕后，只需告诉他们将端口放回正确的VLAN。|3287601|运行多个不知道eachoter的DHCP服务器不是我想要调试的东西:D|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|N|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

I would not recommend setting up a 'rouge' DHCP server... even if we all here couldn't list all the things that could go wrong with this.

But, there are two (probably even more) possible workarounds:

1.) Make a portable pc/laptop, disconnected from the company network, with the boot images, dhcp server, and everything needed. When you need to do an OS install, physically disconnect the PC from the companies network, connect it to your 'instal box', do the install, and then reconnect the PC back to the companies network. This setup can be easily done even with an older laptop, and is portable, and reasonably safe (just don't connect the interface with the dhcpcd running to the internal network).

2.) Contact your network admins, and set up a special VLAN for OS installs, and then run your setup there. When you need to install an OS (probably not too often), contact them, to switch the desired port to your VLAN and run the install. After the install, just tell them to put the port back to the correct VLAN. 

Running multiple DHCP servers where they don't all know about eachoter is not a thing I'd ever want to debug :D

blocks|key|3287621|text|您可以设置一个路由器，它的广域网接口插入您的公司局域网，然后在您控制下运行一个不同的子网，这样您就可以控制您的机器的DHCP，而不影响公司局域网的其余部分，同时仍然访问公司的资源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3287622|不过，除非你能获得有关人士的批准，否则我不会建议你这样做，因为这样做很可能违反可能令你陷入困境的某种形式的政策或合约。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

You could set up a router with it's WAN interface plugged into your company lan, then operate a different subnet under your control so you can control DHCP for your machines without affecting the rest of the company's LAN while still accessing the company's resources.

However I would not suggest to do this unless you can obtain permission from the relevant persons as this will likely be a breach of some form of policy or contract that could land you in trouble.

Recently I want to setup PXE boot server (i.e. DHCP server + TFTP server + syslinux software) for my company network in a LAN. I have read the setup details at here: <a href="http://www.linuxjournal.com/article/9963" rel="nofollow noreferrer">http://www.linuxjournal.com/article/9963</a>

However I don't have admin/access right to the existing DHCP server and I cannot change the settings. (you need to put the PXE server IP address in the DHCP server configuration file to make the PXE booting works).

I want to do the PXE boot in a good intention (make the new OS installation easier). Can I setup my own DHCP server (not 'legal' DHCP server) and use it with my PXE server to do the PXE boot? Is it possible? 

If I cannot setup my own DHCP server, what is the working round for this problem? I really want the PXE boot to easy my batch installation process. thanks.

setup rogue DHCP when using PXE boot

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

最近，我想在局域网中为我的公司网络设置PXE引导服务器(即DHCP服务器+ TFTP服务器+ syslinux软件)。我已经阅读了这里的设置细节：http://www.linuxjournal.com/article/9963但是，我没有对现有DHCP服务器的管理/访问权限，也不能更改设置。(您需要将PXE服务器IP地址放在DHCP服务器配置文件中，以使PXE启动工作)。我想做一个良好的PXE引导

问使用PXE引导时安装流氓DHCP
EN

回答 8

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PXE引导时安装流氓DHCPEN

回答 8

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PXE引导时安装流氓DHCP
EN