Vox Telecom Fatpipe

Hi all. Could I trouble you for some traces? I'm trying to collect from my side as well.
 
Tracing route to vox.co.za [196.41.6.140]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 15 ms 12 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
4 10 ms 11 ms 10 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
5 48 ms 50 ms 48 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
6 11 ms 12 ms 13 ms 41.193.120.113
7 30 ms 30 ms 31 ms 41.193.119.49
8 29 ms 30 ms 31 ms 41.193.32.201
9 29 ms 29 ms 40 ms 41.193.32.150
10 34 ms 30 ms 30 ms 196.41.6.140
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.


Tracing route to cnn.com [157.166.226.25]
over a maximum of 30 hops:

1 4 ms 2 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 11 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
4 25 ms 21 ms 30 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
5 28 ms 25 ms 18 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
6 15 ms 13 ms 12 ms 41.193.120.113
7 179 ms 180 ms 178 ms vox-ldn-telecity-wacs.vox.co.za [196.41.24.174]

8 179 ms 202 ms 178 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 * * * Request timed out.
10 262 ms 262 ms 262 ms TIME-WARNER.ear1.Atlanta2.Level3.net [4.59.12.2]

11 * * * Request timed out.
12 * * * Request timed out.
13 265 ms 265 ms 264 ms www.cnn.com [157.166.226.25]

Trace complete.



Tracing route to is.co.za [196.26.2.114]
over a maximum of 30 hops:

1 3 ms 3 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 13 ms 12 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
4 12 ms 12 ms 11 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
5 12 ms 12 ms 13 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
6 13 ms 12 ms 15 ms 41.193.120.113
7 16 ms 23 ms 15 ms 41.193.120.122
8 16 ms 15 ms 13 ms is.cinx.net.za [196.223.22.10]
9 13 ms 12 ms 12 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.1
2]
10 28 ms 28 ms 28 ms 168.209.100.101
11 28 ms 28 ms 29 ms core1a-pkl-te1-2.isnet.net [168.209.100.238]
12 28 ms 28 ms 28 ms core2a-bry-gi1-0-0.ip.isnet.net [168.209.218.2]

13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
 
Gambit said:
The speed of light is not constant and therefore you are correct that the transportation medium (and even gravity) does affect the speed of light but fibre and copper both run at the speed of light and therefore you saying "Light should by all accounts travel faster." didn't make sense to me and that is why I was asking "faster than what".

Even though copper may be slightly slower than Fibre it is so small that over the 5km distance between your ADSL modem and the exchange it really doesn't make any difference to the latency. The local loop would need to be millions of kilometres to really make a measurable difference. Fibre is better than copper because it can easily facilitate way more bandwidth over long distances with very low signal loss.
Click to expand...
Not quite. There's a big difference between an electron and a photon. Unless you want to explain?
 
plot.jpg


The ping spikes in the first few vox steps is what I believe the problem is...

It makes gaming impossible when your ping sits at 180 - then 200 - then 280 - then 200 - then 260 et etc etc
 
Thanx all. I'm escalating these samples asap
 
Hey guys, is 'Zero-rated usage' my usage between 12am and 6am? I'm on the 150GB FP promo plan.
 
requiem said:
View attachment 317081


The ping spikes in the first few vox steps is what I believe the problem is...

It makes gaming impossible when your ping sits at 180 - then 200 - then 280 - then 200 - then 260 et etc etc
Click to expand...
That 3rd hop problem was supposed to have been resolved by an IPC upgrade at the CT Barrack St. Telkom/Vox link.

I still see it popping up occasionally.
 
AntiGanda said:
That 3rd hop problem was supposed to have been resolved by an IPC upgrade at the CT Barrack St. Telkom/Vox link.

I still see it popping up occasionally.
Click to expand...

It is the whole of the 41.193 range.

I assume it is a lack of capacity somewhere within Vox. WA doesn't have the problem.

I really don't want to keep playing Musical ISP
 
So bolt on coming to a end 30 November...... What a sad day for a very unique type account.....
 
requiem said:
It is the whole of the 41.193 range.

I assume it is a lack of capacity somewhere within Vox. WA doesn't have the problem.

I really don't want to keep playing Musical ISP
Click to expand...
Yes, it's not great.

What irks me is that they said this very problem was fixed. It makes me question what else they said that wasn't true.
 
jsheed_sa said:
Only for the LITE account though.

I've just joined VOX - how does the uncapped addon work for the weekend? From Midnight Fri to 06:00 Mon morning?
Click to expand...
The Fat Pipe lite plus bolton works from 18:00 Friday until 06:00 Monday on weekends.
 
Soul Assassin said:
In the email or SMS they sent you it should have a Account ID which you use, not your ADSL account details.
Click to expand...

I didn't get an email, only an SMS and all the SMS has is ADSL user / pass and a support number. Nothing else.

Additionally the username they sent out was wrong as it didn't include the @ sign. I had to call support to get the correct details. Mildly annoying start so far.

Thanks for the feedback though.

EDIT:

Did some digging and found out why. Vox's mail servers aren't configured correctly (go figure).

They a) haven't setup rDNS and b) resolve to a local DNS entry - so my Postfix install has blocked them.

Code: 
root@meyling:# dig -x 209.203.37.214

; <<>> DiG 9.9.5-9+deb8u3-Debian <<>> -x 209.203.37.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54847
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;214.37.203.209.in-addr.arpa.	IN	PTR

;; AUTHORITY SECTION:
37.203.209.in-addr.arpa. 189	IN	SOA	ns1.datapro.co.za. hostmaster.datapro.co.za. 2013013004 1800 900 86400 3600

;; Query time: 0 msec
;; SERVER: 62.210.16.6#53(62.210.16.6)
;; WHEN: Fri Nov 20 19:31:13 SAST 2015
;; MSG SIZE  rcvd: 120

Code: 
Nov 20 18:59:22 meyling postfix/smtpd[9332]: NOQUEUE: reject: RCPT from unknown[209.203.37.214]: 450 4.7.1 <titania.localdomain>: Helo command rejected: Host not found; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<titania.localdomain>

I reject mail if I can't verify the helo hostname - as having no verification = SPAM SPAM SPAM

Code: 
root@meyling:/# cat /etc/postfix/main.cf | grep reject_unknown
   reject_unknown_sender_domain
   reject_unknown_helo_hostname,
   reject_unknown_reverse_client_hostname,

So they need to setup rDNS and configure the server to use titania.localdomain as the name if applicable.

VOX - you're not conforming to RFC 2821:

"The domain name given in the EHLO command MUST BE either a primary host name (a domain name that resolves to an A RR) or, if the host has no name, an address literal as described in section 4.1.1.1"

Anyone I can mail that will actually pay attention and fix?
 
Last edited:
cavedog said:
So bolt on coming to a end 30 November...... What a sad day for a very unique type account.....
Click to expand...

So no new bolt-on accounts being sold, but existing accounts, I'm assuming, will be honoured for as long as the subscriber, subscribes?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X