[mythtv-users] Ceton card not being found

[Ronald Frazier]

Have you figured out anything more on this? I've been thinking but
can't really come up with any ideas. If you want to give me ssh
access, I can try to poke around at it and see if I can figure
anything odd in the setup that would cause it. If so, my IP is
96.27.87.28 in case you need to poke a hole in the firewall.

---
Ron Frazier



On Wed, Jan 16, 2013 at 10:44 PM, brendan kearney <bpk678 at gmail.com> wrote:
> no firewall locally...
>
> [brendan at desktop Downloads]$ sudo iptables -nL
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> [brendan at desktop Downloads]$ sudo ip6tables -nL
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> proxy is running, but because i have a locally connected interface and an
> exception in place for the 192.168.200.1 address, the traffic goes direct
> and i have confirmed this in both proxy logs and wireshark.
>
> [brendan at desktop Downloads]$ sestatus
> SELinux status:                 disabled
>
> What OS/version are you running? Fedora 17 64bit / Gnome 3
> What version of myth? mythbackend version: fixes/0.26 [0.26.0-1.fc17
> (v0.26.0-28-ge3087dd)] www.mythtv.org
> What version of Qt? 4.8.4 (release 6.fc17)
> What version of the Ceton driver?
> ceton_infinitv_linux_driver_2012_1116_1219.tar.gz
> What version of the Ceton firmware? ceton_infinitv_fw_20120313_1_1_7_2.IMAGE
>
> [brendan at desktop ~]$ nc 192.168.200.1 80
> GET /get_var.json?i=0&s=diag&v=Host_IP_Address
> 1d
> { "result": "192.168.200.1" }
> 0
>
> since F18 is now out, i planned on moving to it.  i normally skip the odd
> releases, but had to use 17 since 16 would not install on this pretty new
> machine.  when i do move to 18, and have a very fresh build with no heavy
> customization, such as proxy, i will try to see if i still get this weird
> issue.  i wont be moving to it just yet, so more debugs can be done on what
> i have running now.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>



-- 
Ron Frazier