You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2.1 External Mode
The usage scenario of External mode is that iVentoy and the third-party DHCP Server are located in the same LAN/VLAN.
In this mode, iVentoy will still start its internal DHCP server, but the internal DHCP server will only snoop the DHCP packet and will not send any response. So it will not interfere with the work of the external DHCP Server.
By snooping the DHCP packet, iVentoy will record the client's BIOS mode, when the client request bootfile through TFTP, iVentoy will send it the right bootfile.
So in this mode, the DHCP server does not need to care about the client's BIOS mode. It only provides a common bootfile name (for example iventoy_loader_16000)
The bootfile name is actually a virtual file name. iVentoy will provide the real bootfile to the client according to its BIOS mode.
iVentoy is set to external mode, but when I try to network boot from a PC I get a null IP when ipxe tries to load the respective menu from the http link:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm having trouble to configure Adguard's dhcp for iventoy network boot.
This is my current config:
As the iventoy's documentation says:
iVentoy is set to external mode, but when I try to network boot from a PC I get a null IP when ipxe tries to load the respective menu from the http link:
The ipxe error says the dns name does not exist.
So... At this point I don't what's going on, and I hope somebody help me.
This is the iventoy detailed dhcp doc link.
Beta Was this translation helpful? Give feedback.
All reactions