wrong streaming-ip destroys tvserver (1 Viewer)

[ownagi]

TV-Server Version: 1.02
MediaPortal Version: 1.02
MediaPortal Skin: blue3wide
Windows Version: Vista 32bit
CPU Type: 3000+ A64
HDD: wd/hitachi
Memory: 1gb singlechannel
Motherboard: asrock nf6
Video Card: onboard
Video Card Driver: 15.24
Sound Card: onboard
Sound Card AC3: onboard
Sound Card Driver: 15.24
1. TV Card: technisat skystar2
1. TV Card Type: dvb-s
1. TV Card Driver: 4.5.0a
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: ffdshow
MPEG2 Audio Codec: ffdshow
h.264 Video Codec: ffdshow
Satelite/CableTV Provider: ??
HTPC Case: gd02
Cooling: stock
Power Supply: seasonic s12ii 380w
Remote: mce remote receiver + harmony 555
TV: 32r8 samsung / epson tw700
TV - HTPC Connection: dvi-hdmi, hdmi-hdmi


Problem:

Switching the Streaming-IP to an IPv6 crashes the server and lets the server-console hang
retrying to start the server console fails becuase of wrong config i cant start the service anymore

seems theres a parsing problem ...

log:
2009-05-31 21:34:44.888737 [12]: RemoteControl: Error getting server Instance - Ungültiger URI: Wegen eines vorhandenen Doppelpunkts (":") wurde ein Anschluss erwartet, aber der Anschluss konnte nicht analysiert werden.
2009-05-31 21:34:44.904337 [12]: card: unable to connect to slave controller at:fe80::4ac:20e5:325d:b070%10
2009-05-31 21:34:44.904337 [9]: RemoteControl: Error getting server Instance - Ungültiger URI: Wegen eines vorhandenen Doppelpunkts (":") wurde ein Anschluss erwartet, aber der Anschluss konnte nicht analysiert werden.
2009-05-31 21:34:44.904337 [9]: card: unable to connect to slave controller at:fe80::4ac:20e5:325d:b070%10
2009-05-31 21:34:45.965137 [SetupTv]: Exception ystem.Net.Sockets.SocketException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen

 

[infinite.loop]

IPV6 is simply not supported.

 

[tourettes]

IPV6 is simply not supported.

Then the bug is that config allows IPV6 to be selected Pretty big bug in my opinion as resolving the issue will require manual editing in DB.

 

[ownagi]

thats the point
you have to undo the settings manually because the config does not start due to the fact the server can not be started

 

[infinite.loop]

thats the point
you have to undo the settings manually because the config does not start due to the fact the server can not be started

actually we should consider to support ipv6.
team is discussing that allready.

 

[mnetzband]

manually reset stream ip to ipv4

Hello,

can you please describe where to reset the stream ip?

Thx.