Topic: Tivo and SQUID

[Mark030]

I ran into a problem when trying to get my Tivo Series 2 connected to the Internet.  After an hour of wasted time and a few google searches, the answer was to disable the transparent proxy feature of SQUID.

To do this I issued the following commands:
/sbin/e-smith/db configuration setprop squid Transparent no
/sbin/e-smith/signal-event remoteaccess-update

If anyone has a better way or a fix for SQUID, please let me know, I kinda like the proxy to be transparent, but this works for now.  I hope this helps other Tivo & SME users as well.

- Mark

[Mark030]

Neglected to metion the versions I am running:

SME Server v6.0.1-01
squid-2.4.STABLE6-6.7.3

Thanks,
- Mark

[cc_skavenger]

Mark, do you get any errors in the squid cache log stating an error about max header size....this is a problem I had with some of my customers and replay TV.  If you do, then add the following command to the /etc/squid.conf file via the templating system:

request_header_max_size 25 KB  

This should allow a larger request header, something that REPLAY TV and TiVO need.

hope this helps

Marco

[Mark030]

I just re-enabled it and watched the logs like a hawk and did not see any errors.  I checked the squid.conf and the request_header_max_size was 5 MB, I tried setting it to 25 KB to no avail.  

Like I said, it works as long as SQUID is set to transparent and I can always manually enter the proxy server.  Thanks for the suggestion.

- Mark

[RayG]

What was the problem you were having with the TIVO ?

Have you tried loading Squidguard and entering the TIVO's ip as unfiltered ? You can also try setting up the domains the TIVO is trying to access as 'always direct'.

[dzink]

Thanks for this post, Mark.  I had the same problem and your workaround is good enough for me.  For anyone interested, the real problem is detailed in the following text that I found on the www.tivocommunity.com bulletin boards:


I believe Smoothwall runs Squid as a transparent proxy. The problem is that Squid is a HTTP/1.0 proxy and is not fully HTTP/1.1-compliant. TiVo expects to connect to a HTTP/1.1 server, but Squid chokes on certain valid HTTP/1.1 requests.

A zero-length POST patch for Squid has been available for some years which fixes the main interoperability problem with TiVo. It would be nice if TiVo would also change their requests to work through potential HTTP/1.0 proxies instead of expecting to be able to connect to a HTTP/1.1 server or proxy.

[jamesd1343]

Ive read about the path for squid but m a newbie and have no idea how to implement this on my esmith...can someone provide me with guidance.

Id rather not disable transparent proxy if I dont have to