In dnsmasq the default EDNS0 max UDP size is limited to the conservative value of 1280 bytes. I have two concerns about this: - the 1280 value can be still too low for coming DNSSEC (the root will be signed next year so we can expect at least 4 time larger DNS response) - in theory it is not the role of dnsmasq at all to constraint clients to a conservative maximum size, i.e., if a client takes the risk of the usual fragmentation issues it should be allowed to do it. So I asked dnsmasq author to look at for a better defaut in next releases but as it is a command line option the best is to fix this directly in the config.
Regards francis.dup...@fdupont.fr PS: the patch itself (from 8.09 svn local copy): Index: package/dnsmasq/files/dhcp.conf =================================================================== --- package/dnsmasq/files/dhcp.conf (revision 18800) +++ package/dnsmasq/files/dhcp.conf (working copy) @@ -9,6 +9,7 @@ option nonegcache 0 option authoritative 1 option readethers 1 + option ednspacket_max 4096 option leasefile '/tmp/dhcp.leases' option resolvfile '/tmp/resolv.conf.auto' #list server '/mycompany.local/1.2.3.4' _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel