search

pipelka / vdr-plugin-xvdr

DISCONTINUED - XVDR Plugin for VDR
GNU General Public License v2.0
43 stars 22 forks source link

switching between ipv4 and ipv6 #84

Closed pwgen closed 11 years ago

pwgen commented 11 years ago

it will be nice to have a config option to force the usage of ipv4, it seems that the server allways opens an ipv6 socket when ipv6 is available .

pipelka commented 11 years ago

yes. whats wrong with ipv6 ? does there any disadvantage arise out of this behaviour ?

manio commented 11 years ago

@pwgen Opening IPv6 socket when available is a intentional action. I am using IPv6 since I introduced it - and it works as fine as without it. Maybe you have some network misconfiguration?

pwgen commented 11 years ago

On 02.01.2013 09:02, Mariusz Białończyk wrote:

@pwgen https://github.com/pwgen Opening IPv6 socket when available is a intentional action. I am using IPv6 since I introduced it - and it works as fine as without it. Maybe you have some network misconfiguration?

— Reply to this email directly or view it on GitHub https://github.com/pipelka/vdr-plugin-xvdr/issues/84#issuecomment-11801775.

i was using xmbc on an embedded client( rasp) and the xvdr plugin on the vdr server. netstat showed the 34891 socket only on an tcp6 socket. so i was wondering how the client should could connect to it because i could configure only ipv4 address for the vdr-xvdr server.

/eric

pwgen commented 11 years ago

On 02.01.2013 02:05, Alexander Pipelka wrote:

yes. whats wrong with ipv6 ?

usually , noting.

does there any disadvantage arise out of this behaviour ?

my vdr server opened the xvdr port only on the ipv6 address.

and my xbmc client could not connect to ipv6 vdr servers.

/eric

pipelka commented 11 years ago

you mean something like:

tcp6 0 0 :::34891 :::* LISTEN 0 1749330 32343/vdr

no problem at all. my clients also use the IPv4 address to connect.

manio commented 11 years ago

From my experience it seems that netstat sometimes behave strange in this manner on different platforms, therefore the best way to test it is eg just:

telnet -4 localhost 34891
telnet -6 localhost 34891

and it is connecting in both cases