Modify

Opened 8 years ago

Closed 8 years ago

#3804 closed defect (invalid)

upnpd not starting automatically, requires symbolic link

Reported by: KillaB Owned by: developers
Priority: normal Milestone: Kamikaze 8.09 RC1
Component: packages Version:
Keywords: Cc:

Description

The following command fixes things, just not sure what to change in source.

ln -s /etc/init.d/upnpd /etc/rc.d/S65upnpd

Attachments (0)

Change History (10)

comment:1 Changed 8 years ago by loswillios

I assume you aren't aware of /etc/init.d/<package_name> enable|disable ?

comment:2 Changed 8 years ago by anonymous

loswillios, no I wasn't aware of that. It works, thanks!

Devs, should a package not be enabled by default? I like to put libupnp in SquashFS, but if someone was installing this package would they also have to enable it? Doesn't make sense to have to enable, by installing it you're implying you want it working.

comment:3 Changed 8 years ago by KillaB

I do see a reference to it in the documentation, so I guess you can just close this ticket.
However it would be nice for it to be enabled both at ipkg install or when embedded in a SquashFS image.

Thanks

comment:4 Changed 8 years ago by loswillios

all packages with init script included in the image are enabled by default. make sure your /etc/config/upnpd says 'option enabled 1'

comment:5 Changed 8 years ago by KillaB

My image r11899 is missing that file.

comment:6 Changed 8 years ago by KillaB

Removed the symbolic link by running "/etc/init.d/upnpd disable" then created "/etc/config/upnpd" and rebooted. It doesn't seem to have any effect after a reboot. Still no "/etc/rc.d/S65upnpd" created automatically. Doesn't matter if you replace upnpd for upnp.

root@OpenWrt:/# cat /etc/config/upnpd

config upnpd

option enabled 1

comment:7 Changed 8 years ago by loswillios

My bad, I read miniupnpd but you are using linux-igd. So, to make it clear: Every package with an init-script which was included in the image will automatically start on boot by default. Every package you install afterwards will default to not start on boot. There is no such thing like 'if this lib is installed, make the package start on boot', the lib is installed as a dependancy anyway.

comment:8 Changed 8 years ago by KillaB

Replying to loswillios:

My bad, I read miniupnpd but you are using linux-igd. So, to make it clear: Every package with an init-script which was included in the image will automatically start on boot by default.

This is incorrect and hence the reason I opened this ticket.

You're right about using linux-igd though. Haven't had a single hiccup with it and therefore see no reason to switch to miniupnpd.

comment:9 Changed 8 years ago by KillaB

loswillios, I apologize if the above sounded offensive, I just thought of a reason it might be doing what it's doing.

Because I'm using this on a DG834Gv2 and all WAN statements in /etc/config/network are commented out during first boot, there exists no nas0 interface to set up upnp. This could be the issue all along. Good to know about the enable|disable commands though and good to see it's in the documentation.

Devs, please close ticket. I don't see a solution to the problem as it's kind of a "catch 22".

comment:10 Changed 8 years ago by florian

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

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.