[Dnsmasq-discuss] No space left in packet
carlos at fisica.ufpr.br
Thu May 29 22:41:11 BST 2008
Hans-Joachim Baader (Hans-Joachim.Baader at cjt.de) wrote on 27 May 2008 11:44:
>I'm currently testing replacing ISC dhdpc with dnsmasq. On one of the test
>machines I got an error "cannot send DHCP/BOOTP option 43: no space left
>in packet". This message repeated endlessly and none of the clients could
>get a lease. All other servers worked fine so far. The other servers have
>identical configuration, but the clients may have a different PXE BIOS.
>What could be the cause of this? Following is the complete config file.
>No command line options are used.
Your client uses bootp, sometimes there's very little space for
options in the packet. You can try removing everything non-essential,
such as net2 options when they're not used.
You may have to build a config tuned for each machine. For example, a
computer here uses dhcp when it boots windows, and there's no space
shortage; in this case it also needs routing info. When it does remote
booting it uses bootp, there's very little space, and it doesn't need
routing. My dhcp-options file has more than 1000 lines... It's
generated by a script.
>dhcp-option=46,1 # netbios node type
>#dhcp-option=47 # empty netbios scope
>The network net2 is not used, there is no second network card in these
>Option 43 is needed to boot some old PXE clients without a special PXE or
>server. Is there something wrong with the config file?
More information about the Dnsmasq-discuss