[Dnsmasq-discuss] both dns & dhcp timeout

zhangweiwu at realss.com zhangweiwu at realss.com
Sat Sep 6 18:19:27 BST 2008


The daemon on a Lemote MIPS server version 2.26 can start but all
connection to its dns service timeout, dhcp clients also timeout trying
to get an IP address.

RAYS:~# ifconfig  | head -n2
eth0      Link encap:Ethernet  HWaddr 00:11:11:11:18:B1 
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
RAYS:~# cat /etc/dnsmasq.conf
dhcp-range=192.168.1.100,192.168.1.150,12h
RAYS:~# grep nameserver /etc/resolv.conf
nameserver 202.106.46.151
nameserver 202.106.195.68
RAYS:~# /usr/sbin/dnsmasq -u dnsmasq -d
dnsmasq: started, version 2.26 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt RTNetlink ISC-leasefile
no-DBus I18N
dnsmasq: DHCP, IP range 192.168.1.100 -- 192.168.1.150, lease time 12h
dnsmasq: read /etc/hosts - 2 addresses
dnsmasq: reading /etc/resolv.conf
dnsmasq: using nameserver 202.106.195.68#53
dnsmasq: using nameserver 202.106.46.151#53

On the client side:

DNS doesn't work:

zhangweiwu at esmeralda:~$ host realss.com 192.168.1.100
Nameserver 192.168.1.100 not responding
realss.com A record not found at 192.168.1.100, try again
zhangweiwu at esmeralda:~$ host realss.com 202.106.46.151
realss.com              A    211.157.114.130

DHCP doesn't work:
zhangweiwu at esmeralda:~$ sudo /etc/init.d/net.eth2 restart
 * Stopping eth2
 *   Bringing down eth2
 *     Stopping dhcpcd on eth2
...                                                      [ ok ]
 *     Shutting down eth2
...                                                           [ ok ]
 * Starting eth2
 *   Configuring wireless network for eth2
 *     eth2 connected to ESSID "ZWW_SOHO" at 00:18:3F:AA:C0:09
 *     in managed mode on channel 6 (WEP enabled - open)
 *   Bringing up eth2
 *     dhcp
 *       Running dhcpcd ...
err, eth2: timed out
warn, eth2: using IPV4LL address
169.254.166.12                                         [ ok ]
 *       eth2 received address 169.254.166.12/16

A modem with DNS+DHCP feature sits just to the next port that connects
to the server runs dnsmasq, which works fine, showing the network itself
should be OK.

Interestingly, sending USR1 to it doesn't cause it coredump (basically
nothing happens after killing it with -USR1)

Operating System is "rays", a "slightly" modified Debian distribution.

-- 
Real Softservice

Huateng Tower, Unit 1788
Jia 302 3rd area of Jinsong, Chao Yang

Tel: +86 (10) 8773 0650 ext 603
Mobile: 159 1111 7382
http://www.realss.com




More information about the Dnsmasq-discuss mailing list