A client's domain is hosted with MWEB with about 14 mailboxes, the client has a Telkom line, for internet access. Due to MWEB and Telkom not peering locally, I had to install a temporary 3G ethernet router and modify the Linux Gateway's routing table to port only pop3.mweb.co.za and smtp.mweb.co.za traffic over the 3G router, thus enabling the client to send and receive e-mail without the high latency. This solution worked well and a few weeks ago I noticed that traffic between Telkom and MWEB were once again routed locally, so I uninsulated and decommissioned the 3G router. The setup worked 100% until Friday, all of a sudden traffic to pop3.mweb.co.za where dropped, but traffic to smtp.mweb.co.za remained unaffected.
From the route trace it is evident that the traffic is still routed locally, but dropped instead. MWEB support advised me to rather use pop3.mweb.net. Having 14 users, I decided to point requests to pop3.mweb.co.za to pop3.mweb.net by adding an entry in the Linux Gateway's hosts file. This worked great until this morning, when pop3.mweb.net, also became unreachable over the Telkom line.Now I am forced to re-setup the 3G router and remap traffic.
Whom is the stubborn party here, Telkom or MWEB. Should I advise the client to cancel the Telkom Tidus line (no ADSL available in this area), and install a solution or rather just migrate their domain away from MWEB?
Code:
[root@pdc /]# traceroute pop3.mweb.co.za
traceroute to pop3.mweb.co.za (196.28.76.80), 30 hops max, 40 byte packets
1 196.25.202.193 (196.25.202.193) 2.433 ms 3.133 ms 3.654 ms
2 obfn-ip-esr-1-wan.telkom-ipnet.co.za (196.25.90.225) 22.461 ms 26.997 ms 31.891 ms
3 196.43.11.202 (196.43.11.202) 44.643 ms 49.388 ms 53.946 ms
4 196.43.25.138 (196.43.25.138) 58.946 ms 63.672 ms 68.418 ms
5 197-80-4-118.jhb.mweb.co.za (197.80.4.118) 75.794 ms 79.726 ms 84.386 ms
6 vl-11.vic-hscore-1.mweb.co.za (196.22.169.227) 88.450 ms 26.485 ms 26.185 ms
7 tengig-3-1.vic-core-sw1.mweb.co.za (196.22.169.66) 31.255 ms 40.639 ms 45.313 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 *
[root@pdc /]#From the route trace it is evident that the traffic is still routed locally, but dropped instead. MWEB support advised me to rather use pop3.mweb.net. Having 14 users, I decided to point requests to pop3.mweb.co.za to pop3.mweb.net by adding an entry in the Linux Gateway's hosts file. This worked great until this morning, when pop3.mweb.net, also became unreachable over the Telkom line.Now I am forced to re-setup the 3G router and remap traffic.
Whom is the stubborn party here, Telkom or MWEB. Should I advise the client to cancel the Telkom Tidus line (no ADSL available in this area), and install a solution or rather just migrate their domain away from MWEB?
