Community discussions

MikroTik App
 
elhombredelabata
just joined
Topic Author
Posts: 10
Joined: Wed May 23, 2007 2:47 am

ADSL PPPOE client not working fine

Tue Oct 09, 2007 3:10 am

Hi everyone, i am running a new asdl line. i used to run a cablemodem connection that asign the public ip address directly to the mikrotik wan interface (eth3).

The adsl modem is a cheap one that my isp gives to new clients, so i cant make port forwarding or things like that. I configure the device in BRIDGE mode and whit my windows PC and a direct PPOE connection everything works fine. When i configure the pppoe client in the mikrotik an change the masquerade rule, internet works in all the pcs connected to it, but some url dont respond.

I can not surf the web normally. I tried changing the MTU but nothing seems to fix the problem. Web sites like microsoft.com or the forum.mikrotik.com never respond.

Anyone has a clue?

Thanks a lot.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 2:18 am

what about tracing the route to these sites?
 
User avatar
t3rm
Member Candidate
Member Candidate
Posts: 143
Joined: Sat Aug 04, 2007 1:57 pm
Location: Bandung - WJ - Indonesia

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 9:48 am

1. Make sure you have the ip address assigned by modem, and check the routing tables. You should have default gateway routing and the ip address itself. Be sure to check the DNS Servers assigned also. Check with ping. Got reply ?
2. Give the report of pinging the host: http://www.mikrotik.com , what is the ip ?
3. Open the command prompt windows, type like this below:

C:\> telnet http://www.mikrotik.com 80

Hit ENTER after that, wait .. if your screen turn and goes blank, it means connected.
If not, there is something wrong


- Rio.Martin -
 
kvan64
Member Candidate
Member Candidate
Posts: 186
Joined: Tue Apr 10, 2007 1:54 pm
Location: Brisbane Australia
Contact:

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 2:35 pm

what about tracing the route to these sites?
could you show me how to do this? Thanks
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 4:32 pm

what about tracing the route to these sites?
could you show me how to do this? Thanks
in command prompt, type
tracert mikrotik.com
 
User avatar
gmsmstr
Trainer
Trainer
Posts: 982
Joined: Fri Jun 04, 2004 2:22 am
Location: St. Louis, MO
Contact:

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 4:45 pm

Check your MTU too. Should be 1400 or so. Less than 1460.
 
joie
newbie
Posts: 46
Joined: Tue May 22, 2007 10:49 pm

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 5:57 pm

Did you do this?

http://forum.mikrotik.com/viewtopic.php ... t=&p=76334

MT is not that great for a PPPoE router. I was hoping to use some of them for certain customers but it's just not reliable. Those mangles rules work in my office but if I take the same router to a customer site it doesn't work so I just stopped trying. Hopefully one day MT will make them auto like every other router out there so we don't need mangle rules or anything like that, just plug and play.
 
elhombredelabata
just joined
Topic Author
Posts: 10
Joined: Wed May 23, 2007 2:47 am

Re: ADSL PPPOE client not working fine

Wed Oct 10, 2007 6:38 pm

Thanks everyone for the answers.

I found the solution in another post of this forum:

[url]http://forum.mikrotik.com/viewtopic.php ... U+Problems[/url]

Only need is to add a mangle rule:

add chain=forward protocol=tcp out-interface=cityconnect tcp-flags=syn action=change-mss new-mss=1440

Now everything works fine.

I don´t know exactly what the rule does, but i read that the mss-tcp option in the pppoe profile did not work, so this rule solves the MTU fragmentation problem.

Another solution was adding this other rules:

/ ip firewall mangle
add chain=forward tcp-flags=syn action=jump jump-target=mss comment="\[tcp\], mss" disabled=no
add chain=mss protocol=tcp tcp-flags=syn tcp-mss=!536-1460 action=change-mss new-mss=1440 comment="\[tcp\], mss fixation" disabled=no
add chain=mss protocol=tcp tcp-flags=syn tcp-mss=1453-65535 action=change-mss new-mss=1440 comment="\[tcp\], mss 1440 for mtu 1492" disabled=no
add chain=mss protocol=tcp tcp-flags=syn action=change-mss new-mss=clamp-to-pmtu comment="\[tcp\], mss clamp-to-pmtu" disabled=no
add chain=prerouting action=change-ttl new-ttl=set:65 comment="\[tcp\], mss ttl fix" disabled=no

I don´t test this ones, the first one works for me.

Thanks a lot for the interest in this topic and for the posts in the forums that help me with this problem.

Who is online

Users browsing this forum: critter and 119 guests