home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugtracker Feed
0003437: Multiseat breaks if an additional IP for ipv4 has been added serverside
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MediaPortal-Bot" data-source="post: 868283" data-attributes="member: 48617"><p>TvServer/heartbeat is unable to handle additional IPs for ipv4 of IPv4.<br /> <br /> Usecase:<br /> - [Server] 1 NIC - local network + VPN<br /> - [Server]Main IP: i.e. 192.168.10.10<br /> - [Server]Alternate Configuration IP: 10.0.0.10<br /> - [Server]Streaming IP: 192.168.10.10<br /> - [Client] TV-Server connection configured on all clients as: 192.168.10.10 - not hostname<br /> <br /> As soon as you entered 10.0.0.10 as additional IPv4 IP serverside, then on all clients you will encounter a "Lost connection to TV_Server" when you try to tune a channel (might require a reboot of the client first).<br /> <br /> How to work around this issue clientside:<br /> - give the client 10.0.0.11 as additional IPv4 adress<br /> - or add "10.0.0.10 Servername" in the hosts file<br /> <br /> <br /> I think that this issue has to do with heartbeat failing badly. As if TVServer would start to accept communication only on the 10.0.0.10 adress. And since clients are not configured for that adress, heartbeat fails.</p><p></p><p><a href="http://mantis.team-mediaportal.com/view.php?id=3437" target="_blank">Continue reading...</a></p></blockquote><p></p>
[QUOTE="MediaPortal-Bot, post: 868283, member: 48617"] TvServer/heartbeat is unable to handle additional IPs for ipv4 of IPv4.<br /> <br /> Usecase:<br /> - [Server] 1 NIC - local network + VPN<br /> - [Server]Main IP: i.e. 192.168.10.10<br /> - [Server]Alternate Configuration IP: 10.0.0.10<br /> - [Server]Streaming IP: 192.168.10.10<br /> - [Client] TV-Server connection configured on all clients as: 192.168.10.10 - not hostname<br /> <br /> As soon as you entered 10.0.0.10 as additional IPv4 IP serverside, then on all clients you will encounter a "Lost connection to TV_Server" when you try to tune a channel (might require a reboot of the client first).<br /> <br /> How to work around this issue clientside:<br /> - give the client 10.0.0.11 as additional IPv4 adress<br /> - or add "10.0.0.10 Servername" in the hosts file<br /> <br /> <br /> I think that this issue has to do with heartbeat failing badly. As if TVServer would start to accept communication only on the 10.0.0.10 adress. And since clients are not configured for that adress, heartbeat fails. [url="http://mantis.team-mediaportal.com/view.php?id=3437"]Continue reading...[/url] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugtracker Feed
0003437: Multiseat breaks if an additional IP for ipv4 has been added serverside
Contact us
RSS
Top
Bottom