Client Over Wan

[needbb]

Well I think I am the first to attempt this I am using the 15 day trial to see if I could stream my recorded shows and live TV over the internet. I have set up the SageTV server and it works great with the client connected on the LAN. On my remote location, the client will start up but many times I get the "the connection to the TV server has been lost..." error. I have plenty of bandwidth on both sides as the server is connected to a 155mbps fiber line while the remote client has a 15mbps fiber line. Just to make sure I had enough bandwidth, I did some ftp downloads from the server to the client and it went at 1.2MB/s. Using the client on the LAN only uses around .5-.6MB/s. The ping times to the server is less than 50ms with zero packet loss. The server is on a public IP address (no NAT) and has the proper ports forwarded. The client pc also has the same ports forwarded.

I have tried messing with the client_gc_period under the sageclient config and it has helped. Are there any other tweaks that I can do to allow sage to work with multiple hops and ping times over 10+ms?

Thanks

[Opus4]

Instead of using the regular client over the internet, have you looked into the Placeshifter client in the latest betas? (See the Beta Test forum section.)

- Andy

[needbb]

Well my server isn't fast enough for placeshifting. The connection between the server and client is plenty of fast enough. There is some issue with the client and how the timeout is set. Is there any way to change the timeout or better adapt it for multiple hops on a network?

[gplasky]

Set the Placeshifting client for no transcoding. You have a better chance of getting this working than trying to get the client meant for a LAN to work over a WAN.

Gerry

[needbb]

The placeshifting client worked, but I would still like to use the regular client until all the bugs are worked out. Is there any techical reason (IE in the JAVA code) that steaming over a WAN won't work? Is the 35ms delay between server and client too long?

Here is a speed test example:

running 10s outbound test (client to server) . . . . . 71.88Mb/s
running 10s inbound test (server to client) . . . . . . 68.12Mb/s

Thanks

[nielm]

I think the client has shorter network timeouts than the placeshifter, so its not so much the bandwidth, but the latency...

However:

remote client has a 15mbps fiber line.
...ftp downloads from the server to the client and it went at 1.2MB/s.
...running 10s inbound test (server to client) . . . . . . 68.12Mb/s

1.2Mbytes/sec ~= 15Mbits/sec, so that makes sense
But how did you manage to get 68MB*/sec (either bits or bytes) over a 15mbit link?

In any case, 15mbit is really at the limit for streaming MPEG2 -- people have had problems streaming over 802.11b 11mbit WLANS...

[needbb]

I got it working. I had to use a VPN tunnel between the server and client. The vpn tunnels 2x the bandwith, but Sagetv is only using 1MB/s.

[Speedy64i]

Could you elaborate on how to set this up? I have the exact same problems you descibe in the beginning of this thread and would LOVE to get it to work.

Thank you,

JT

[needbb]

I used OpenVPN to connect both machines, and used the vpn server's IP address to connect using Sage Client.