Who said that P1 was fast?
Im not sure what can help for P1 for a lower ping.

All PS3 users can't connect to Playstation Network. If can, later 5-10 minutes disconnected. Is this related to all the problems here.
Tq all

I've just spent some time researching on the IP addresses that i got:

Why is the 115.134.x.x ISP name, CORE IP NETWORK DEVELOPMENT?



While the others like 60.x, 124.x and 118.x are all under TELEKOM MALAYSIA BERHAD. Does anyone knows the difference?

Talking about the DSL Downstream rate.. my modem has always been showing a pathetic 1024.. but just now i was like when i saw the Downstream rate was 4000+ and Upstream rate was 800+ !!!

No joke, for the first time i saw something like that and i was too slow to print screen.. but only a few seconds later the DSL light blinked and reconnected.. the numbers went back to normal I have no idea what happened and how i wished i could get the 4MB status out of error lolx

I really have no idea why my friends and my cousin who is living in another area nearby can get the 1.5MB status while miine is still stucked at 1MB.. why??

By the way, can anyone who's using DLINK DSL-520B explain to me why the DNS Server and Alternate DNS Server are shown as 192.168.1.1? Aren't they supposed to be showing something like 202.188.0.133 and 202.188.1.5??

There is no official "1.5 Mbps" package. So if anyone is getting 1.5 Mbps under a 1 Mbps plan, he/she is lucky

Anyway, to explain the D-Link DNS: Your router (whose IP address is 192.168.1.1) acts as a DNS relay. The DNS relay's job is to listen on port 53 (within the local network), and forward all DNS requests from clients within the network to the upstream DNS server (in this case, the Streamyx DNS server). When your computer attempts to resolve a domain name, it will forward the request to your router, and your router in turn forwards the request to the Streamyx DNS server. Once the Streamyx DNS server passed the answer back to your router, your router will in turn pass the answer back to your computer.

This has few functions. Your router can act as a DNS cache. This means that your router will keep a list of recently resolved DNS queries so that your computer can obtain DNS answers more quickly (less latency). Another function is that you won't have to reconfigure all the computers within your network if you change your upstream DNS servers.

Hope this helps

Thanks CK for the opendns config guide.

I am using LinkSys WAG200G router/modem. I followed the guide and key in opendns ip into Static DNS 1 & 2 followed by save.
Switch to the Status tab and do a disconnect and connect. However its still showing the old streamyx DNS server:

Default Gateway:219.93.218.177
DNS1:202.188.0.133
DNS2:202.188.1.5

I tried powering off the router and shut down my PC. Turn router power on again and reboot PC(WinXP).
Still status show the same above.
What did I do wrong with configuration?
Do I need to config DNS on my PC?
Any help esp. from WAG200G user who happen to use OpenDNS server would be much appreciate.
Thanks

you can always set the DNS at your WinXP...it's the same thing with router config.....

infact my router cant config DNS so i have to config it at my comp...

This post has been edited by andrew9292: Jul 28 2009, 03:58 PM

Andrew,
Thanks for your advise. I config it on my computer and it confirmed on opendns site.
What if I use other DNS server like Jaring or P1.
How to check and confirm the key in DNS server are being connected?
In case of opendns, we can use their site to check. For others, how and what software are available to check DNS server being used?
In case of streamyx, 202.188.0.133 is always primary and 202.188.1.5 is secondary.
Can this be change to make 202.188.1.5 primary as this has less packet lost?
Thanks

errr....how does packet loss relate to dns performance? dns will still work if there's a filter in place right? ping www.windowsupdate.com gives 100% packet loss but the site still works.

Just config it on your computer, if you can load pages after that, means the DNS is working.

http://www.infoarch.net/s_broadband.htm ... a page of all DNS to use in this region

HOWEVER, Jaring DNS has blocked non Jaring users, do using Jaring DNS you will not get good conenctivity. P1 DNS also, only their 1st DNS responds to non P1 users now. all other p1 DNS do no respond to outsiders.



that is because that website blocks ICMP pings, same goes with www.hotmail.com....

If a website is pingable, but shows some packet loss, then it has problems

If a website is pingable and show 100% PL, but accesible, that means it is blocking pings.

Ig a website is not pingable and canot access..means its DOWN

i don' think this is true 100% of the time. my network admin at the office just showed me that its also possible to limit pings...according to him this is a common security practice. i goggled around and found this


One obvious application of rate limiting on incoming traffic is to block ping flooding. We can obviously block ping floods with a rule blocking incoming echo-request ICMP packets altogether, but this is inelegant; this is linux, remember? What we want to do, rather, is to allow such packets but only in small quantities. Have a look at the relevant rule:

iptables -A INPUT -p ICMP -icmp-type echo-request -m limit -limit 1/minute -limit-burst 5 -j ACCEPT

-limit 1/minute will do what it says; it will only match for a rate of incoming packets up to an average of 1 per minute. The operative word here is average. So, does this mean that the first ping request you get will be accepted, then none for a whole minute? Not quite.

-limit-burst 5 tells iptables to let 5 such packets in before permitting the rule to match; so, in one minute, we can have 5 ping requests popping through. So, -limit 1/minute permits a maximum of 1 packet per minute on average, but -limit-burst 5 permits 5 in one shot. Have we found a logical error in iptables? No you silly clod, remember, -limit stes a limit on average, whereas -limit-burst limits by number of packets in one go. What will happen then in our example?

The firewall will let the first 5 packets in in the first minute, thanks to -limit-burst 5; this means, however, that the packets/minute now is 5, so any further packets are blocked until packets/minute = 1, i.e. 5 minutes later. In the sixth minute, packets/minute will be 5/6 < 1, so another ping request will be let in. When the extra ping request is admitted, the ratio becomes 6/6 = 1 again, and packets are DROPped again until the next minute. Again, average is the operative word.

Source : http://www.geocities.com/youssef116/writing/ratelim.html


for the case of tmnut, it can either really be an issue or they are just being paranoid and have an archaic filter up. as for me, i've tried both the default tm dns and open dns and so far have not noticed any noticeable differences. i *have* however noticed that tm's servers somehow give better performance for facebook liao. let's just hope that this is no fluke and that tm is finally waking up!

C:\Documents and Settings\Shuwei>nslookup www.facebook.com. resolver1.opendns.com

Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: www.facebook.com
Address: 69.63.186.11 ----> US IP?


C:\Documents and Settings\Shuwei>nslookup www.facebook.com. 202.188.0.133
Server: cns3.tm.net.my
Address: 202.188.0.133

Non-authoritative answer:
Name: a2047.w7.akamai.net
Addresses: 203.106.85.48, 203.106.85.176, 203.106.85.57, 203.106.85.64
203.106.85.184, 203.106.85.163, 203.106.85.193, 203.106.85.169, 203.106.85.59 -----> Malaysian??
Aliases: www.facebook.com, www.facebook.com.edgesuite.net


C:\Documents and Settings\Shuwei>ping 69.63.186.11

Pinging 69.63.186.11 with 32 bytes of data:

Reply from 69.63.186.11: bytes=32 time=401ms TTL=238
Reply from 69.63.186.11: bytes=32 time=319ms TTL=238
Reply from 69.63.186.11: bytes=32 time=343ms TTL=238
Reply from 69.63.186.11: bytes=32 time=351ms TTL=238

Ping statistics for 69.63.186.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 319ms, Maximum = 401ms, Average = 353ms



C:\Documents and Settings\Shuwei>ping 203.106.85.48

Pinging 203.106.85.48 with 32 bytes of data:

Reply from 203.106.85.48: bytes=32 time=32ms TTL=55
Reply from 203.106.85.48: bytes=32 time=32ms TTL=55
Reply from 203.106.85.48: bytes=32 time=30ms TTL=55
Reply from 203.106.85.48: bytes=32 time=30ms TTL=55

Ping statistics for 203.106.85.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 32ms, Average = 31ms

This post has been edited by tadwinks: Aug 1 2009, 02:19 AM

Andrew,
Thank you for your usefull and detail explaination.
My question on:
In case of streamyx, 202.188.0.133 is always primary and 202.188.1.5 is secondary.
Can this be change to make 202.188.1.5 primary as this has less packet lost?
Any inputs on this?
Thanks again for your help and have a nice day.

yes but only a very small amount of webpages practice this method.

---

Added on August 1, 2009, 12:00 pm

Yes, just input 202.188.1.5 into the box @ preferred DNS server when you change your DNS through computer. It will be then used as the primary DNS for your connections.

Then you can also input another non-TM DNS (like OPENDNS) at the alternate DNS server box.

This post has been edited by andrew9292: Aug 1 2009, 12:00 PM

I have 2 DNS servers that i have been using for years without any problems.

203.115.225.24
203.115.225.25

These are NTT Public DNS servers, which is less likely to face problems. Speeds are fast the all the time.

nice DNS there... thanks... using it now...

but it blocks ICMP pings, so we wont be able to tell if it's having problems or not... and also to check the latency... =\

I'm facing this problem when goes to facebook, this message appear all of sudden, it is first time... TM fault?

This post has been edited by pengiranijam: Aug 6 2009, 10:03 PM

Tried using open dns it looks like i can integrated open dns inside my hotspot system and it's working perfectly, good for deployment in school and university so we can manage to block students for unnecessary surfing and prawn

today opendns are blocking all the XXX website, i have selected Minimal as my filtering level. It is TMNut problem or opendns?

XXX website always got malicious code, OpenDns blocked that kind of site for your safety

seems not only tmnet, i'm using maxis wired also experienced shitty dns problem.

even this lowyat page i had to refresh nearly 20 times then only can connect. and when it's connected, it's fast. it's not about speed