View Full Version : Streaming over wired LAN issue
I'm using my Viper V40 box in client mode with the latest version of OpenVIX.
It will run quite happily over wireless without issues.
Whenever I use the wired ethernet socket the box will freeze - takes anywhere between 5 mins to 1 hour before this happens. No error messages, reboot etc. Box locks up.
While troubleshooting I've tried OpenATV 6.4 and 7.1/7.2 and experience the same issue.
Am I right in assuming that it's a hardware fault?
Well, it could be that the wired interface has been configured with an IP address that is the same as something else that only runs intermittently.
Both the wireless and wired interfaces were using DHCP. Nevertheless, I have now tried assigning a fixed IP outside of the DHCP address pool. After 10 mins the box locked up.
Worth mentioning it's not just the picture that freezes, the whole box becomes unresponsive to remote input/power button on front etc
Both the wireless and wired interfaces were using DHCP. Nevertheless, I have now tried assigning a fixed IP outside of the DHCP address pool. After 10 mins the box locked up.
Worth mentioning it's not just the picture that freezes, the whole box becomes unresponsive to remote input/power button on front etc
Post debug log
A shot in the dark as where might EPG saving to?
As suggested, here's the log. I'm just an end user so most of the log means nothing to me. Hopefully someone more knowledgeable can find something that might lead to a resolution.
The eth0 broadcast address is wrong.
It should be 192.168.200.255 (assuming you have a standard class C address network).
I can't see how to set the broadcast address within the OpenVix UI. I'm only using a fixed IP because I'd inferred from your earlier suggestion that there might be an issue with DHCP leases.
Can you tell me how to change the broadcast address or should I go back to DHCP?
..so I've given the STB a static IP in my routers DHCP server outside of the main DHCP pool. I've checked the log and DHCP is assigning the correct broadcast address. If I have further freezing, I'll post a log again.
Started my box up from cold this evening and it ran for 2 3/4 hours before locking up. This is an unusually long time for it to run without freezing, typically it's within 20-40 minutes.
I've attached the log.
When you say from cold from what ?
Deep Standby
Powered on from rear
On from standby
May i ask why you are turning box off at rear as most of use the standby or deep standby selection.
Powered on from rear.Does that mean you switch it off when not watching just by using that same switch?
Another things I can see, which might be irrelevant to the problem, but may not be totally irrelevant:
< 34.2554> 17:51:19.1222 [ChannelsImporter][checkEPG] Force EPG save on remote receiver...
< 34.2556> 17:51:19.1224 [ChannelsImporter][saveEPGonRemoteReceiver] URL: http://192.168.200.23/api/saveepg
< 34.3158> 17:51:19.1826 [ChannelsImporter][saveEPGonRemoteReceiver] ERROR: HTTP Error 401: Unauthorized
Does that mean you switch it off when not watching just by using that same switch?
I do this as after the box has crashed, it's not possible to put it in/out of standby.
Another things I can see, which might be irrelevant to the problem, but may not be totally irrelevant:
If we go back to my original post which stated that streaming works flawlessly over wifi, I will look to see if the same error occurs over this connection. If it does, then would rule it out as a cause of the lan port locking up?
[QUOTE=adsk;530661...then would rule it out as a cause of the lan port locking up?[/QUOTE]Yes. It would rule it out as a direct cause.
Yes. It would rule it out as a direct cause.
So I've now tested the box with wifi and it has these same errors but, as stated previously, runs without locking up. I can access the EPG successfully on the client box (in both wired and wireless modes) and if I understand the next few lines of code that follow the error, the box tries another method of downloading the epg which evidently works successfully.
For a bit of history, I've been using Client Mode via a wired ethernet connection for about 3 years. Initially I used a Edision OS Mega and the Viper V40 replaced this. In another room, I've got a Viper 4K51 also connected by wired ethernet. I've never experienced this freezing that I'm getting through the wired ethernet of the V40 with the other 2 boxes.
That's the reason for my suggestion that it might be a hardware fault. I suppose a driver issue could be to blame but wouldn't that show up in the logs somewhere?
I suppose a driver issue could be to blame but wouldn't that show up in the logs somewhere?Only if the driver spotted the error.
If A is waiting for B while B is waiting for A then neither will report anything.
@adsk
< 34.2554> 17:51:19.1222 [ChannelsImporter][checkEPG] Force EPG save on remote receiver...
< 34.2556> 17:51:19.1224 [ChannelsImporter][saveEPGonRemoteReceiver] URL: http://192.168.200.23/api/saveepg
< 34.3158> 17:51:19.1826 [ChannelsImporter][saveEPGonRemoteReceiver] ERROR: HTTP Error 401: Unauthorized
You did not respond to why you are not able to fetch the EPG.
@adsk
You did not respond to why you are not able to fetch the EPG.
I get the EPG on my device - it works fine. I don't understand why the log should post this message.
Where is epg been saved to ?
abu baniaz
28-01-23, 18:16
Where is epg been saved to ?
All EPG acquisition methods fetch EPG to RAM. It is only saved to epg cache on graceful restart/shut down or you select the save EPG option.
The epg error message occurs regardless of which interface is used and the epg works regardless of which interface is used.
We still seem to be no closer to working out why the ethernet interface on the box freezes the box in client mode but the wireless interface does not.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.