I mean, for the exchange which is the "fibre-head" exchange it needs 21CN WBC first?
From the two devices that I own from Billion, I believe 1492 bytes is the max.
He already uses 1500, 1492 is a PPPoE limit.
Assuming your PC is running Windows, change its MTU to 1500 with
TCP Optimizer. Tick "Modify All Network Adapters", tick "Optimal" at the bottom and click "Apply changes" & "OK", but say "No" to restart prompt, and close TCP Optimizer. Then, re-open TCP Optimizer, tick "Custom" at the bottom, in the "MTU" box enter "1500". I've also attached a picture of what the other settings should be, but a note about the "Disable Nagle's algorithm" section in the "Advanced Settings" tab - leave them on "default" (
explanation). I've disabled both Nagle algorithms for minimum latency (gaming), but it's not good for data transfer (streaming). The rest are ideal for you. After you're done click "Apply changes" and restart your PC for it to take effect.
To test if 1500 is working on your PC, open a "command prompt" and you should get similar results:
ping google.com -l 1472 -f
Pinging google.com [172.217.23.14] with 1472 bytes of data:
Reply from 172.217.23.14: bytes=64 (sent 1472) time=74ms TTL=51
Reply from 172.217.23.14: bytes=64 (sent 1472) time=73ms TTL=51
Reply from 172.217.23.14: bytes=64 (sent 1472) time=74ms TTL=51
Reply from 172.217.23.14: bytes=64 (sent 1472) time=74ms TTL=51
Ping statistics for 172.217.23.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 74ms, Average = 73ms
-------------------------------------------------------------
ping google.com -l 1473 -f
Pinging google.com [172.217.23.14] with 1473 bytes of data
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 172.217.23.14:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
About SRA, just keep it unticked.
give unticked a shot, and see whether you have more de-syncs (dropouts).It isn't supported on ADSL [just ADSL2], and it's always better to have it off when not supported. People had problems with it enabled in the router because of its router implementation, like not syncing or line problems.
When you get ADSL2 this year
, if you'll have line drops, you could try ticking it (there's a chance your exchange wouldn't support it though).
I hope you ticked Firewall in the ATM interface. Also if you want you can screenshot any or all the router pages and I'll say which settings to use.