Differences

This shows you the differences between two versions of the page.

--- troubleshooting:network_packet_loss [2019/06/16 12:29]
neds
+++ troubleshooting:network_packet_loss [2019/10/22 18:18]
jasonl Add Mac/Linux instructions
@@ Line 3: / Line 3: @@
 ===== Testing for packet loss =====
-==== Low level test for network packet loss =====
+<WRAP indent>
+==== Low level test for network packet loss ====
+<WRAP indent>
 From a cmd prompt run: <code>
@@ Line 15: / Line 18: @@
 You should see a series of dots. "n" indicates network packet loss. "t" indicates a reception error. "s" is informational.
-==== Low level test for network packet loss - Legacy devices =====
+</WRAP>
+==== Low level test for network packet loss - Mac/Linux ====
+<WRAP indent>
+From Terminal (Mac) or a shell on Linux, run: <code>
+hdhomerun_config FFFFFFFF set /tuner0/vchannel <channel number>
+hdhomerun_config FFFFFFFF save /tuner0 null</code>
+Replace "<channel number>" with one of your HD channels. For HDHomeRun PRIME, make sure that it is a non-DRM channel.
+If you have more than one HDHomeRun unit then replace "FFFFFFFF" with the device ID of the desired unit.
+You should see a series of dots. "n" indicates network packet loss. "t" indicates a reception error. "s" is informational.
+</WRAP>
+==== Low level test for network packet loss - Legacy devices ====
+<WRAP indent>
 ) Run HDHomeRun Setup and go into the channel editor. Choose a physical channel number (for example CH45). This is the number before the - in the Tune column.
@@ Line 28: / Line 49: @@
 You should see a series of dots. "n" indicates network packet loss. "t" indicates a reception error. "s" is informational.
+</WRAP>
+</WRAP>
 ===== Common issues and solutions =====
+<WRAP indent>
 ==== Network loss due to wireless ====
+<WRAP indent>
 We recommend using a wired network for streaming high-definition video.
@@ Line 45: / Line 72: @@
 If the router permits limiting the network speed to something below its theoretical max, try utilizing that. For example, eather than the typical 108Mb/s max for 802.11n, try limiting it to 72 or 54Mb/s operation. While in theory this will limit the maximum performance of the network, in practice the network will operate more reliably at the lower speed, minimizing speed fluctuations that can cause packet loss.
+</WRAP>
 ==== Network loss due to Windows network throttling ====
+<WRAP indent>
 http://support.microsoft.com/kb/948066
@@ Line 56: / Line 87: @@
 You will need to reboot after making this change.
+</WRAP>
 ==== Network loss due to the PC network card ====
+<WRAP indent>
   - <wrapper>Open network settings\\
 (Win7/8) Go into Control Panel, View network status and tasks, Change adapter settings\\
@@ Line 67: / Line 101: @@
     - Intel based interface: Click Configure and switch to the Advanced tab. Test with alternative Interrupt Mitigation settings.
     - All interfaces: Click Configure are switch to the Advanced tab. Increase the Receive Buffer size (if this option is present). Test with the Interrupt Mitigation/Moderation setting both On and Off (if this option is present). If the issues persist after adjusting these settings, try disabling all options referencing "offload".
+</WRAP>
 ==== Network loss due to a 3rd party software firewall ====
+<WRAP indent>
 We have seen instances where some 3rd party firewall drivers fail to keep up with streaming HD video over RTP.
@@ Line 74: / Line 112: @@
 If uninstalling the 3rd party firewall fixes the problem then 1) Try upgrading to the latest version, or 2) contact the firewall vendor, or 3) consider using an alternative firewall such as Windows Firewall.
+</WRAP>
 ==== Network loss in macOS ====
+<WRAP indent>
 Create a file called sysctl.conf in /etc (this must be done as root or using sudo) and add the following lines:<code>kern.ipc.maxsockbuf=2097152
 net.inet.tcp.sendspace=1048576
@@ Line 83: / Line 125: @@
 Save the file and then reboot the computer.
+</WRAP>
+</WRAP>
+{{tag>troubleshooting}}

troubleshooting