1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato 1.23, dnsmasq problem

Discussion in 'Tomato Firmware' started by madsonic, Mar 2, 2009.

  1. madsonic

    madsonic Addicted to LI Member

    Hello!

    I am currently trying to setup a pxe enviroment to boot gentoo on a diskless client, using a WRT54GL running tomato 1.23. According to the manpage dnsmasq has a built-in tftp server which would be ideal so serve the bootimage. To enable the tftp i added
    Code:
    enable-tftp
    dhcp-boot=/cifs1/alix-bootimages/pxelinux.0,,192.168.1.1
    tftp-root=/cifs1/alix-bootimages/
    
    into the custom dns config window (webif), but as soon as i click save all my dns stopps working and dnsmasq dissapears. "# ps | grep dns*" gives me nothing, and as soon as i commnent the enable-tftp it works again and dnsmasq gets restarted. Apperently any illegal option causes dnsmasq to stop working?

    Someone had the same problem or am i just missing something? maybe a typo?

    greetings

    madonic
     
  2. madsonic

    madsonic Addicted to LI Member

    Have been playing around with it a bit, emerging dnsmasq on my gentoo box. It seems that the standard buildconfig does not enable the tftp server. Is it possible to build a custom version of dnsmasq and replace the tomato original version?
     
  3. Planiwa

    Planiwa LI Guru Member

    An unbroken dnsmasq sure would be nice. One that doesn't do this:

    Code:
    Mar  1 22:03:10 ROUTER daemon.info dnsmasq[116]: DHCPDISCOVER(br0) 192.168.0.108 xx:xx:xx:xx:xx:xx
    Mar  1 22:03:10 ROUTER daemon.info dnsmasq[116]: DHCPOFFER(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:10 ROUTER daemon.info dnsmasq[116]: DHCPDISCOVER(br0) 192.168.0.108 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:10 ROUTER daemon.info dnsmasq[116]: DHCPOFFER(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:14 ROUTER daemon.info dnsmasq[116]: DHCPDISCOVER(br0) 192.168.0.108 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:14 ROUTER daemon.info dnsmasq[116]: DHCPOFFER(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:22 ROUTER daemon.info dnsmasq[116]: DHCPDISCOVER(br0) 192.168.0.108 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:22 ROUTER daemon.info dnsmasq[116]: DHCPOFFER(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:22 ROUTER daemon.info dnsmasq[116]: DHCPREQUEST(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:22 ROUTER daemon.info dnsmasq[116]: DHCPACK(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx tomatohostname
    Mar  1 22:03:25 ROUTER daemon.info dnsmasq[116]: DHCPREQUEST(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:25 ROUTER daemon.info dnsmasq[116]: DHCPACK(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx tomatohostname
    Mar  1 22:03:32 ROUTER daemon.info dnsmasq[116]: DHCPREQUEST(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:32 ROUTER daemon.info dnsmasq[116]: DHCPACK(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx tomatohostname
    Mar  1 22:03:50 ROUTER daemon.info dnsmasq[116]: DHCPINFORM(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx 
    Mar  1 22:03:50 ROUTER daemon.info dnsmasq[116]: DHCPACK(br0) 192.168.0.131 xx:xx:xx:xx:xx:xx PC-hostname
    And that doesn't get stuck in a state where wl associates, dnsmasq leases, but no routing happens.

    Restarting dnsmasq (or wl) does not fix it.

    The only (non-human) recourse I know is for the router to detect the problem heuristically:

    "if there are (enough) associated clients who are normally pingable but cannot be pinged" and/or
    "if there are (practically) no recent connections in Conntrack for wifi LAN hosts" and/or
    "if there is no WAN traffic at all" (for (any) wifi LAN hosts)
    then reboot the router.

    crude, but effective.

    Oh, and 90% of the syslog is filled with those prolonged lease negotiations (7 day leases).

    Oh, and then there is the issue with the tomatoname from /etc/hosts.dnsmasq (Basic > Static DHCP) not being displayed in places like "Device List" (WOL works :)).
     
  4. Megaweapon

    Megaweapon Addicted to LI Member

    I found this out as well today and was quite disappointed. I am using teddy_bear's USB-enabled Tomato and was pretty excited about the idea of running my network-based OS installs and other PXE-bootable things (such as PLoP) entirely from my WL-520gU with dnsmasq's tftpd and PXE boot features. Unfortunately...

    Code:
    unsupported option (check that dnsmasq was compiled with DHCP/TFTP/DBus support)
    :sad:

    Does anyone know why the tftp dnsmasq feature is disabled at compile in Tomato? Does it take up too much space? Break something else? Have unreasonable depends? I'd like to know if pursuing a custom compile of my own is worth the effort for a 4MB router.

    Any help would be appreciated.
     

Share This Page