Ernillew / wl500g

Automatically exported from code.google.com/p/wl500g
0 stars 0 forks source link

Problem with default /etc/miniupnpd.conf #304

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Default /etc/miniupnpd.conf have following line:
allow 1024-65535 192.168.1.0/24 1024-65535
which explicitly disable to make rooter holes for needed services with lower 
ports numbers like sshd (22), www (80), ident (113), etc.

What is the expected output? What do you see instead?
I wish to fully control upnp lower ports mapping, probably by additional web 
interface option.

What version of the product are you using?
1.9.2.7-rtn

Please provide any additional information below.
I try to edit this file by hand, changing 1024 to 1, but my change not survive 
across reboot, restoring old values. Perhaps improperly I use
flashfs save && flashfs commit && flashfs enable && reboot
and even 
echo /etc/miniupnpd.conf > /usr/local/.files
but it doesn't help to save this file. So, while there is no configuration 
option I suggest, the question is: how to save edited files in /etc?

Original issue reported on code.google.com by ache...@gmail.com on 27 Mar 2012 at 1:57

GoogleCodeExporter commented 9 years ago
nvram save
doesn't help too...

Original comment by ache...@gmail.com on 27 Mar 2012 at 2:11

GoogleCodeExporter commented 9 years ago
Someone tells me about virtual server method, but this is not acceptable. 
Rooter holes created (and deleted) dynamically by local machine's miniupnpc 
when it is needed, but virtual server require script which hardly sense local 
machine presence.

Original comment by ache...@gmail.com on 27 Mar 2012 at 2:55

GoogleCodeExporter commented 9 years ago
Sorry, we are unable to provide personal support. You have to read wiki & 
wl500g.info forum.

Additionally, by enabling privilege ports in UPNP, you make security hole.

Original comment by lly.dev on 27 Mar 2012 at 5:01

GoogleCodeExporter commented 9 years ago
>Additionally, by enabling privilege ports in UPNP, you make security hole.

I am well aware about it, and this is the case when my local network is 
absolutely trusted, so I need some way (I don't care which one) to bypass your 
completely unnecessary for absolutely trusted local network restriction.

Original comment by ache...@gmail.com on 27 Mar 2012 at 5:06

GoogleCodeExporter commented 9 years ago
check r4049

Original comment by themiron.ru on 31 Mar 2012 at 6:51

GoogleCodeExporter commented 9 years ago
Big thanks!

Original comment by ache...@gmail.com on 31 Mar 2012 at 6:54