PXEboot with CentOS 5.6 and dnsmasq

Install the required software:
yum install dnsmasq

Open up the firewall:
/sbin/iptables -I INPUT -m udp -p udp --dport 67 -j ACCEPT
/sbin/iptables -I INPUT -m udp -p udp --dport 53 -j ACCEPT

Then run:
dnsmasq -d --interface=br0 --dhcp-range=181.30.68.111,static --dhcp-host=84:2b:2b:78:30:79,181.30.68.112 --dhcp-option=option:router,181.30.68.65 --dhcp-boot=pxelinux.0 --enable-tftp --tftp-root=/var/ftpd

Put all required files, such as pxelinux.0 from the package syslinux in /var/ftpd

Ubuntu/Debian

I'm running RedHat-based software on all of my machines. Above information may be useful for Ubuntu/Debian users, but it's not tested and I'm not supporting it.

Servers: RedHat Enterprise Linux/CentOS is more suitable for servers, as there's a lot of professional level support available. I think that's important, because if I say, get a car accident, I want the servers to be managable by another professional.

Desktops/Laptops: RPM packages are pretty exchangable between RedHat-based platforms. That's a good reason to run Fedora on the desktop.
© GeekLabInfo PXEboot with CentOS 5.6 and dnsmasq is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

Windows 7 network awareness

After switching my network to a more strict proxy server recently, I found that Windows 7 machines were reporting they weren't connected to the internet anymore. While this is partly true, unauthenticated users can no longer just access http, users don't need to get this message.

The probing software is called Microsoft NCSI. What it does, is:

  1. perform a DNS lookup on www.msftncsi.com, and request http://www.msftncsi.com/ncsi.txt. This file is a plain-text file that contains only the text Microsoft NCSI.
  2. then do a DNS lookup request for dns.msftncsi.com. The answer should be an A-record resolving to 131.107.255.255. If no answer, or a wrong answer is given, NCSI assumes the internet connection is faulty.

I whitelisted www.msftncsi.com in my proxy to allow outbound http-connections from unauthenticated users to this domain.

© GeekLabInfo Windows 7 network awareness is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

VMWare Data Recovery is crap

VMWare Data Recovery is crap:

  • VMWare Data Recovery cannot be monitored and does not send out any warnings.
  • Running one instance of VMWare Data Recovery is too heavy for the appliance, causing the backups to be corrupted all the time
  • When running multiple instances of VMWare Data Recovery, say one instance per host, the whole thing is still slow as hell
  • Every few weeks, one backup gets corrupted. Of course the appliance does not notify you, no, instead you must login to the appliance to check the logs.
  • When you find a backup that is corrupted, you need to manually flag the restore point as "marked for deletion" and then start the integrity check.
  • When doing the integrity check, better pray that none of the other instances starts using the same nas/fileserver, as it gets so slow that the whole integrity check never gets completed.
  • I just tried to split the backups to multiple destinations, so that we can backup each virtual machine to its very own destination, and reduce the shitload of work the integrity check has to do when another backup is broken. Appears that VMWare Data Recovery only supports 2 destination per appliance instance.

I seriously consider VMWare Data Recovery to be the worst backup solution I've ever used.

© GeekLabInfo VMWare Data Recovery is crap is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
Loading...