Hello,
I've attached a second patch. This patch changes VDR's svdrp port handling in the following way: If only the localhost item is found in svdrphosts.conf, then the port is attached to "INADDR_LOOPBACK", which makes it impossible to reach the port from outside. As soon as even one additional item is added, the port is opened to "INADDR_ANY", again, so the port is accessible from network. This way, the default configuration of VDR is "rock solid" and there should be no need to disable svdrp at all. We also have no additional configuration mechanisms. The user only has to work with svdrphosts.conf, as he did with previous VDR versions.
CU
Manuel
Sorry to make things complicated, but would it not satisfy everybody needs if you could bind to an ip address, which could be any one you specify? For example, I would prefer mine to be bind to my eth0's ip for internal lan clients to connect, but not accessible via ppp0 for example.
So I guess what I'm asking is, if you could start vdr with a listen parameter switch and could specify for each listen switch a source ip address or even a interface name?
Theunis
2010/1/9 Manuel Reimer Manuel.Reimer@gmx.de:
Il 09/01/2010 18:10, Theunis Potgieter ha scritto:
Right!!!
From a simple user (not a technical one) i appreciate an item menu so i
can set the local IP to enable, without need to modify configuration files on the file system.
That's a simple, functional and easy solution, obvious IMHO.
Diego
Theunis Potgieter wrote:
... where we would be back at my first patch, which added the possiblity to specify the svdrp port in the way "$IP:$PORT".
Maybe it would be an idea to combine the two. If the IP is given at command line with the -p switch, then this setting is preferred. If the IP isn't given at command line, then it is 127.0.0.1 if svdrphosts.conf only contains "127.0.0.1" and 0.0.0.0 otherwise.
IMHO we shouldn't get too complicated at this point, as it isn't VDRs main usage to be a network daemon, unlike apache, where there are much more and much more complicated ways to listen to one or multiple ports and to filter based on IP.
CU
Manuel
I was just about to prepare a patch which does this, and apart from the naming of functions it looks _identical_ to this one. So it has to be correct :-) (I've also tested that this works with empty or missing svdrphosts.conf too, although in this case we could as well disable SVDRP entirely.)
Documentation and sample is correct in this case, too.
Olaf
-
Diego Pierotto -
Manuel Reimer -
Olaf Titz -
Theunis Potgieter