PPPoE Client problem (some pages are slow)

zernz · Wed Oct 31, 2012 6:08 am

first, I'm sorry for my bad english...

I just make a PPPoE client config

here's my network thopology

internet
|
|
modem (bridge) 192.168.1.1
|
|
mikrotik 192.168.1.2 / 192.168.10.1
|
|
pc's 192.168.10.0/26

here's the configs:

interfaces -> pppoe client

add ac-name="" add-default-route=yes allow=pap,chap,mschap1,mschap2 comment=\
    "" dial-on-demand=no disabled=no interface=ether5-gateway max-mru=1480 \
    max-mtu=1480 mrru=disabled name=test password=xxxx profile=\
    default service-name="" use-peer-dns=no user=zzzzzz

ip -> firewall -> mangle :

/ip firewall mangle> print dynamic
Flags: X - disabled, I - invalid, D - dynamic 
 0 D chain=forward action=change-mss new-mss=1440 tcp-flags=syn protocol=tcp 
     in-interface=test tcp-mss=1441-65535 

 1 D chain=forward action=change-mss new-mss=1440 tcp-flags=syn protocol=tcp 
     out-interface=test tcp-mss=1441-65535

ip -> firewall -> nat :

/ip firewall nat> print
Flags: X - disabled, I - invalid, D - dynamic 
 0   ;;; BRIDGE MODE
     chain=srcnat action=masquerade out-interface=test

ip -> dns :

/ip dns> print
                servers: 8.8.8.8,8.8.4.4
  allow-remote-requests: yes
    max-udp-packet-size: 512
             cache-size: 2048KiB
          cache-max-ttl: 1w
             cache-used: 9KiB
[petrus@purishpga] /ip dns> static
[petrus@purishpga] /ip dns static> print
Flags: D - dynamic, X - disabled, R - regexp 
 #     NAME          ADDRESS                                         TTL         
 0     Google2       8.8.8.8                                         1d          
 1     Google1       8.8.4.4                                         1d

and here's the ping result:

Yahoo

ping www.yahoo.com
72.30.38.140 64 byte ping: ttl=52 time=231 ms
72.30.38.140 64 byte ping: ttl=52 time=235 ms
72.30.38.140 64 byte ping: ttl=52 time=300 ms
72.30.38.140 64 byte ping: ttl=52 time=308 ms
72.30.38.140 64 byte ping: ttl=52 time=231 ms
72.30.38.140 64 byte ping: ttl=52 time=272 ms
72.30.38.140 64 byte ping: ttl=52 time=231 ms
72.30.38.140 64 byte ping: ttl=52 time=286 ms
72.30.38.140 64 byte ping: ttl=52 time=317 ms
72.30.38.140 64 byte ping: ttl=52 time=232 ms
72.30.38.140 64 byte ping: ttl=52 time=241 ms
72.30.38.140 64 byte ping: ttl=52 time=290 ms
13 packets transmitted, 12 packets received, 7% packet loss
round-trip min/avg/max = 231/264.5/317 ms

Facebook

ping www.facebook.com
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=209 ms
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=209 ms
69.171.229.16 64 byte ping: ttl=244 time=209 ms
69.171.229.16 64 byte ping: ttl=244 time=211 ms
69.171.229.16 64 byte ping: ttl=244 time=209 ms
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=210 ms
69.171.229.16 64 byte ping: ttl=244 time=211 ms
69.171.229.16 64 byte ping: ttl=244 time=209 ms
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max = 209/209.7/211 ms

Google

ping www.google.com
173.194.38.176 64 byte ping: ttl=55 time=38 ms
173.194.38.176 64 byte ping: ttl=55 time=49 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=37 ms
173.194.38.176 64 byte ping: ttl=55 time=37 ms
173.194.38.176 64 byte ping: ttl=55 time=37 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
173.194.38.176 64 byte ping: ttl=55 time=36 ms
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max = 36/37.5/49 ms

Google dns : 8.8.8.8

ping 8.8.8.8
8.8.8.8 64 byte ping: ttl=50 time=50 ms
8.8.8.8 64 byte ping: ttl=50 time=50 ms
8.8.8.8 64 byte ping: ttl=50 time=45 ms
8.8.8.8 64 byte ping: ttl=50 time=49 ms
8.8.8.8 64 byte ping: ttl=50 time=46 ms
8.8.8.8 64 byte ping: ttl=50 time=45 ms
8.8.8.8 64 byte ping: ttl=50 time=51 ms
8.8.8.8 64 byte ping: ttl=50 time=48 ms
8.8.8.8 64 byte ping: ttl=50 time=45 ms
8.8.8.8 64 byte ping: ttl=50 time=49 ms
8.8.8.8 64 byte ping: ttl=50 time=52 ms
8.8.8.8 64 byte ping: ttl=50 time=47 ms
8.8.8.8 64 byte ping: ttl=50 time=43 ms
8.8.8.8 64 byte ping: ttl=50 time=47 ms
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max = 43/47.6/52 ms

Please help...
If anyone need the others config, I'll post them...

thx

jandafields · Wed Oct 31, 2012 5:13 pm

connect your pc to the router and ping yahoo.com without pppoe, and what are the results?

zernz · Thu Nov 01, 2012 4:38 am

sry, which router do you mean?

the mikrotik or adsl router one?

mixig · Thu Nov 01, 2012 1:03 pm

sry, which router do you mean?

the mikrotik or adsl router one?

Connect your PC directly to your adsl router, and than ping the same pages, what are the results?

zernz · Fri Nov 02, 2012 8:03 pm

oh, ok...

this is my bad...
I just get problem when opening yahoo pages and some others...
the pages load slowly or even worst wont load at all...

the ping is the same when I connect pc to adsl router..

I just made a fix, I made the order in the mangle of CHANGE MSS to the top... it's dynamic that appears when the pppoe connection is connected..

and now, everything's OK...

PPPoE Client problem (some pages are slow)

PPPoE Client problem (some pages are slow)

Re: PPPoE Client problem (some pages are slow)

Re: PPPoE Client problem (some pages are slow)

Re: PPPoE Client problem (some pages are slow)

Re: PPPoE Client problem (some pages are slow)