Unexplained HTTP issues with SAINET

[Pada]

I've just moved to a SAINET 384kbps uncapped account, however I have a few strange/unexplained things going on...

On my user account page, it said that I have a "Prepaid Quota" of 62.5GB? Its supposed to be uncapped... Now its already at like 60GB.

The other thing that I can't explain is why websites (HTTP protocol) aren't working. I can ping local & international destinations with decent latencies (like 50ms for local & 300ms for google) and I can connect to IRC & Warcraft III servers just fine. HTTPS is also working, but not HTTP.
Eventually I had the idea of enabling my transparent proxy on my MikroTik RB750 and now HTTP is also working. I have absolutely now idea why it would only work when my Transparent proxy is enabled? My guess is that their transparent proxy servers are sensitive to DSCP (TOS) or TTL.

Ideas would be appreciated. For now I'll be able to live with a transparent proxy

 

[Tinuva]

Maybe you have a rule on your mikrotik to enable the transparent proxying in the firewall, but while the webproxy is disabled that would break all http connections. It is all I can think of?

 

[Pada]

Tinuva, that was definitely not the case. I explicitly disabled the transparent proxy and all the NAT/Mangling rules that went along with it, due to a certain IRC server not allowing any Proxy services being hosted on your IP address. My Internet was working 100% without the transparent proxy with IS Local Only & Axxess accounts, but not with the SAINET account...

 

[Basjohn]

Now not sure if this is entirely related but on DC I've experienced a similar issue a few times. My router being a n00besque Belkin lacks a transparent proxy feature for me to have tested it with but in general I sometimes found when DC was acting up HTTPS would work, pinging would work, IMing would work but http connections would fail. Is SAINET's uncapped service also running through BCSnet? Perhaps there's an adjustment made on the ISP level to accommodate this and SAINET are simply still figuring that out? (As this hasn't happened on DC for several weeks now).

Anyway not sure of the likely hood of this being involved and no idea why enabling the transparent proxy sorted things but just adding some ideas to the pot.

 

[Pada]

I'm also hosting a VPN on my MikroTik, so that I can access it from work. I was able to visit HTTP sites without the transparent proxy being enabled when I used the PPTP VPN from work, which was dialed by my PC.
At my friend's home, who's also sharing my connection, connected to the same VPN service, but with his MikroTik router and he had the same issue where HTTP sites didn't work.

Maybe I should run Wireshark and see what if I can figure out what is going on...
Here's my traceroute to www.aardvark.co.za:

  4   244 ms   243 ms   330 ms  grzar01-gig3-50.neoinx.net [41.216.193.174]
  5   206 ms   231 ms   162 ms  grzisg01-ms-50.neoinx.net [41.216.193.177]
  6    94 ms    72 ms    86 ms  sainetcr02-eth2-vlan215.neoinx.net [41.216.193.190]
  7   111 ms   116 ms    74 ms  grzcr01-eth1.neoinx.net [41.216.193.1]
  8    62 ms   256 ms   122 ms  grzbr01.neoinx.net [41.216.193.14]
  9   164 ms   192 ms   191 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.110.45]
 10   122 ms   190 ms   136 ms  nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.58]
 11   150 ms   131 ms   132 ms  196.25.181.54
 12   169 ms     *      104 ms  196.25.211.106

 

[Pada]

I've reached 0 bytes left on the cap. Now I'm getting 'failed to authenticate ourselves to peer' error on my MikroTik RB750 and the account doesn't want to work anymore. LOL

This was supposed to be uncapped... with the account name being [email protected]

Luckily I still own a few other accounts to get by with until this cap issue has been resolved too

 

[Pada]

This is definitely a first for me:

Unfortunately this account has been disabled due to bandwidth abuse. You have subscribed for 384k uncapped but your line is currently running at 4MB. Until this line is running at 384k this account cannot be reactivated.

 

[pjjdp]

This is definitely a first for me:

For me too. But it makes sense. Hoever it's good to know they are not throttling the service to 384. It will probably mean better speeds/latency

 

[Pada]

Here's a whole thread where SAINET related stuff is discussed: http://mybroadband.co.za/vb/showthread.php?216319-SAINET