Ray, Thank for your review,

> Right. Obviously (I hope this is obvious) you cannot use a source with a
> 1.5 Mbps upload limit to test a 2 Mbps download ... unless, I suppose, the
> 2 Mbps connection is running *way* below rated speed. You might do better
> to find a public ftp repository (a Linux-distro mirror, for example) near
> you and do some downloads from it.

Done, here the result :
---> RETR linux-2.6.6.tar.bz2
150-Connecting to port 2403
150 34078.3 kbytes to download
[....] ############################## [....]
226-File successfully transferred
226 490.382 seconds (measured here), 69.49 Kbytes per second
ftp: 34896138 bytes received in 492.34Seconds 70.88Kbytes/sec.
ftp>

I'm using the public repository one that near my place at Malaysia. (
ftp://ftp.averse.lkams.kernel.org/ )
When i run traceroute, it was about 14 hop from my local LAN :

  1     *        *        *     Request timed out.
  2     1 ms     1 ms     1 ms  202.185.xxx.xxx
  3     4 ms     4 ms     4 ms  161.142.xxx.xxx
  4     4 ms     4 ms     5 ms  e0.sha15.jaring.my [161.142.236.16]
  5     8 ms     7 ms     7 ms  s4-1-2.bkj4.jaring.my [61.6.2.93]
  6    27 ms    19 ms    23 ms  161.142.173.90
  7     9 ms     9 ms    10 ms  pos0-0.mlk90.jaring.my [161.142.25.86]
  8    27 ms    19 ms    12 ms  pos2-0.mea90.jaring.my [61.6.17.46]
  9    29 ms    13 ms    12 ms  fe-5-1-0.mea15.jaring.my [61.6.17.70]
 10    15 ms    16 ms    19 ms  203.208.152.9
 11    19 ms    31 ms    16 ms  POS3-6.tp-core1.ix.singtel.com
[202.160.250.9]
 12    17 ms    30 ms    18 ms  202.160.250.54
 13    27 ms    20 ms    23 ms  PC2.commonwealth.singnet.com.sg
[165.21.12.26]
 14    27 ms    33 ms    20 ms  203.127.221.98

Is the result makes any sense for 2Mbps line?

> [...]
> > > As to your Web-page problem ...

> Even simpler ... on the LAN host you are testing from, change its DNS from
> the router to use the "upstream" DNS resolver directly. If this improves
> performance, than suspect dnsmasq as the cause of the problem. If it
> doesn't, then use an app like "host" to test the response speed of the
> upstream DNS (which I assume is your ISP's DNS forwarder).

Done, still experiance a same problems. I get a fast response's result with
dns query using host :

yahoo.com name server ns1.yahoo.com
yahoo.com name server ns2.yahoo.com
yahoo.com name server ns3.yahoo.com
yahoo.com name server ns4.yahoo.com
yahoo.com name server ns5.yahoo.com
yahoo.com mail is handled (pri=1) by mx2.mail.yahoo.com
yahoo.com mail is handled (pri=5) by mx4.mail.yahoo.com
yahoo.com mail is handled (pri=1) by mx1.mail.yahoo.com

www.yahoo.com is a nickname for www.yahoo.akadns.net
www.yahoo.akadns.net has address 66.94.230.42
www.yahoo.akadns.net has address 66.94.230.35
www.yahoo.akadns.net has address 66.94.230.44
www.yahoo.akadns.net has address 66.94.230.37
www.yahoo.akadns.net has address 66.94.230.39
www.yahoo.akadns.net has address 66.94.230.43
www.yahoo.akadns.net has address 66.94.230.38
www.yahoo.akadns.net has address 66.94.230.34

> Do you mean that images actually *stored* on your DMZ Web server (not just
> offsite ones referenced by it) exhibit this problem?

yup,

> If that's the case,
> then problems with connections from the DMZ to the LAN (do you mean the
> "staff ntwork" or the "student network"? or both? you seem to have 2
> "local" LANs) are almost surely related to the router swap.

Both LAN and sorry to ask, if it was a problem with the router swap, how i
could troubleshoot or correct it? if there was a way to do it.

> The only other thing I would direct your attention to is the
> extraordinarily high collision rate on eth3. As you report it ...
>
> >6: eth3: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> >     link/ether 00:04:ac:6e:52:b8 brd ff:ff:ff:ff:ff:ff
> >     RX: bytes  packets  errors  dropped overrun mcast
> >     3229811836 726754647 0       0       0       0
> >     TX: bytes  packets  errors  dropped carrier collsns
> >     310837687  6346146  0       0       0       2149416
>
> ... 2 million collisions against 6 million packets is simply awful. But
> since I don't know if the "local LAN" exhibiting the problem is this one
or
> eth0 (or both), I do not know if this is relevant to your problem.

eth0 is connected to my staff network ( 192.168.0.0/24 ) and eth3 is
connected to my student network ( 192.168.1.0/24 ) . Is there any how i
could trace the source of collisions? Do you have any other suggestions or
advice?

Thanks In Advance,
Regards,
zamri

*----------------------------------------------------------------*
i dont held any responsible with anything below than this line and it's
was beyong my control and knowledge. - zamri -
*----------------------------------------------------------------*




The content of this email and any files transmitted with it are confidential and 
intended solely for the use of individual or entity to whom they are address and may 
be privileged. If you are not the intended receipient or if you have received it in 
error, please do not read, use, print, copy, forward or distribute the content or 
disclose it to anyone. Instead, please inform the sender by return email or telephone 
and please delete it or any copy of it from your system immediately. Opinions, 
conclusions and other informations in this messages that do not relate to the official 
businness of PTPL Group Of Companies shall be understood as neither given nor endorsed 
by PTPL SDN. BHD.



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to