[Dnsmasq-discuss] dnsmasq.leases
I'm worried I might have still got a glitch in my dnsmasq config. I have a new print server which gets its ip via dhcp from dnsmasq, and it is duly registered in dnsmasq.leases. However about 1/2 hour to an hour later, the dnsmasq.leases entry for it vanished. I can't ping it via its hostname anymore but I can ping it via its ip address that it got from dnsmasq. It sounds to me as if the print server is acting strangely but could there be something in dnsmasq that is causing this problem? Can I configure any useful dhcp-option to encourage it to act normal? Regards Adam
[Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac
Hi guys,
For sometime now I've been using DNSMasq off a DD-WRT router to PXE boot
machines on my network to run diagnostics and OS installers. Recently I got
the drive to set this up for my Intel Mac, I got it working with the ISC
dhcp server in my virtual machine environment, but can't seem to understand
how to translate the options to DNSMasq in order to run it on my local
network. Below is the pertinent section:
class AppleNBI-i386{
match if substring (option vendor-class-identifier, 0, 14) =
AAPLBSDPC/i386;
option dhcp-parameter-request-list 1,3,17,43,60;
if (option dhcp-message-type = 1) { option vendor-class-identifier
AAPLBSDPC/i386; }
if (option dhcp-message-type = 1) { option vendor-encapsulated-options
08:04:81:00:00:67; }
# The Apple Boot Loader binary image. This file will in turn TFTP the kernel
image and extension cache.
filename Diag106NetBoot.nbi/i386/booter;
## NOTE: Try to keep the root path as short as possible. I copy the DMG
files to /nbi and export that folder.
option root-path nfs:192.168.33.1:
/var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg;
}
This came from http://www.afp548.com/article.php?story=20061220102102611
I was wondering if you guys could help me. So far I have:
dhcp-vendorclass=AppleNBI-i386,AAPLBSDPC/i386
dhcp-option=net:AppleNBI-i386,option-vendor,AAPLBSDPC/i386
dhcp-option=net:AppleNBI-i386,option:filename,Diag106NetBoot.nbi/i386/booter
dhcp-option=net:AppleNBI-i386,option:root-path,nfs:192.168.33.1:
/var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg
But this actually seems to have broken DNSMasq. Do you guys think you can
help me translate this ISC configuration to a DNSMasq configuration?
If the Developers are out there on the list I really enjoy the product,
thanks for the great work!
-Max
Re: [Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac
Hallo, Max, Du meintest am 30.01.10 zum Thema [Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac: option root-path nfs:192.168.33.1: /var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg; dhcp-option=net:AppleNBI-i386,option:root-path,nfs:192.168 .33.1: /var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg Your root-path option looks strange (for me): must be a directory, no file. Is NetBoot.dmg a directory? Is tftpboot:Diag106NetBoot.nbi a subdirectory? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] dnsmasq.leases
Adam Hardy wrote: I'm worried I might have still got a glitch in my dnsmasq config. I have a new print server which gets its ip via dhcp from dnsmasq, and it is duly registered in dnsmasq.leases. However about 1/2 hour to an hour later, the dnsmasq.leases entry for it vanished. I can't ping it via its hostname anymore but I can ping it via its ip address that it got from dnsmasq. It sounds to me as if the print server is acting strangely but could there be something in dnsmasq that is causing this problem? Can I configure any useful dhcp-option to encourage it to act normal? I've come across devices like this that just don't do lease renewal. They get a DHCP lease for whatever time the server gives them, but don't actually renew it. When the lease-time expires, the hostname disappears. The fix is to tell the dnsmasq DHCP server to give that device an infinite lease. dhcp-host=MAC address,infinite should do the trick. Cheers, Simon.
Re: [Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac
Thanks for your quick response Simon. I had to move to a different system
to get some diagnostic output (DD-WRT doesn't seem to support some options
or just isn't giving me output at the terminal).
using the --test option I found that DNSMasq didn't like the line:
dhcp-vendor=apple-boot,AAPLBSDPC/i386
Without that line it accepts the configuration file but my Mac will still
not NetBoot. I now am testing this in my virtual machine environment with
DNSMasq to rule out any differences in the two environments (except for the
DHCP server) causing the problem.
I have to step away for a couple hours, but next I will try adding:
dhcp-option-force=apple-boot,60,AAPLBSDPCi/i386
which DNSMasq doesn't find any problems with when I run the configuration
through DNSMasq with the --test argument.
Helmut -
Your root-path option looks strange (for me): must be a directory,
no file.
Is NetBoot.dmg a directory?
Is tftpboot:Diag106NetBoot.nbi a subdirectory?
This is part of how Apple does its network booting. Diag106NetBoot.nbi is a
folder in the root directory accessible via tftp, and NetBoot.dmg is the
root filesystem for the machine. Maybe it means the path to the root
filesystem.
Thanks guys! I'll do some more testing later and let you know how it goes.
-Max
On Sun, Jan 31, 2010 at 7:30 AM, Simon Kelley si...@thekelleys.org.ukwrote:
Max Turkewitz wrote:
Hi guys,
For sometime now I've been using DNSMasq off a DD-WRT router to PXE boot
machines on my network to run diagnostics and OS installers. Recently I got
the drive to set this up for my Intel Mac, I got it working with the ISC
dhcp server in my virtual machine environment, but can't seem to understand
how to translate the options to DNSMasq in order to run it on my local
network. Below is the pertinent section:
class AppleNBI-i386{
match if substring (option vendor-class-identifier, 0, 14) =
AAPLBSDPC/i386;
option dhcp-parameter-request-list 1,3,17,43,60;
if (option dhcp-message-type = 1) { option vendor-class-identifier
AAPLBSDPC/i386; }
if (option dhcp-message-type = 1) { option vendor-encapsulated-options
08:04:81:00:00:67; }
# The Apple Boot Loader binary image. This file will in turn TFTP the
kernel image and extension cache.
filename Diag106NetBoot.nbi/i386/booter;
## NOTE: Try to keep the root path as short as possible. I copy the DMG
files to /nbi and export that folder.
option root-path nfs:192.168.33.1:
/var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg;
}
Even better:
dhcp-vendor=apple-boot,AAPLBSDPC/i386
dhcp-option-force=apple-boot,vendor:AAPLBSDPC/i386,8,81:00:00:67
dhcp-option-force=apple-boot,option:root-path,nfs:192.168.33.1:
/var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg
dhcp-boot=net:apple-boot,Diag106NetBoot.nbi/i386/booter
HTH
Simon.
This came from http://www.afp548.com/article.php?story=20061220102102611
I was wondering if you guys could help me. So far I have:
dhcp-vendorclass=AppleNBI-i386,AAPLBSDPC/i386
dhcp-option=net:AppleNBI-i386,option-vendor,AAPLBSDPC/i386
dhcp-option=net:AppleNBI-i386,option:filename,Diag106NetBoot.nbi/i386/booter
dhcp-option=net:AppleNBI-i386,option:root-path,nfs:192.168.33.1:
/var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg
But this actually seems to have broken DNSMasq. Do you guys think you can
help me translate this ISC configuration to a DNSMasq configuration?
If the Developers are out there on the list I really enjoy the product,
thanks for the great work!
-Max
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
