Still have packet loss on my Samsung STB
 

I've been waiting for a firmware update to fix the packet loss for ages now, but nothing has happened :( This netstat -s was done just now.

TCP Statistics for IPv4

Active Opens = 8784
Passive Opens = 913
Failed Connection Attempts = 329
Reset Connections = 718
Current Connections = 21
Segments Received = 797056
Segments Sent = 742500
Segments Retransmitted = 29977

Re: Still have packet loss on my Samsung STB
 

have you run dan elwells bb speed test to see what that shows up :)

Re: Still have packet loss on my Samsung STB
 

Here are the results, but I don't see how it helps -- I know that I'm on a 1.5mbit connection, after all ;)

Also, the packet loss occurs still occurs when peer to peer applications are open (i.e. when my download and upload are both saturated -- although upload has to be past 15k/s to get significant loss). I've had a repull and everything, but it still has not yet been fixed.

Re: Still have packet loss on my Samsung STB
 

i asked because i was curious how much packet loss was involved ;) , nobody queried what service you were on ;) , nice to be nice when ppl try and help you ;)

Re: Still have packet loss on my Samsung STB
 

No no, I'm not trying to be nasty at all. The thing is that the packet loss varies in different operating conditions. (i.e. when upload and download are saturated).

On the netstat thing, I know someone who can keep eMule open all day and only get 100 segments retransmitted. On mine, it has creeped up every time I do it over a number of seconds, and when eMule olr whatever is open (it does it with any P2P application which saturates the connection).

Re: Still have packet loss on my Samsung STB
 

You shouldn't saturate the upstream or downstream, as it will (as you've found) affect your connection.

Have a look at this for a bit of info on P2P problems - http://homepage.ntlworld.com/robin.d...mtips/p2p.html

Re: Still have packet loss on my Samsung STB
 

It dosen't just affect my connection in terms of latency, it affects it in terms of packet loss, which I shouldn't be getting at all. Show me your netstat -s after a while of eMule being on full saturation. I guarantee that you won't get the same 'segments retransmitted' as me.

See http://homepage.ntlworld.com/robin.d.h.walker/cmtips/loss.html

Re: Still have packet loss on my Samsung STB
 

it's as simple as Matt D suggests - do not saturate either upstream or downstream.

Re: Still have packet loss on my Samsung STB
 

limit the upstream, and also lower the number of similtaneous connections- not sure if you can do this with emule.... never used it myself!

Re: Still have packet loss on my Samsung STB
 

Even if I limit my upload to 15k/s, I still get packet loss -- images sometimes do not load, etc. It is not a solution.

I know someone else who, if they match my operating environment, gets no packet loss whatsoever.

Re: Still have packet loss on my Samsung STB
 

Ultimately, the only way a bandwidth cap can be enforced is by dropping packets. The CMTS/UBR will at first try to enforce the cap by delaying packets in a buffer (or leaky bucket), and hoping that the flow control properties of TCP will cause the rate of arrival of data to slow down. But if the packets continue to flood in, the leaky bucket will overflow and the overflowed packets will be lost. Maybe (or maybe not) this is what is happening to you.

Much depends on your TCP Receive Window, or RWIN, setting. If you have an over-large RWIN setting, it will eventually be impossible for the CMTS/UBR to delay/hold complete TCP Windows (for each of your incoming TCP sessions) in its leaky bucket, and you will lose incoming data. I suggest you run the Tweak Test at http://www.broadbandreports.com/tweaks which will report your active RWIN setting.

Another potent cause of packet loss could be an ethernet duplex mismatch between your STB and the device connected to it. What are the ethernet speed and uplex settings in force there?

Re: Still have packet loss on my Samsung STB
 

My RWIN is currently at default, and I've tried all duplex settings. BillC told me to use 10 half duplex until the problem was fixed, but that was 3 months ago :(

Perhaps the answer (in the short term) is to use a ridiculously small RWIN value so any packets which are not recieved can be resent quickly.

I've also changed the network adapter from the one on my motherboard (VIA Rhine) to a PCI one (Realtek), but hasn't affected much.

Re: Still have packet loss on my Samsung STB
 

If at all possible try and do yourself a favour and get a SACM. The Samsung is jack, I had similar problems and couldn't put up with it. The reliability of my connection is now superb (I've got the 200 SACM version), I can't believe I put up with the STB for so long (Pace didn't have the same problems as the Samsung but it did crash fairly frequently).

Re: Still have packet loss on my Samsung STB
 

I tried to get an SACM out of them but they wouldnt give me one....
They just kept redirectin me to another department. Would it be possible to buy my own sacm off like ebay and put it in myself? Or wud i have to tell ntl i was doing that?

Re: Still have packet loss on my Samsung STB
 

Nope, the only modems NTL allows on it's network are those it supplies.