• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.


Search the Community

Showing results for tags 'pxe'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • vpsBoard
    • Announcements & Contests
    • Industry News
  • Virtual Private Servers
    • General Talk
    • Operating a VPS Business
    • Tutorials and Guides
    • Questions and Answers
  • The Lounge
    • The Pub (Off topic discussion)
    • Coding, Scripting & Programming
    • SBC, ARM, Home Automation
  • Marketplace & Reviews
    • Reviews
    • VPS Offers
    • Other Offers
    • Service Requests

Found 3 results

  1. I am using a user friendly router at home. Great for guest wlan and even separated lans, but it is not able to add boot information on the DHCP service. But - thanks to dnsmasq - you are able to add this information without modifying your router. It is able to enrich the DHCP response. Installation is simple: apt-get install dnsmasq Afterwards move the original configuration: mv /etc/dnsmasq.conf /etc/dnsmasq-bak.conf And create a new one: nano /etc/dnsmasq.conf With following content: port=0 dhcp-range=,proxy dhcp-boot=pxelinux.,, pxe-service=x86PC,"Automatic Network boot",pxelinux enable-tftp tftp-root=/usr/tftproot pxe-prompt="Press F8 for selection",5 pxe-service=X86PC,"Boot from harddrive", DNS is disabled by the "port=0" command. DHCP range is given by your router. "" is the ip of the linux server running the dnsmasq instance. You do not have to install a ftp server, tftp is part of the dnsmasq service. Just add the information where the boot files are stored. After that you have to define what pxe-services or boot images you are providing. Due to the additional config files and default settings this will be part of my next tutorial.
  2. Is IPMI important for a Dedi?

    Would you buy a dedicated server without IPMI? Provided that remote re-install is available and automated by customer (via PXE). A rescue system is also available (via PXE). Remote reboot is available (via Switched PDU or tickets free). remote KVM is available for loan for a small fee. Yes, we're planning to release some budget dedicated servers in the future. i5 Haswell 8GB RAM 500GB HDD ($49 or below).
  3. Collectively brain pooling on this one. Looking for easiest/quickest PXE boot server solution. Simply, need a setup where netboot can get one of many distro options to be served by this server. Anyone have a recommendation for the simplest/quickest to setup PXE boot server?