View Single Post
Old 11-09-2008, 23:50   #1
Ignitionnet
Inactive
 
Join Date: Jun 2008
Location: Leeds, West Yorkshire
Age: 47
Posts: 13,995
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Bittorrent On VM

I'm curious if anyone else is seeing some unexplained behaviour while using Bittorrent on Virgin Media.

I have done the usual tricks and am permitted 50 half-open connections simultaneously so that is NOT the issue in question.

I have checked my router and its' NAT table isn't even close to full.

I have checked the connection to ensure I'm not seeing any issues with bandwidth utilisation. The connection is going no higher than 60% upstream utilisation and isn't even close on downstream.

Pings show the odd spike but nothing to write home about:

Pinging www.bbc.net.uk [212.58.251.195] with 32 bytes of data:

Reply from 212.58.251.195: bytes=32 time=16ms TTL=118
Reply from 212.58.251.195: bytes=32 time=13ms TTL=118
Reply from 212.58.251.195: bytes=32 time=17ms TTL=118
Reply from 212.58.251.195: bytes=32 time=14ms TTL=118

So why oh why is my browsing utterly mashed to the point of being unusable?

Something to do with these at a guess:

Ah Yes... The columns are:

Frame Number - Time Since Capture Start - Source - Destination - Protocol - Source Port > Destination Port - TCP Flags - Summary

Quote:
1282 13.113980 192.168.100.2 87.106.129.133 TCP udpradio > http [SYN] Seq=0 Win=16384 Len=0 MSS=1460
1300 13.243386 87.106.129.133 192.168.100.2 TCP http > udpradio [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1380
1301 13.243417 192.168.100.2 87.106.129.133 TCP udpradio > http [ACK] Seq=1 Ack=1 Win=16560 Len=0
1302 13.243611 192.168.100.2 87.106.129.133 HTTP GET /board/newthread.php?do=newthread&f=12 HTTP/1.1
1661 16.236539 192.168.100.2 87.106.129.133 HTTP [TCP Retransmission] GET /board/newthread.php?do=newthread&f=12 HTTP/1.1
2420 22.171080 192.168.100.2 87.106.129.133 HTTP [TCP Retransmission] GET /board/newthread.php?do=newthread&f=12 HTTP/1.1
2431 22.336216 87.106.129.133 192.168.100.2 TCP [TCP Previous segment lost] http > udpradio [ACK] Seq=2761 Ack=843 Win=6736 Len=0 SLE=1 SRE=843

6337 50.572019 192.168.100.2 87.106.129.133 TCP udpradio > http [FIN, ACK] Seq=843 Ack=1 Win=16560 Len=0
6356 50.747083 87.106.129.133 192.168.100.2 TCP http > udpradio [ACK] Seq=2761 Ack=844 Win=6736 Len=0
For the curious this also proves that I don't have a problem with half open connections - the connection was open I just couldn't do anything with it for whatever reason

It also eliminates the possiblity that it's my router - the SYN, SYN-ACK was already done and the connection had been set up in my router's NAT table already.

The first bit was fine, the next bit was loss central then my machine gave up and just sent the FIN to CF.

Is this normal behaviour while using a not particularly challenging amount of Torrent bandwidth? More to the point why?
Ignitionnet is offline   Reply With Quote