Modify

Opened 4 years ago

Closed 4 years ago

Last modified 20 months ago

#14629 closed defect (fixed)

dhcp not working on first boot

Reported by: anonymous Owned by: jow
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: dnsmasq Cc:

Description

hello seems like few days old changes breaks dnsmasq dhcp service.

after updating to the latest trunk dhcp (dnsmasq) stop working after router reboot. to fix it you need to login and manually restart the service.

i see no log issues.

at first start dnsmasq open 53 (dns) port and no 67 (dhcpd) port. after restart service it come back normally.

i tried to use 'froce 1' option on my lan segment, have no affect.

month old trunk works fine.

Attachments (0)

Change History (15)

comment:1 follow-up: Changed 4 years ago by anonymous

Because you have another dhcp server in lan...

comment:2 in reply to: ↑ 1 Changed 4 years ago by twerrt

Replying to anonymous:

Because you have another dhcp server in lan...

no i don't. if i do, 'force 1' will fix the issue.

also r39098 works fine

comment:3 Changed 4 years ago by anonymous

Got the same issue after upgrading to r39125 with a 3700v2. No other dhcp server, too.

Moreover, I could previously use a simple static IP setup for my computers; now I need to run some DHCP client on them to browse the net.

comment:4 Changed 4 years ago by anonymous

me too r39135

comment:5 Changed 4 years ago by duvi

Same here, r39123. Dnsmasq listens only on port 53, not on port 67.

comment:6 Changed 4 years ago by anonymous

Same problem here. dnsmasq starts before the LAN interface is up.

When it first boots /tmp/etc/dnsmasq.conf is missing this section:

dhcp-range=lan,192.168.1.221,192.168.1.250,255.255.255.0,12h
no-dhcp-interface=eth1

After restarting dnsmasq (/etc/init.d/dnsmasq restart), the above section appears in the config file.

This is because dnsmasq launched before netifd is done configuring br-lan. Suspect r39101 as the source of the issue. This was working fine before. There's a race condition here. Moving dnsmasq to later in the init.d boot up should workaround the problem. Ideally dnsmasq.init will do something specific to handle this scenario.

comment:7 Changed 4 years ago by jow

  • Owner changed from developers to jow
  • Priority changed from normal to response-needed
  • Status changed from new to accepted

Please try r39152

comment:8 Changed 4 years ago by twerrt

working fine

comment:9 Changed 4 years ago by duvi

works for me, too

comment:10 Changed 4 years ago by brian.olmsted@…

I have to wait until the r39152, r39153 or r39155 snapshot is uploaded to downloads.openwrt.org snapshot repository. Don't have a compilation environment and don't want to brick my router in the meantime. Hopefully sometime tomorrow morning ;)

comment:11 Changed 4 years ago by brian.olmsted@…

seems fine for me. Only issue I have is with /etc/init.d/network restart issuing an error about "Command failed: Not Found"

comment:12 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:13 Changed 4 years ago by jow

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:14 Changed 3 years ago by kor.korrd+openwrt@…

I have a very similar problem with the trunk version "Chaos Calmer r46314".
After boot either DNS or DHCP is working nor are the ports open. IP-Traffic and everything else works pretty normal.
I have to restart dnsmasq manually, then it works fine.

comment:15 Changed 20 months ago by puleglot

Never had this issue with the Routerstation PRO, but NEXX wt3020 suffers from this issue almost on every boot. :(

Right after boot:

root@nexx:~# ss -lnu
Netid  State      Recv-Q Send-Q    Local Address:Port    Peer Address:Port              
Cannot open netlink socket: Protocol not supported
udp    UNCONN     0      0                     *:53                 *:*
udp    UNCONN     0      0                    :::546               :::*
udp    UNCONN     0      0                    :::547               :::*
udp    UNCONN     0      0                    :::53                :::*
root@nexx:~# cp /var/etc/dnsmasq.conf /tmp/
root@nexx:~# /etc/init.d/dnsmasq restart
root@nexx:~# ss -lnu
Netid  State      Recv-Q Send-Q    Local Address:Port    Peer Address:Port
Cannot open netlink socket: Protocol not supported
udp    UNCONN     0      0                     *:53                 *:*
udp    UNCONN     0      0                     *:67                 *:*
udp    UNCONN     0      0                    :::546               :::*
udp    UNCONN     0      0                    :::547               :::*
udp    UNCONN     0      0                    :::53                :::*
root@nexx:~# diff -u /var/etc/dnsmasq.conf /tmp/dnsmasq.conf 
root@nexx:~#

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.