turingmachine / omxplayer-sync

OMXPlayer-Sync facilitates synchronization of multiple OMXPlayer instances over the network in a master/slave fashion.
194 stars 70 forks source link

network is unreachable #37

Closed burtonworldart closed 8 years ago

burtonworldart commented 8 years ago

Cool software, thank you. Is wifi dongle and LAN required for this to run? when I play master (sudo omxplayer-sync -muv /home.pi/videos/syntest.mp4) won't work unless I am connected to my home wifi network. Will it run point to point via RJ45 alone? Does it require RJ45 crossover cables?

Thanks for your help!

Francesc116 commented 8 years ago

I tested the LAN. It works too under Wheezy.

Pi 1 $ sudo nano /etc/network/interfaces Delete iface eth0 inet dhcp. In fact, all the lines with eth0 info Add

iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 gateway 192.168.0.254

Pi 2, the same but iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.254

It works to me. Maybe it helps.

burtonworldart commented 8 years ago

Ah Ha! Thanks a lot! I was missing the gateway 192.168.0.254. Still encountering major deviation in sync across rj45 cable but at least both pis are on the same network.

turingmachine commented 8 years ago

@burtonworldart what exactly is your issue you have with the software? The title of this thread reads "network is unreachable". Do you still have network connectivity problem? If not please let the thread know so this issue can be closed. If you encounter other problems, please open a separate issue for each problem. This common netiquette in open source communities.

Below some guidelines that explain what I mean:

Be precise: don’t wander around and go straight to the point, describing as precisely as possible what’s happening Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug Be economic: provide the minimum amount of information needed to understand what’s happening Be clean: report only one problem per issue so we can track individual issues Be curious: has it been asked before? is it really a bug? Google is your friend!

http://www.kurento.org/blog/kurento-issue-tracker-guidelines