Status
Not open for further replies.
ok.

Code:
outlawstar@outlawstar:~$ ping -c 4 -M do -s 1473 155.133.238.163
PING 155.133.238.163 (155.133.238.163) 1473(1501) bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 155.133.238.163 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3056ms

outlawstar@outlawstar:~$ ping -c 4 -M do -s 1472 155.133.238.163
PING 155.133.238.163 (155.133.238.163) 1472(1500) bytes of data.
1480 bytes from 155.133.238.163: icmp_seq=1 ttl=56 time=21.4 ms
1480 bytes from 155.133.238.163: icmp_seq=2 ttl=56 time=21.4 ms
1480 bytes from 155.133.238.163: icmp_seq=3 ttl=56 time=21.4 ms
1480 bytes from 155.133.238.163: icmp_seq=4 ttl=56 time=21.4 ms

--- 155.133.238.163 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 21.412/21.449/21.491/0.150 ms
So 1472 works, 1473 dont, which is expected, because 1473 needs an MTU of 1501. So its not MTU that is the issue then.

Well I can pass a 1500 frame from the Vumatel Edge Router to 155.133.238.163 as well as to Loppas' public IP. So that's interesting. What happens when you try ping the gateway on the Vumatel network?
 
Well I can pass a 1500 frame from the Vumatel Edge Router to 155.133.238.163 as well as to Loppas' public IP. So that's interesting. What happens when you try ping the gateway on the Vumatel network?
Parameter could be the layer 7 payload length, not the lower level ones. Or something specific to in game traffic, not necessarily TCP related.
 
You are 100% correct. Craighall park

Can you download and install iperf and run the following command from a cabled PC:

iperf3.exe -R -u -b 40M -p 17001 -c iperf.cisp.co.za
iperf3.exe -R -u -b 40M -p 17001 -c lnms.cisp.co.za

where the 40M is your line speed IE 20M 50M 100M etc
 
Well I can pass a 1500 frame from the Vumatel Edge Router to 155.133.238.163 as well as to Loppas' public IP. So that's interesting. What happens when you try ping the gateway on the Vumatel network?

The size 1472 is 1500 frame if I read the ping command output correct.

But its the same to the vumatel router:
Code:
outlawstar@outlawstar:~$ ping -c 4 -M do -s 1473 155.93.243.1
PING 155.93.243.1 (155.93.243.1) 1473[B](1501)[/B] bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 155.93.243.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3048ms

outlawstar@outlawstar:~$ ping -c 4 -M do -s 1472 155.93.243.1
PING 155.93.243.1 (155.93.243.1) 1472[B](1500)[/B] bytes of data.
1480 bytes from 155.93.243.1: icmp_seq=1 ttl=254 time=1.63 ms
1480 bytes from 155.93.243.1: icmp_seq=2 ttl=254 time=1.72 ms
1480 bytes from 155.93.243.1: icmp_seq=3 ttl=254 time=2.46 ms
1480 bytes from 155.93.243.1: icmp_seq=4 ttl=254 time=45.9 ms

--- 155.93.243.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 1.634/12.948/45.971/19.068 ms
 
The size 1472 is 1500 frame if I read the ping command output correct.

But its the same to the vumatel router:
Code:
outlawstar@outlawstar:~$ ping -c 4 -M do -s 1473 155.93.243.1
PING 155.93.243.1 (155.93.243.1) 1473[B](1501)[/B] bytes of data.
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500

--- 155.93.243.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3048ms

outlawstar@outlawstar:~$ ping -c 4 -M do -s 1472 155.93.243.1
PING 155.93.243.1 (155.93.243.1) 1472[B](1500)[/B] bytes of data.
1480 bytes from 155.93.243.1: icmp_seq=1 ttl=254 time=1.63 ms
1480 bytes from 155.93.243.1: icmp_seq=2 ttl=254 time=1.72 ms
1480 bytes from 155.93.243.1: icmp_seq=3 ttl=254 time=2.46 ms
1480 bytes from 155.93.243.1: icmp_seq=4 ttl=254 time=45.9 ms

--- 155.93.243.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 1.634/12.948/45.971/19.068 ms

Yeah so no issue on the frame transport.
 
International is very patchy indeed, getting major lag spikes in Elder Scrolls Online now with jumps to 800ms which isn't normal, Speedtest for international is shocking, I am guessing same issue as last night as it appears to be affecting the same clients.
 
International is very patchy indeed, getting major lag spikes in Elder Scrolls Online now with jumps to 800ms which isn't normal, Speedtest for international is shocking, I am guessing same issue as last night as it appears to be affecting the same clients.

Not the same issue as last night, please run the same Iperf test in my previous post? And send me the results, then do the same tomorrow morning if you can.
 
PBCool, how do I get the results to you, won't let me PM as it has too many lines/chars
 
International streaming from 3 different "iptv" providers shocking again tonight
Vuma Aerial Morningside Sandton
on 200/200 but international is laggy , thought it may be my dns redirector provider changed to 1.1.1.1 as well as Cisp default with no improvement
 
Yes last night was very bad had to eventually use 4G tried fortnite up and down went to Call of Duty and that was even worse have no idea how they going to solve this issue but it's super annoying.

2 bar in Call of Duty that means 200ms to 500ms (widgetdamage)

9a405eea02c274150c54bbcb1538b2c8.jpg

Yeah same for me tonight, much worse than it has been. Cant really play games. Seems like the openserve issue is back.
 
Yeah same for me tonight, much worse than it has been. Cant really play games. Seems like the openserve issue is back.

Yup, I can relate, getting 6 meg international now this evening, shocking....
 
Seems like congestion on the AEx network, so Vumatel aerial, Evotel etc.
 
Yeah same for me tonight, much worse than it has been. Cant really play games. Seems like the openserve issue is back.
We're aware of Openserve reports, we have logged it with OS again.
 
Can you download and install iperf and run the following command from a cabled PC:

iperf3.exe -R -u -b 50M -p 17001 -c iperf.cisp.co.za
iperf3.exe -R -u -b 50M -p 17001 -c lnms.cisp.co.za

where the 40M is your line speed IE 20M 50M 100M etc

I am unable to send them as I am getting a lot of packet out of order issues which is causing the messages to be too long, but here is the outcome:

lnms.cisp
Code:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  60.3 MBytes  50.6 Mbits/sec  2.042 ms  2859/7710 (37%)
[  4] Sent 7710 datagrams
[SUM]  0.0-10.0 sec  19 datagrams received out-of-order

iperf.cisp
Code:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  87.4 MBytes  73.3 Mbits/sec  1.643 ms  6772/11192 (61%)
[  4] Sent 11192 datagrams
[SUM]  0.0-10.0 sec  69 datagrams received out-of-order
 
International streaming from 3 different "iptv" providers shocking again tonight
Vuma Aerial Morningside Sandton
on 200/200 but international is laggy , thought it may be my dns redirector provider changed to 1.1.1.1 as well as Cisp default with no improvement

Same here on 200/20 Vumatel trenched Weltevreden Park, its a second time this week, terrible internet, feel like the ADSL days are back...oh wait even ADSL was faster than 200mbps fibre with Vumatel and Cool Ideas... this is becoming "the usual" now and always some "Congestion stories".

http://www.speedtest.net/result/7539493611.png

I think PBCool, when time comes for me to pay the R 1400 for internet I should come up with a story "my wallet is congested and I cannot pay you right now" lets see how you will react, will you accept that or not.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X