Routing Problem?
#1
Hi,
I do hope this is the correct thread to post this in, apologies if not.
It might also be specifically an OpenELEC problem, but I thought I'd try here first.

Our setup:
Raspberry Pi 2 running OpenELEC / Kodi, with a USB HDD connected, our CDs and DVDs ripped to the HDD. RPi is wired to my (Virgin Media) router, and connected via CEC/HDMI to our Sony Bravia TV. The TV is also wired to the router.

PCs around our home use a local installation of Kodi to access the media centre and it's hard drive, hence able to access music and movies.
Smartphones and tablets use Bubble UPnP to access our media centre.

Where we can use the media centre:
On our TV, and on the PCs that are wired to the router.
Also on tablets and phones anywhere in our home via Bubble UPnP.

Where we can't use the media centre:
On any PC that is wireless connected to our LAN. It seems as though our media centre sees this as a separate network and won't talk to it (?)

Any clues?

Thanks in advance.
Reply
#2
On one of your PC's that are wired, list its ip address

On one of your wireless clients, list its ip address
Reply
#3
Wired: 192.168.0.4
Wireless: 192.168.0.25

Cheers
Reply
#4
Hrmmm, you are on the same subnet so thats not the problem. Can you ping your media center via one of your wireless clients?
Reply
#5
Yup, no problem:
mark@UbuntuLaptop:~$ ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=20.1 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=1.96 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=5.73 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=64 time=1.10 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=64 time=1.03 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=64 time=3.61 ms
64 bytes from 192.168.0.2: icmp_seq=7 ttl=64 time=1.24 ms
64 bytes from 192.168.0.2: icmp_seq=8 ttl=64 time=27.6 ms
64 bytes from 192.168.0.2: icmp_seq=9 ttl=64 time=1.11 ms
^C
--- 192.168.0.2 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8011ms
rtt min/avg/max/mdev = 1.039/7.069/27.627/9.284 ms
mark@UbuntuLaptop:~$

Frustrating, isn't it?

What I've done as an interim solution is run up a spare Raspberry Pi as a second media centre, connected wirelessly to our router, and plugged the backup USB HDD into that (we keep two copies, just in case, and the original CDs and DVDs in the garage just in case in case). That's working but it's not ideal, ideally all client devices should be pointed at the one media centre!

Cheers.
Reply
#6
Ok so we know its not a networking issue. Can you actually describe how its not "talking" to the media center? As in, when you are trying to add a source from within Kodi its not showing up in the list of networking places, or something else?
Reply
#7
Yes that's right, when I try to add a source from within Kodi it's not showing up in the list of networking places. Also if I type in the UPnP or other address long hand it still can't access the media centre, it says it's not connected (or something like that) and would I like to add the source anyway?

Cheers.
Reply
#8
And if I add the source anyway it fails (won't connect) when I try to open that source.
Reply
#9
Would you enable debug logging, re-open Kodi and try to manually enter in the smb:// location of the source? Exit kodi and upload a debug log to pastebin?
Reply

Logout Mark Read Team Forum Stats Members Help
Routing Problem?0