The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump.
While this is not a major issue I'd prefer to register an "official" port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that.
Any comments/ objections?
Best regards, Christian
On 4 March 2010 13:44, Christian Tramnitz chris.ace@gmx.net wrote:
The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump.
While this is not a major issue I'd prefer to register an "official" port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that.
Any comments/ objections?
A lot of changes is required if from end user perspective. Nothing that can't be fixed in a few minutes. Would this then imply that plug-ins like streamdev (network plug-ins) should also register?
Best regards, Christian
Am 04.03.2010 13:00, schrieb Theunis Potgieter:
A lot of changes is required if from end user perspective. Nothing that can't be fixed in a few minutes.
No change is required from end-user perspective in the end when the plugins/extensions are adapted to the new port. (In the current vdr-dev 1.7.x most plugins also have to be adopted to work with the latest version so this is not really an issue, see cChannel changes in 1.7.13). Also, for experienced users (and 1.7.x is still a "dev" version) changing a port number in the config (or worst case in the plugin source code) shouldn't be too complicated either.
Would this then imply that plug-ins like streamdev (network plug-ins) should also register?
streamdev, live and vdradmin are not using its own protocol but http (on a non-standard port). The reason for not using a standard port is that port 80 will be already in use, so using a non-standard port is feasible.
Best regards, Christian
Am 04.03.2010 13:00, schrieb Theunis Potgieter:
On 4 March 2010 13:44, Christian Tramnitz chris.ace@gmx.net wrote:
The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA.
that can't be fixed in a few minutes. Would this then imply that plug-ins like streamdev (network plug-ins) should also register?
My VDR machine currently opens these ports:
2001 dc (SVDRP) 2002 globe (remote-telnet, user-assigned) 2004 mailbox (streamdev VTP) 2010 search (osd-server) 3000 remoteware-cl (streamdev HTTP) 8008 http-alt (live-plugin) 37890 (unassigned) (xineliboutput)
I'm sure that's not anywhere near all the ports that are used by VDR and various plugins. Would be a lot to register IMHO.
Cheers,
Udo
Hi,
epgsearch uses SVDRP for timer programming. Although the port can be configured in epgsearch's setup a change of the default port would probably cause some support. Plugins can not read vdr's SVDRP port til now, so it would be great to have any function for this and a change of the default would do no harm.
BR, Christian
Christian Tramnitz schrieb:
The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump.
While this is not a major issue I'd prefer to register an "official" port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that.
Any comments/ objections?
Best regards, Christian
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 4 March 2010 22:02, Christian Wieninger cwieninger@gmx.de wrote:
epgsearch uses SVDRP for timer programming. Although the port can be configured in epgsearch's setup a change of the default port would probably cause some support. Plugins can not read vdr's SVDRP port til now, so it would be great to have any function for this and a change of the default would do no harm.
The client can check if svdrp is defined in /etc/services, and use the new "official" port from there, otherwise default to 2001.
On 04.03.2010 12:44, Christian Tramnitz wrote:
The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump.
While this is not a major issue I'd prefer to register an "official" port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that.
Any comments/ objections?
I like port 2001 - why stir this up and cause turmoil amoung all those who have been using the default port for so long?
What are services "dc" and "wizard", anyway?
Klaus
Am 04.03.2010 23:08, schrieb Klaus Schmidinger:
I like port 2001 - why stir this up and cause turmoil amoung all those who have been using the default port for so long?
What are services "dc" and "wizard", anyway?
Klaus
I understand that you don't want to touch this, but you are also regularly blaming broadcasters for not obeying DVB standards so what is wrong with following TCP/IP standards?
http://www.iana.org/assignments/port-numbers Ports between 0-49151 are managed by IANA, ports above 49151 may be used without reservation as they are in the dynamic/private range.
Best regards, Christian
On 05.03.2010 13:05, Christian Tramnitz wrote:
Am 04.03.2010 23:08, schrieb Klaus Schmidinger:
I like port 2001 - why stir this up and cause turmoil amoung all those who have been using the default port for so long?
What are services "dc" and "wizard", anyway?
Klaus
I understand that you don't want to touch this, but you are also regularly blaming broadcasters for not obeying DVB standards so what is wrong with following TCP/IP standards?
I was afraid this would fire back at me one day ;-)
http://www.iana.org/assignments/port-numbers Ports between 0-49151 are managed by IANA, ports above 49151 may be used without reservation as they are in the dynamic/private range.
Well, maybe having an "svdrp" entry in /etc/services wouldn't be that bad after all...
Klaus
I wonder if this really is a problem. In all my years of using VDR I've never heard of a single complaint about the SVDRP port. However, everyones needs/setup is different so may there is a "real" issue that I'm unaware of. Could someone give a couple real world (ie: not what-if's) examples of when this causes problems?
Best regards, Derek
-
Christian Tramnitz -
Christian Wieninger -
Klaus Schmidinger -
Theunis Potgieter -
Torgeir Veimo -
Udo Richter -
VDR User