TX/RX packets

Started by Tacitus, Apr 05, 2009, 11:16:11

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Tacitus

Since the naming conventions on some modems seems to vary, could someone just clarify/confirm that TX are transmitted packets and that RX are those which are re-sent? 

Thus, stats which report the RX packets as being significantly higher (+20% or so) than the TX packets, is showing a bad line even though downstream SNR is reported as 15dB.

Rik

You're right on names, Tac, but I'm not sure what you mean in your last sentence.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

I thought Rx simply refers to packets received, not necessarily re-sent.

Tacitus

Quote from: Sebby on Apr 05, 2009, 11:23:37
I thought Rx simply refers to packets received, not necessarily re-sent.

Your confusion chimes with mine Seb :)  I thought TX was transmitted packets (= sent).  RX was re-sent packets which would be a reflection of errors.  I suppose though it could simply be received packets, in which case the figures are pretty meaningless for trying to get some idea of the line quality. 

Rik

Does the router list FEC errors, Tac?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Apr 05, 2009, 11:34:48
Does the router list FEC errors, Tac?

No - just TX/RX.  I suspect a lot of stuff is done via the cli but i haven't a manual at present.

Rik

Is this your connection, Tac? IDNet would be able to tell you the error count, so any ISP should be able to do so.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Apr 05, 2009, 12:47:26
Is this your connection, Tac? IDNet would be able to tell you the error count, so any ISP should be able to do so.
Yes it is mine. I have a Zyxel running at the moment as it has a VPN facility but seems to be getting slower & slower.  Best is probably put the 2-Wire back as that has a good reporting system. Tryingto get sense out of the Demon script monkeys is a bit of a lottery :-)

Rik

:(

It's frustrating, because I know that Demon have access to the information, but a change of router might be your best bet right now. (Or you could try some long term pinging and look for packet loss...)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Apr 05, 2009, 15:29:45
:(
Or you could try some long term pinging and look for packet loss...

Brilliant idea Rik!  Now I know why I hang out here.   :)

Average over 100 pings to 212.69.36.10 is 33.114ms with zero packet loss.  No idea what's going on, but SNR at the moment is 12dB; RX = 14785  TX = 17387.  Looks as though Seb was right - it's simply sent and received packets.  However if there's zero packet loss I can't see why the profile should be heading downhill.  OK it might be noisy, but it doesn't seem to result in packet loss so what gives?

I'll see what it's like in the morning.  If there's no improvement - given the weekend it could be work going on either by BT or at Demon - I'll give them a ring. 


Sebby

Packet loss and speed are not directly related, afaik. If your speed is suffering, it's either that your sync has dropped, or some low sync events have caused the profile to drop.

Tacitus

Quote from: Sebby on Apr 05, 2009, 23:15:26
Packet loss and speed are not directly related, afaik. If your speed is suffering, it's either that your sync has dropped, or some low sync events have caused the profile to drop.

I was thinking more of packet loss and noise being related.  Greater packet loss might suggest a noisier line, although an SNR of 12dB points to the opposite.  The wonders of broadband  ::)

talos

Not sure if this clarifies, but in my experience TX meant transmit or send, RX meant receive or received  :dunno:



Rik

Quote from: Tacitus on Apr 06, 2009, 07:52:43
I was thinking more of packet loss and noise being related.  Greater packet loss might suggest a noisier line, although an SNR of 12dB points to the opposite.  The wonders of broadband  ::)

It might, Tac, but often the noise merely (!!) affects the sync speed.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Its noise bursts that are doing it.  Around noon the SNR dropped to 5dB and then climbed up to 7dB for a while before returning to its more normal daytime 10/11dB. 

Since it seems to have settled without any more disconnects I'll leave it for a while and see if it recovers.  If this was iDNet, or for that matter Zen, I'd give them a ring, talk it through and see if they could identify the cause. Intermittent noise bursts are difficult to pin down though, so there's probably not a lot that can be done short of getting BT/OR to move the line.  For an appropriate charge of course.

Rik

You left out massive, Tac. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

LesD

Regards,

Les.


Rik

To the point, aren't they, Les. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Apr 06, 2009, 15:33:07
To the point, aren't they, Les. ;)

Exactly!  Thanks Les that settles it.   :)

Tacitus

Quote from: Rik on Apr 06, 2009, 15:08:33
You left out massive, Tac. ;D

Running way off topic of course but....   

Surprisingly iDNet are quoting £108 for installing a new phone line which compares favourably to the £180 or so people have quoted as a BT call out charge if they decide nothing is wrong.  No guarantees the new line would prove any better of course, but I suspect problems would come when BT decided to charge for cancelling the old line and transferring the existing phone number to the iDNet line.

Rik

If you're not in contract, Tac, there's no charge for cancelling. Not sure about transferring the number, though.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Tacitus

Quote from: Rik on Apr 06, 2009, 15:47:20
If you're not in contract, Tac, there's no charge for cancelling. Not sure about transferring the number, though.

Interesting though as I imagine that since iDNet as an ISP have access to the same diagnostic tools as BT/OR, they would also, as a phone provider, have similar access to BT's diagnostic tools for phone only lines. 

Rik

I think the phone side is more a billing exercise, but you can certainly go through them for CS.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.