Web Squad ISP

Status
Not open for further replies.
... I see you removed the original post... still wanna respond though...

That 20MB line you reference is actually 20Mb... notice the big and small b. data is transferred at Megabit, data is stored on disk as MegaByte.

that 20Mb line, that would translate to about 2 MB, at theoretical best, so if you getting 1.5Mb, you doing well.

Even though you've fixed your problem with a 6TB drive, I'd propose still sync'ing your data to a cloud provider. I've had a couple of friends with a nice NAS setup, jsut for thieves to clear the house out, with NAS and then sit with no media/photo's docs etc... My TrueNAS is configured to sync a directory sub structure to a 2TB Google Drive (R150/month).

G

Question for all,

I need to back up some data from my NAS, as I need to replace a few drives and potentially recreate the ZFS Pool, I have a Hertzer server in DE, an Oracle Cloud Server in JHB and using Wireguard as a hub and spoke. All traffic goes to JHB then to DE.

Why is uploading so slow?

Getting 1.50 Mb/s out of a potential 20 MB/s? (range of 1 MB/s to around 3.3 MB/s)
Can anyone recommend any optimization?

Ps. I'm finding that I get more consistent speeds going out to Oracle in JHB, then to Germany, than connecting directly?

Thoughts and considerations appreciated, I really don't want to rent an R900 server again next month :)
Thanks for taking the time to respond.

However, I've got a 1000/200 line with WS, so I'd expect to see at least 150 Megabits a second, instead of the 20 Megabits I'm getting now...

Also realized I didn't mention that I have a gigabit line.
 
Thanks for taking the time to respond.

However, I've got a 1000/200 line with WS, so I'd expect to see at least 150 Megabits a second, instead of the 20 Megabits I'm getting now...

Also realized I didn't mention that I have a gigabit line.
Have you tried enabling TCP BBR on your host server (I missed your original post, so I'm not sure if this is available to you). We enabled BBR on Digital Ocean's servers in the UK and saw a 200-300% improvement in throughput.
 
Have you tried enabling TCP BBR on your host server (I missed your original post, so I'm not sure if this is available to you). We enabled BBR on Digital Ocean's servers in the UK and saw a 200-300% improvement in throughput.
I will have to try this,
An alternative option (since I'm still in the Oracle Cloud trial) I managed to upload 1.5 Terabytes to their object storage :)

Turns out for best performance you got to have multiple threads, when using the Wireguard solution I used it was limited by the one connection topping out at 30 Mbps

1649069203467.png

So, thanks for the rad upload I guess :giggle:

1649069254725.png

PS. At some stage I'm going to have to download all this again
 
Still offline here (on Openserve in Durban).
First lost connectivity to JHB/overseas at 14:13, now once I restarted my router the PPPoE doesn’t authenticate at all.
 
@websquadza any updates on the KZN outage? Any plans to add more redundance to the region as this seams to be happening more and more lately? :(
Still offline here (on Openserve in Durban).
First lost connectivity to JHB/overseas at 14:13, now once I restarted my router the PPPoE doesn’t authenticate at all.

We're still awaiting updates from NLD vendors. At this point we had our one JHB-KZN path go down at 3am, another at 10am, a third at 14:13 including our third path (KZN<>CPT). We have ordered a 4th path via the northern route (DFA's trenched path between KZN and JHB), which we are waiting on delivery, so we are in the process of ensuring additional redundancy to our existing 2 "extra" routes. The scale of this break is large, and affecting multiple networks, including a fail safe (yes I read the irony here) we implemented after January's NLD headaches. We will provide further feedback shortly.
 
Last edited:
We're still awaiting updates from NLD vendors. At this point we had our one JHB-KZN path go down at 3am, another at 10am, a third at 14:13 including our third path (KZN<>CPT). We have ordered a 4th path via the northern route (DFA's trenched path between KZN and JHB), which we are waiting on delivery, so we are in the process of ensuring additional redundancy to our existing 2 "extra" routes. The scale of this break is large, and affecting multiple networks, including a fail safe (yes I read the irony here) we implemented after January's NLD headaches. We will provide further feedback shortly.
Yes - DFA is still up - seems a good option.
 
Target Name: www.twitter.com
IP: 104.244.42.65
Date/Time: 2022/04/05 12:13:38 - 2022/04/05 12:23:38

Hop Sent PL% Min Max Avg Host Name / [IP]
1 76 0 0,26 61,58 3,97 192.168.0.1 [192.168.0.1]
2 76 0 2,07 13,19 2,69 core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 76 12 2,21 306,07 15,36 100.99.198.1 [100.99.198.1]
4 76 14 2,51 86,38 7,52 core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
5 76 9 2,32 267,62 14,74 165-65-148-197.as37497.za.net [197.148.65.165]
6 76 11 23,48 174,89 31,77 6-71-148-197.as37497.za.net [197.148.71.6]
7 76 12 164,17 341,07 178,29 54-71-148-197.as37497.za.net [197.148.71.54]
8 76 13 161,08 300,06 173,75 197.148.66.41 [197.148.66.41]
9 76 100 0 0 0 [-]
10 76 11 164,26 378,65 189,30 www.twitter.com [104.244.42.65]

Not sure what's happening, internet is really chugging.
Johannesburg, Floracliffe
 
Once again major packet loss. This issue is still occurring!

Ticket ID: 319848

View attachment 1283864
Target Name: www.twitter.com
IP: 104.244.42.65
Date/Time: 2022/04/05 12:13:38 - 2022/04/05 12:23:38

Hop Sent PL% Min Max Avg Host Name / [IP]
1 76 0 0,26 61,58 3,97 192.168.0.1 [192.168.0.1]
2 76 0 2,07 13,19 2,69 core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 76 12 2,21 306,07 15,36 100.99.198.1 [100.99.198.1]
4 76 14 2,51 86,38 7,52 core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
5 76 9 2,32 267,62 14,74 165-65-148-197.as37497.za.net [197.148.65.165]
6 76 11 23,48 174,89 31,77 6-71-148-197.as37497.za.net [197.148.71.6]
7 76 12 164,17 341,07 178,29 54-71-148-197.as37497.za.net [197.148.71.54]
8 76 13 161,08 300,06 173,75 197.148.66.41 [197.148.66.41]
9 76 100 0 0 0 [-]
10 76 11 164,26 378,65 189,30 www.twitter.com [104.244.42.65]

Not sure what's happening, internet is really chugging.
Johannesburg, Floracliffe
@TwinDucT still struggling here? Please log a ticket. @mystic007 hoping the test config helps us here.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X