@tvdnagel - I followed your instructions, and it is working for my TX-NR717, also.
The receiver properly initialized on the first power up, passed the network test, and I’ve been streaming for about 45 minutes with no problems. Looks like a winner. Thanks for sharing the detailed procedure. I had previously been apprehensive about creating the firewall rules in the Vera, and had tried to block those ports in the router, to no avail. ;D
I blocked those ports in dd-wrt in my router and it worked great. Seems the firewall function isn’t available in Vera2.
[quote=“tvdnagel, post:60, topic:173509”]What worked for me (VeraLite & Onkyo TX-NR616) was disabling uPNP traffic coming from my VeraLite:
Go to http://your vera ip address/cgi-bin/webif/info.sh and login with your root password.
Go to network → firewall.
Click “add” in the rules section on the bottom of the page.
Source Zone = LAN
Protocol = UDP
Destination Port = 1900
Action = Reject
Click “Save and Apply”
Click “add” in the rules section on the bottom of the page.
Source Zone = LAN
Protocol = TCP
Destination Port = 5000
Action = Reject
Click “Save and Apply”
Done![/quote]
thank you!
Man, am I happy that I found this workaround! I just bought an TX-NR414 and already returned one due to this problem. But since the second unit had the same problem I started to dig deeper.
On the internet I found this topic: Onkyo Network problems - ISSUE IDENTIFIED. This pointed to the UPnP problems in the Onkyo network stack.
So removing UPnP related devices from the network showed the VeraLite to be the cause, as many have seen. Happy that blocking the ports from the Vera works for now. Otherwise I would have returned the Onkyo to the shop again. I will still raise a support ticket with Onkyo, as they really need to fix this.
@nlrb Yes, do create a support ticket. They already have some on the subject, but the more they get reminded about the customer impact from this problem , the better. They have promised to investigate the problem and report back promptly on my ticket and in a thread in their own forum, but I’ve been waiting for a couple of months for them to show any results, and others have waited far longer. At this point, I’m not confident they really are taking it seriously, or doing anything about it, but it doesn’t hurt to try.
Sent from my Transformer TF101 using Tapatalk 4 Beta
Ticket submitted. Response from Onkyo:
Many thanks for pointing this out to us - I'm afraid that I can't tell you when it will be implemented into a new firmware but I have passed it up the chain so that the development team can see it.
[quote=“nlrb, post:66, topic:173509”]Ticket submitted. Response from Onkyo:
Many thanks for pointing this out to us - I'm afraid that I can't tell you when it will be implemented into a new firmware but I have passed it up the chain so that the development team can see it.[/quote]
Interesting that they react to every report of this same issue as if it is new and surprising to them, despite prior reports and much discussion of it in great detail in their own forum. The problem seems to straightforward to us customers, and it would seem to be easy to replicate and resolve. I’m not optimistic they will really take the time and trouble to fix it, but it sure doesn’t hurt to report it. In the meantime, at least we have a workaround.
[quote=“tvdnagel, post:60, topic:173509”]What worked for me (VeraLite & Onkyo TX-NR616) was disabling uPNP traffic coming from my VeraLite:
Go to http://your vera ip address/cgi-bin/webif/info.sh and login with your root password.
Go to network → firewall.
Click “add” in the rules section on the bottom of the page.
Source Zone = LAN
Protocol = UDP
Destination Port = 1900
Action = Reject
Click “Save and Apply”
Click “add” in the rules section on the bottom of the page.
Source Zone = LAN
Protocol = TCP
Destination Port = 5000
Action = Reject
Click “Save and Apply”
Done![/quote]
The above method didn’t work for me, but got me in the right direction. Thanks for this thread! I have a Onky TX-NR616 and had the same trouble. The DNLA player from Onkyo will not work (or very shortly) when my Vera 3 is active. What I like about this firewall method is that I don’t have to use a separate subnet. I got things working by blocking ports 9999-65000.
There are two ways to do this. The first is described by tvdnagel above and uses the OpenWrt interface. Another method can be found here: http://forum.micasaverde.com/index.php/topic,9895.0.html. Log in via a telnet client (I used Putty) and use the password on the bottom of your device, and give the following commands:
uci add firewall rule uci set firewall.@rule[-1].src=wan uci set firewall.@rule[-1].target=REJECT uci set firewall.@rule[-1].proto=tcp+udp uci set firewall.@rule[-1].dest_port=9999-65000 uci set firewall.@rule[-1].src_port=9999-65000 uci commit firewall /etc/init.d/firewall restart
After that I restarted (hard reboot) all my network components. Now the Onkyo seems works like it should. The Vera 3 blocks a wide range of ports now. So it probably can be tuned a bit more. Maybe WireShark can help us finding the right port.
PS look at your configuration. On my Vera 3 I use the wan port, therefore I need to block things on the wan site. If you use your lan port, you should block traffic on that port.
I hope Onkyo fixes this bug, probably all their network capable receivers are effected by this bug.
Onkyo TX-NR626 working fine with Wired and Wireless on my network with Vera3. No special sub-netting,
router or Vera3 system configuration.
http://forum.micasaverde.com/index.php/topic,15302.0.html
MWP
Sorry to semi hijack this post but it’s very similar to an issue I am experiencing with my Vera 3. I am running Verizon Fios at home with Cisco set top boxes. I bought my Vera 3 two monts after having verizon in my house. My set top boxes were working great, no problems. I install the Vera 3 and everything was still working great. One day over the summer last year we lost power and everything reset. The Internet router came back up, the Vera 3 came back up but every set top box in my house was on an endless reboot cycle. So I called Verizon out to service them, 3 techs later and replacing everything inside/outside of my house they gave up. Eventually out of pure luck we unplugged the Vera 3 and wa-la all the set top boxes booted up no problem. I have been dealing with this for around a year now and haven’t been able to find anything similar other than this post. I was wondering if any of you guys have seen this?
No, I haven’t experienced this issue. If you power cycle the Vera 3, does it continue to cause the set top boxes to go back into endless reboots? Are you still able to access and use the Vera 3 normally? If it does repeatedly cause the problem,and you can’t resolve it with resetting and reinstalling the Vera, I would consider replacing it.
The set top boxes will come on as long as they catch the Vera 3 powered off or during it’s boot up cycle. If the Vera 3 is on and plugged into the network or connected via wireless it will cause the set top boxes to go into a reboot cycle. I can always access the Vera 3 with no problems.
Since the symptoms are so easily repeatable, short of a replacement, you might want to submit a Support Ticket. They can remote access the unit, diagnose and hopefully resolve it for you.
Sent from my Transformer TF101 using Tapatalk 4 Beta
I am new to these forums and still somewhat new to the MiCasa as well. However, I want to chime in on this discussion with my comments and feedback.
I’ll start with the summary: Both Onkyo and MiCasa have shame on them for shoddy software.
My story: I have several Onkyo AVR’s. Two of them are networked. A 2011 model TX-NR3009 and a 2013 model TX-NR626. I added the MiCasa as part of my plan to move my Home Theater to a full IP controlled solution (no more quirky IR). I also have plans for whole house lighting/automation as well. When I added the VeraLite to my system I did not notice any problems with the 3009 at first, because I wasn’t using the IP remote functions and netstreaming much. As soon as I started in with Roomie and then iRule I noticed problems. Then I couldn’t upgrade FW on the Onkyo, so I assume the 3009 was bad. In to the repair shop it went. Meanwhile, I took delivery of the NR626 and plugged it into the very same set of wires (as a stopgap) in my HT. Things worked, which verified my suspicion of the NR3009 (OR SO I THOUGHT!).
Once I get the NR3009 back it failed right away, causing consternation with the repair shop. Therefore the NR3009 went back in to the shop, although they didn’t do anything the 2nd time because it worked for them!
More debugging and then careful iterations of adding devices narrowed it down to the VeraLite as the “problem.” Some Googling later and I find many many documented cases of problems with the Onkyo FW and then for sure problems with Onkyo + Vera. I read this thread in particular and say thanks to the great posters. I happen to know quite a bit about software and networking as that is my field of study and my full time job for many years.
Onkyo summary:
Naughty behaviors at many points. You management of uPNP traffic is poor. Your net streaming functions get hung in the worst kind of ways with NO indications to the users except complete in-operation. It has been reported repeatedly yet you seem uninterested in fixing FW on recently purchased units that cost $k’s of dollars. There is no way to reset the networking without a full A/C power cycle. Naughty, naughty! This thread explains some of the problems: [url=http://onkyoproductsupport.forumotion.com/t298p30-tx-nr709-network-initializing-issue]http://onkyoproductsupport.forumotion.com/t298p30-tx-nr709-network-initializing-issue[/url]
MiCasa summary on the VeraLite:
The VeraLite, unlike the big brother Vera3, is only an automation controller. A powerful IP<->Zwave interface. It makes perfect sense that MiCasa would use the same software foundation on the Lite as the Vera3. However, MiCasa is also very much at fault here. They left all sorts of router functionality open on the LAN port of a device not intended to function as a router on the network. Then they hid all of the panels to get to those functions thereby allowing you to stick a subversive device onto your LAN!!! If you are making a device that can function as a router but should not function as a router then you sure better turn that stuff off!!!
This post in this thread cleared up my problems:
[url=http://forum.micasaverde.com/index.php/topic,12773.msg113981.html#msg113981]http://forum.micasaverde.com/index.php/topic,12773.msg113981.html#msg113981[/url]
It might not work for everyone, but it should help immensely if you are running only a VeraLite. The fact that it works proves (and I can snatch the packet sniffs to prove it) that the VeraLite is responding to uPNP port requests.
I can only hope that others find this thread and find it useful before wasting time chasing these subtle network issues. The other option is that MiCasa and Onkyo both suffer product returns and bad reputations as deserved for shoddy software.
P.S. Yes, I am opening cases with both companies to offer them a chance to fix it.
if u happen to have a asus n** series router … turn of vpn server in it and streaming is happy again.
New firmware released by Onkyo seems to have fixed the network problem with my 515. I’m happy!
-GT
turning off the autodetect upnp devices in vera also solves it.
That did not work for me. The new firmware does which is nice so I can use DLNA now since my Onkyo was behind another router.
The update is working for my NR717 Onkyo. That was a long time coming, but I’m glad they didn’t ignore the issue.
i’d go for a Anthem or Yamaha amp… so much better sound.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules