Opened 12 years ago
Closed 5 years ago
#11143 closed Bug Report - General (Abandoned)
Ceton usb infinitv will not connect in version 0.26
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - General | Version: | 0.26 |
Severity: | low | Keywords: | Ceton usb |
Cc: | Ticket locked: | no |
Description
I have downloaded,built, and installed mythtv 0.26 hoping that i would be able to connect my usb Ceton infinitv. However, it will not connect despite the bug fix for that problem in the 0.26 version. Using tcpdump, i see a lot of SSDP advertisements from the Ceton, but there is never a connection. The Ceton user-space driver for the usb box has been built and installed.
Attachments (1)
Change History (6)
comment:1 Changed 12 years ago by
Priority: | major → minor |
---|---|
Severity: | high → low |
Status: | new → infoneeded_new |
Version: | Unspecified → 0.26 |
Changed 12 years ago by
Attachment: | ceton.pcap added |
---|
.pcap file captured while attempting to use the backend config tool to connect to usb ceton box
comment:2 Changed 12 years ago by
Please let me know what other supporting data you need to pursue this. The usb0 interface has an ip of 192.168.180.3. Note that the device also seems to have an http service at 192.168.180.1, from which most of the packets are delivered. There are no firewalls running on the host computer. I have also attempted to use the 192.168.180.1 address as the connect address in the configuration, but, that failed as well.
comment:3 Changed 12 years ago by
Status: | infoneeded_new → new |
---|
comment:4 Changed 10 years ago by
Hi. I am having the same problem, running the latest Mythbuntu version (downloaded 1 week ago (4/7/2015). Did you find a solution? I'm also working with Ceton support, who are trying to be helpful, however they haven't found a solution yet.
I'm happy to provide any/all logs. Thanks, Neil
comment:5 Changed 5 years ago by
Resolution: | → Abandoned |
---|---|
Status: | new → closed |
Closing out old tickets.
Any logs, tcpdumps or other relevant information forthcoming? If not, I'm going to close this ticket as invalid. There's simply not enough information in this ticket for a developer to be able to spot the issue, without having access to such a device and being able to replicate the issue.
Have you disabled all firewalls etc?