Modify

Opened 8 years ago

Closed 7 years ago

Last modified 4 years ago

#6843 closed defect (no_response)

trunk - dnsmasq and ixp4xx (Gateworks Cambria) issue

Reported by: nlinux <mekelly5@…> Owned by: developers
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: base system Version: Kamikaze trunk
Keywords: Cc:

Description

I having issues with dnsmasq in current trunk performing correctly on gateworks cambria ixp4xx board. I cannont get any dns forwards to occur all dnsmasq queries fail. It appears to be ingnoring the settings in /tmp/resolv.auto.

Also I am seeing dhcp clients issued issued ip's that are outside the defined range. I have clients issued with .199 and .200 right now but the defined range is only 100 - 150.

I am using the stock dnsmasq config file as far as I know:

config 'dnsmasq'

option 'domainneeded' '1'
option 'boguspriv' '1'
option 'filterwin2k' '0'
option 'localise_queries' '1'
option 'local' '/lan/'
option 'domain' 'lan'
option 'expandhosts' '1'
option 'nonegcache' '0'
option 'authoritative' '1'
option 'readethers' '1'
option 'leasefile' '/tmp/dhcp.leases'
option 'resolvfile' '/tmp/resolv.conf.auto'

config 'dhcp' 'lan'

option 'interface' 'lan'
option 'start' '100'
option 'limit' '150'
option 'leasetime' '6h'

config 'dhcp' 'wan'

option 'interface' 'wan'
option 'ignore' '1'
option 'dynamicdhcp' '0'

if I add:

option 'dhcp_option' '6,4.2.2.1'

then all my clients get passed that dns server by dnsmasq, but dnsmasq will not do any lookups.

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by anonymous

I had the similar problem, and am not sure exactly what causes it, but what I did learn is that when I set option 'logqueries' '1' and option 'nodaemon' '1', then run /etc/init.d/dnsmasq restart, it works fine. The simple workaround was to change the line in /etc/init.d/dnsmasq where it launches dnsmasq to:

(/usr/bin/dnsmasq $args | logger -tdnsmasq -plocal1.info &) && ( ...

... so that it will boot with those options set. I don't think this is the permanent solution; but at least my router is functional for now.

comment:2 Changed 7 years ago by jow

  • Priority changed from high to response-needed

Is this problem still present in rc3 ?

comment:3 Changed 7 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

Timeout. Last time I had issues with it not using resolv.conf.auto it was because of a broken system date

comment:4 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.