Opened 13 years ago
Closed 4 years ago
#10589 closed Bug Report - General (Won't Fix)
trying to get UPNP working
| Reported by: | Owned by: | dblain | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - UPnP | Version: | Master Head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
MythTV Version : v0.26-pre-34-gba0b3de-dirty MythTV Branch : master Network Protocol : 73 Library API : 0.26.20120411-1 QT Version : 4.8.0 Options compiled in:
linux profile use_hidesyms using_alsa using_jack using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
launched with mythbackend --log-level debug results
2012-04-12 23:03:31.579031 D MMulticastSocketDevice(239.255.255.250:36): setsockopt - IP_DROP_MEMBERSHIP eno: Invalid argument (22)
Above is repeated at least once a second
There is a firewall before the netgear, but does not block this subnet.
All devices on same subnet connected to dumb netgear switch UN40D6000 Samsung TV sees My PC Mythdvr sees nothing My PC can map a drive using samba to mythdvr mythdvr,TV,my pc have internet mythdvr firewall is off and iptables --list is (policy ACCEPT) for all
Attachments (3)
Change History (14)
comment:1 Changed 13 years ago by
| Milestone: | 0.26 → unknown |
|---|
comment:3 Changed 13 years ago by
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.3.1 0.0.0.0 UG 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN 5645/xinetd tcp 0 0 0.0.0.0:5801 0.0.0.0:* LISTEN 5645/xinetd tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 5463/mysqld tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3727/smbd tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 5645/xinetd tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN 5645/xinetd tcp 0 0 192.168.3.2:6543 0.0.0.0:* LISTEN 7752/mythbackend tcp 0 0 127.0.0.1:6543 0.0.0.0:* LISTEN 7752/mythbackend tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 4856/rpcbind tcp 0 0 192.168.3.2:6544 0.0.0.0:* LISTEN 7752/mythbackend tcp 0 0 127.0.0.1:6544 0.0.0.0:* LISTEN 7752/mythbackend tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 4847/vmware-convert tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 5121/perl tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN 4929/java tcp 0 0 127.0.0.1:4243 0.0.0.0:* LISTEN 4929/java tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 4899/sshd tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 5604/cupsd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 4847/vmware-convert tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3727/smbd tcp 0 0 192.168.3.2:22 192.168.3.54:59025 ESTABLISHED 6443/1 tcp 0 0 192.168.3.2:445 192.168.3.54:59287 ESTABLISHED 8027/smbd tcp 0 0 192.168.3.2:4242 192.168.3.54:59590 ESTABLISHED 4929/java tcp 0 0 192.168.3.2:22 192.168.3.54:59002 ESTABLISHED 6292/0 tcp 0 0 :::34570 :::* LISTEN 4688/java tcp 0 0 :::34571 :::* LISTEN 4688/java tcp 0 0 :::139 :::* LISTEN 3727/smbd tcp 0 0 :::34572 :::* LISTEN 4688/java tcp 0 0 :::34573 :::* LISTEN 4688/java tcp 0 0 ::1:6543 :::* LISTEN 7752/mythbackend tcp 0 0 :::111 :::* LISTEN 4856/rpcbind tcp 0 0 ::1:6544 :::* LISTEN 7752/mythbackend tcp 0 0 :::80 :::* LISTEN 6520/httpd2-prefork tcp 0 0 :::22 :::* LISTEN 4899/sshd tcp 0 0 :::631 :::* LISTEN 5604/cupsd tcp 0 0 :::445 :::* LISTEN 3727/smbd udp 0 0 0.0.0.0:5353 0.0.0.0:* 1049/avahi-daemon: udp 0 0 0.0.0.0:40198 0.0.0.0:* 2017/dhclient6 udp 0 0 239.255.255.250:58899 0.0.0.0:* 7752/mythbackend udp 0 0 0.0.0.0:44641 0.0.0.0:* 1049/avahi-daemon: udp 0 0 0.0.0.0:10000 0.0.0.0:* 5121/perl udp 0 0 239.255.255.250:1900 0.0.0.0:* 7752/mythbackend udp 0 0 255.255.255.255:51059 0.0.0.0:* 7752/mythbackend udp 0 0 0.0.0.0:111 0.0.0.0:* 4856/rpcbind udp 0 0 192.168.3.255:137 0.0.0.0:* 3703/nmbd udp 0 0 192.168.3.2:137 0.0.0.0:* 3703/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 3703/nmbd udp 0 0 192.168.3.255:138 0.0.0.0:* 3703/nmbd udp 0 0 192.168.3.2:138 0.0.0.0:* 3703/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 3703/nmbd udp 0 0 0.0.0.0:41166 0.0.0.0:* 7752/mythbackend udp 0 0 0.0.0.0:631 0.0.0.0:* 5604/cupsd udp 0 0 0.0.0.0:789 0.0.0.0:* 4856/rpcbind udp 0 0 :::34570 :::* 4688/java udp 0 0 :::34577 :::* 4688/java udp 0 0 :::34578 :::* 4688/java udp 0 0 :::34579 :::* 4688/java udp 0 0 :::34580 :::* 4688/java udp 0 0 :::14144 :::* 2017/dhclient6 udp 0 0 :::111 :::* 4856/rpcbind udp 0 0 :::177 :::* 5655/kdm udp 0 0 :::546 :::* 2017/dhclient6 udp 0 0 :::789 :::* 4856/rpcbind
comment:5 Changed 13 years ago by
I have added the log files from mythbackend -v upnp to help diagnose the problem.
comment:6 Changed 12 years ago by
I wrote a perl program which uses UPNP to detect UPNP capable devices. It sees my PC and the front room tv, but still no Mythdvr.
sample output:
[0] : [TV]UN40D6000 Manufactor Samsung Electronics manufacturer_url http://www.samsung.com/sec model_description Samsung RVU TV series 6 model_name UN40D6000 model_number AllShare1.0 model_url http://www.samsung.com/sec serialnumber <Hidden> udn uuid:5d83e28c-ea4a-4f38-a7ff-dc95f2f9ff66
Please advise:
I included my program so someone who has a working setup can test it. Note: <Device dependant> My program may output dozens of screens worth of text information.
I have updated to:
MythTV Version : v0.26-pre-388-g29ca559-dirty MythTV Branch : master Network Protocol : 74 Library API : 0.26.20120509-1 QT Version : 4.8.1
My UPNP devices can't see mythtv nor does mythtv see them.
comment:7 Changed 12 years ago by
Try to apply this fix #11111 and see if it helps with UPNP discovery.
comment:8 Changed 12 years ago by
@spamme please keep responses in this ticket.
I have tested upnp-locator 0.2.2 with MythTV 0.25 + fix #11111 and the myth server is discovered.
could you provide a log running mythbackend -v upnp ? and could you provide the 'getDeviceDesc' file you get from:
"wget http://<IP to mythbackend>:6544/getDeviceDesc"
comment:9 Changed 12 years ago by
no luck
<?xml version="1.0" encoding="utf-8"?> <root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:mythtv="mythtv.org"> <specVersion> <major>1</major> <minor>0</minor> </specVersion> <URLBase>http://mythbackend:6544/</URLBase> <device> <deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType> <friendlyName>mythdvr: MythTV AV Media Server</friendlyName> <manufacturer>MythTV</manufacturer> <modelURL>http://www.mythtv.org/</modelURL> <modelName>MythTV AV Media Server</modelName> <manufacturerURL>http://www.mythtv.org/</manufacturerURL> <modelDescription>MythTV AV Media Server</modelDescription> <modelNumber>0.26.20120822-1</modelNumber> <serialNumber>v0.26-rc2-30-g272fb61-dirty</serialNumber> <presentationURL>/</presentationURL> <mythtv:X_secure>false</mythtv:X_secure> <mythtv:X_protocol>75</mythtv:X_protocol> <dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMS-1.00</dlna:X_DLNADOC> <UDN>uuid:0705d747-7b55-415d-b2cf-d9517014cb7d</UDN> <serviceList> <service> <serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType> <serviceId>urn:upnp-org:serviceId:CMGR_1-0</serviceId> <SCPDURL>CMGR_Control/GetServDesc</SCPDURL> <controlURL>CMGR_Control</controlURL> <eventSubURL>CMGR_Event</eventSubURL> </service> <service> <serviceType>urn:schemas-upnp-org:service:ContentDirectory:1</serviceType> <serviceId>urn:upnp-org:serviceId:CDS_1-0</serviceId> <SCPDURL>CDS_Control/GetServDesc</SCPDURL> <controlURL>CDS_Control</controlURL> <eventSubURL>CDS_Event</eventSubURL> </service> </serviceList> </device> </root>
comment:10 Changed 12 years ago by
I am using the latest build from git version 26 so something else must have changed since them also.
Please don't set the Milestone on tickets.
What is the output of /sbin/route -n on your backend machine?