Apr 27 2008, 07:00 PM
QUOTE(spanker @ Apr 27 2008, 05:06 PM)
So I was really fed up of the lies thrown at me by Streamyx call center (VADS), but the last straw came when TM tech support themselves lied to me about blocking my traffic, so I have no choice but to get proof. This is how I did it:
1) Download Ethereal Network Analyzer
2) Install Ethereal along with the WinPcap driver that comes with it.
2a) Alternatively you can download the latest version of WinPcap instead of using the one packaged in Ethereal
3) Run Ethereal
4) Click to configure snooping
5) Configure the interface, which port you want to monitor, protocols, yada yada
6) After you've started capturing, remember to stop.
7) This is roughly what things will look like after you are done. If you are sniffing your BT traffic Look for the RST packet (as described in this thread.
What it actually means is that the client (you being the host) has acknowledged your request to reset the connection. However, if you check your entire TCP stream you will find that you have NOT sent out a RST packet. Meaning Streamyx screwed you.
Alternatively, if you are having problem with non-BT connection (perhaps you are downloading ahems from IRC), like how I am facing very slow traffic with my paid NNTP news service, you see this:
This proves that somehow part of your TCP sequence (usually the binary part) has been dropped by someone, so your entire sequence cannot be used by the application and has to be requested again. In short, you're still screwed by streamyx.
When I used a friend's streamyx account to log in(this dude has much lower traffic than I do), all these errors miraculously dissappeared and I am getting full speed.
I have decided to documented my findings because 2 days back after I made a complaint to Streamyx to escalate my case to level 2, someone from TM Technical Support said "international traffic is not our problem", and decided to close my case. He even challenged me to go to the SS13 TM office to prove my case, which I will do tomorrow, along with my documentations. I made another follow-up call to Streamyx today to inform them my findings, and viola, miraculously all those errors dissappeared.
Anyway, I'm going to visit TM tomorrow, and if it happens again, I'm going to complain to MCMC.
Hope it helps you people.
Hope they speechless when you showing this to them.......... 1) Download Ethereal Network Analyzer
2) Install Ethereal along with the WinPcap driver that comes with it.
2a) Alternatively you can download the latest version of WinPcap instead of using the one packaged in Ethereal
3) Run Ethereal
4) Click to configure snooping
5) Configure the interface, which port you want to monitor, protocols, yada yada
6) After you've started capturing, remember to stop.
7) This is roughly what things will look like after you are done. If you are sniffing your BT traffic Look for the RST packet (as described in this thread.
What it actually means is that the client (you being the host) has acknowledged your request to reset the connection. However, if you check your entire TCP stream you will find that you have NOT sent out a RST packet. Meaning Streamyx screwed you.
Alternatively, if you are having problem with non-BT connection (perhaps you are downloading ahems from IRC), like how I am facing very slow traffic with my paid NNTP news service, you see this:
This proves that somehow part of your TCP sequence (usually the binary part) has been dropped by someone, so your entire sequence cannot be used by the application and has to be requested again. In short, you're still screwed by streamyx.
When I used a friend's streamyx account to log in(this dude has much lower traffic than I do), all these errors miraculously dissappeared and I am getting full speed.
I have decided to documented my findings because 2 days back after I made a complaint to Streamyx to escalate my case to level 2, someone from TM Technical Support said "international traffic is not our problem", and decided to close my case. He even challenged me to go to the SS13 TM office to prove my case, which I will do tomorrow, along with my documentations. I made another follow-up call to Streamyx today to inform them my findings, and viola, miraculously all those errors dissappeared.
Anyway, I'm going to visit TM tomorrow, and if it happens again, I'm going to complain to MCMC.
Hope it helps you people.
Because I'm very sure those Nut didn't study deeply about the networking thing
The only ppl will understand is the person who control the dslam..............
But tm point ppl
they only a normal stuff
Pray they will understand what you're trying to said so
Quote
0.0165sec
0.47
6 queries
GZIP Disabled