Greetings Friends.
I used to have a DSL Tplink router (for PPPoE connection). I replaced it with RB951Ui-2HnD
I'm stuck with making a simple PPPoE Client connection. Is it possible that my ISP is blocking cloned MAC (from Tplink).
Though The PPPoE Connection is established and able to ping the gateway from router and computer.
I cannot ping 8.8.8.8 from router or computer.
My configuration is listed below.

[admin@MikroTik] > ip firewall nat print
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=masquerade out-interface=pppoe-out1

[admin@MikroTik] > ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE
0 192.168.4.1/24 192.168.4.0 e4-LAN
1 D 182.50.xx.yy/32 182.50.67.xx pppoe-out1
2 D 10.115.99.22/24 10.115.99.0 e3-DSL

[admin@MikroTik] > ip route print
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 10.115.99.1 0
1 DS 0.0.0.0/0 182.50.67.xxx 1
2 ADC 10.115.99.0/24 10.115.99.22 e3-DSL 0
3 ADC 182.50.xx.yy/32 182.50.67.xx pppoe-out1 0
4 ADC 192.168.4.0/24 192.168.4.1 e4-LAN 0

[admin@MikroTik] > ping 182.50.67.xxx
HOST SIZE TTL TIME STATUS
182.50.67.xxx 56 64 8ms
182.50.67.xxx 56 64 6ms
182.50.67.xxx 56 64 9ms
182.50.67.xxx 56 64 3ms
182.50.67.xxx 56 64 8ms
sent=5 received=5 packet-loss=0% min-rtt=3ms avg-rtt=6ms max-rtt=9ms

[

admin@MikroTik] > ping 8.8.8.8
HOST SIZE TTL TIME STATUS
8.8.8.8 timeout
8.8.8.8 timeout
8.8.8.8 timeout
8.8.8.8 timeout
8.8.8.8 timeout
sent=5 received=0 packet-loss=100%

Thanks

Code: Select all

[admin@MikroTik] > ip route print
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          10.115.99.1               0 <======= here is the problem
 1  DS  0.0.0.0/0                          182.50.67.xxx             1
 2 ADC  10.115.99.0/24     10.115.99.22    e3-DSL                    0
 3 ADC  182.50.xx.yy/32    182.50.67.xx    pppoe-out1                0
 4 ADC  192.168.4.0/24     192.168.4.1     e4-LAN                    0

There's your problem. Your connection on e3-DSL is getting a better default route than the pppoe interface is.
Note the distance = 0 on the dsl, and 1 on the pppoe.
(lowest distance is the tie-breaker)

To fix it, go into your dhcp-client configured for e3-DSL, and where it's configured to use the default gateway there, change the distance from 0 to 2 or higher. (but lower than 255, which is "unreachable")

That will fix the routing issue.

The thing that really should catch your eye when looking at this is not the distance, but the lack of the 'A' flag (active) on the route that you wanted to be the default route.

As per the Doctor's Instruction.
I changed the settings ZeroByte mentioned.
It worked like a charm.



One thing i'm concerned is, if i have to make the same type of DSL PPPoE connection at my friends apartment then do i have to do it the same changes manually. i.e. Changing the "Default Route Distance = x"
or there is a process if you create the interface first than you will get the proper default route distance.
It worked but i just want to know how to do it so that i can understand better.
Thanks ZeroByte

One thing i'm concerned is, if i have to make the same type of DSL PPPoE connection at my friends apartment then do i have to do it the same changes manually. i.e. Changing the "Default Route Distance = x"
or there is a process if you create the interface first than you will get the proper default route distance.
It worked but i just want to know how to do it so that i can understand better.
Thanks ZeroByte

Well, 0 is the default distance for a default gw from DHCP and 1 is the default for pppoe. This is just normal.
It's a bit unusual to intentionally configure dhcp and pppoe client at the same time on the same interface, though.
That's why you got the unusual behavior. If the dhcp is there just to get a management address to reach the DSL modem or something, then you could just un-check the "use default gateway" setting on the dhcp client and then it will not try to become your internet connection - it will just obtain an address.

Well, 0 is the default distance for a default gw from DHCP and 1 is the default for pppoe. This is just normal.
It's a bit unusual to intentionally configure dhcp and pppoe client at the same time on the same interface, though.
That's why you got the unusual behavior. If the dhcp is there just to get a management address to reach the DSL modem or something, then you could just un-check the "use default gateway" setting on the dhcp client and then it will not try to become your internet connection - it will just obtain an address.

Wow... Now i can see the clear blue sky...
Thanks a ton for blowing off the clouds..
I don't know when i will reach people like your's level of expertise
Many Thanks Friend

Hello Admins & Mods, Is there a button ? To Mark it as Solved ???

Wow... Now i can see the clear blue sky...
Thanks a ton for blowing off the clouds..
I don't know when i will reach people like your's level of expertise
Many Thanks Friend

I've been at this for quite some time now - as long as you enjoy learning about networks and always try to learn more, and never come to think of yourself as the greatest expert of all time, (so many in this business do that) then you will have no limit to your expertise.

Well, 0 is the default distance for a default gw from DHCP and 1 is the default for pppoe. This is just normal.
It's a bit unusual to intentionally configure dhcp and pppoe client at the same time on the same interface, though.
That's why you got the unusual behavior. If the dhcp is there just to get a management address to reach the DSL modem or something, then you could just un-check the "use default gateway" setting on the dhcp client and then it will not try to become your internet connection - it will just obtain an address.

Wow... Now i can see the clear blue sky...
Thanks a ton for blowing off the clouds..
I don't know when i will reach people like your's level of expertise
Many Thanks Friend

After reading your reply i disabled dhcp in the interface.
Actually this is the actual config that i should have done.
Now it's pretty clean and understandable.

Lean and mean!
That's the way it should be.

I did do one interesting thing with my own WAN interface - DOCSIS devices default to having a management IP of 192.168.100.1
So I added 192.168.100.2/24 as a static second IP address, and made a srcnat rule such that if I browse to 192.168.100.1 from my LAN, then I get masqueraded as 100.2 and not the public IP.

This way, if I need to call tech support and see the status of my modem, I don't need to go dig out the modem from my entertainment center, unplug the router and plug in my laptop with an ethernet cable and configure a static IP on the Local Area Connection profile. I just browse from wherever.


It only added one rule to my firewall, so I decided, "Why not?"

Wow... Now i can see the clear blue sky...
Thanks a ton for blowing off the clouds..
I don't know when i will reach people like your's level of expertise
Many Thanks Friend

I've been at this for quite some time now - as long as you enjoy learning about networks and always try to learn more, and never come to think of yourself as the greatest expert of all time, (so many in this business do that) then you will have no limit to your expertise.

I Agree with you.