Subnet mask

[baxy]

I have the original consumer ouya unmodded no root and latest firmware and I am unable to connect to my live tv server and mediabrowser3 server which both run on the same machine, all of the other devices I own don't have a problem. .. its just the ouya

[cabji]

Hi everyone,

I believe I have this same issue, but I only noticed it after setting up tvheadend on my server and then trying to stream it via Wifi to the Ouya. Initially I set all the software up (server on the server and client on the Ouya) and got it going while the Ouya was on ethernet cable connection. Happy with its performance and that it was working I then moved the Ouya outside on a monitor and tried to get it working. No dice.

I tried restarting the tvheadend server software, reinstalling the tvheadend client software etc. etc. nothing worked. I then did some network diagnostics. The Ouya could see the gateway and access the internet. It couldn't see the server on my internal LAN (at least) as xbmc's log was telling me "no route to host" when I would run tvheadend client.

From my server (running Linux) it could access internet, see the gateway and ping it, but it could not see the Ouya at all. No ping. I thought it was a routing issue with my router (which is also the gateway) but I can access the server from any other wirelessly connected LAN clients, so don't think it is a routing issue. I figured it could be a netmask issue but for me the Ouya has worked for all other application except tvheadend and the stock UI reported my netmask as 255.255.255.0 which should work afaik.

After all of this, I plugged the Ouya back into the ethernet connection and tvheadend works flawlessly! So zeroing in on a problem with Wifi specifically for me.

[bluefish]

I also have this and cant change it ??

[Eldon.McGuinness]

Hi guys, for those of you having issues like this please make sure you post the following

• IPs and subnet masks of the OUYA and server
• ping, both to the ouya from the server and from the ouya to the server
• does the software use netbios to discover shares/sources? If so try adding entries to your /etc/hosts file on the OUYA.
• the port ranges the OUYA is getting INCOMING traffic on, note I said INCOMING as outgoing should be wide open.

[bluefish]

Hi guys, for those of you having issues like this please make sure you post the following

• IPs and subnet masks of the OUYA and server
• ping, both to the ouya from the server and from the ouya to the server
• does the software use netbios to discover shares/sources? If so try adding entries to your /etc/hosts file on the OUYA.
• the port ranges the OUYA is getting INCOMING traffic on, note I said INCOMING as outgoing should be wide open.

hi Eldon can I ask how would I do this ??? as I cant get past this . please look at post 19 http://ouyaforum.com/showthread.php?...ya-store/page2

thanks

[Eldon.McGuinness]

Sorry mate, I have never liked WiFi and use a powerline ethernet adapter instead. The only thing I could think of would be to try and turn off all authentication and encryption on your router, make it a public access point, and see if that fixes it, if not try a factory reset on the device. If making it public fixes it then it is likely the encryption or authentication scheme that is being used.

As for obtaining the network data you will need to check the server for the server's information and the OUYA for the OUYA's (over adb), these are all command line based applications/commands:

• Windows - ipconfig /all
• Linux/Android/OUYA - ip addr show (This might work on Mac OS as well)

You can ping the devices by running:

• ping IPADDRESS

As for the netbios and ports, you will need to query the application developers of the applications you are trying to use.

[bluefish]

[QUOTE=Eldon.McGuinness;162180]Sorry mate, I have never liked WiFi and use a powerline ethernet adapter instead. The only thing I could think of would be to try and turn off all authentication and encryption on your router, make it a public access point, and see if that fixes it, if not try a factory reset on the device. If making it public fixes it then it is likely the encryption or authentication scheme that is being used.

As for obtaining the network data you will need to check the server for the server's information and the OUYA for the OUYA's (over adb), these are all command line based applications/commands:
[LIST][*]Windows

thanks have same problems with hardwird also have tried my ouya in m8s house also and get same problems yet his ouya works ???


thanks

[Eldon.McGuinness]

I would try a factory reset and if that does not work I would try to enter the recovery console and clear the app/user data and cache, then sideload the latest update to it.

You can get the latest firmware HERE.

[bluefish]

once again thank for your time I have done a factory reset and cleared the app/user data and cache with usb keyboard could I please ask how would I do a sideload update ??? thanks

I would try a factory reset and if that does not work I would try to enter the recovery console and clear the app/user data and cache, then sideload the latest update to it.

[Eldon.McGuinness]

You will need the ADB application, which you can get as part of [ ReRoot ], and then boot back into that console and choose the option that mentions updating from ADB. You will need to hook your OUYA to your computer via the USB cable, the drivers for this are also in the ReRoot package, and then download the latest update and place it in the same directory as the ADB command. Then only the OUYA is asking you to sideload the the firmward use the following command to send it:

adb sideload RC-OUYA-1.2.1378-r1_ota.zip

Edit:
You can also get the latest link from the [ RSS ] feed I just made.