Hi all,

I have a router connected to 2 ISP's. One ISP provides Dynamic IP, the other gives a /26 of addresses.

when I trace route to one of the addresses from the /26 the trace completes but returns the IP of the DHCP interface as the hop just before the destination IP. This information is wrong. It should be the IP of the interface the trace uses. How do I fix this??


Thanks

Joe

Please ? can someone help?

Can you post the 2 traceroutes and show us what is wrong with them?

Sam

Thank you very much for your reply. I will post trace rts but I need to be off my network to show you.

Essectially what happens is that the traffic is going to interface 64.156.x.x but in trace rt it shows it went to interface 67.x.x.x it actually completes to address 64.156.x.70 but why does Mikrotik report it went through the wrong interface? one that actually gets it address via dhcp???

thanks

Joe

Here is trace route.

Router at hop 16 is connected to my Mikrotik, but not the interface that shows up in the trace. The IP of the connected interface is 64.xxx.xxx.xxx

The next hop is also a Mikrotik with the same problem. The interface that shows up in the trace is not the interface that is connected to the router in hop 17 (this router also has an interface that has DHCP client enabled)

the information that is returned in the trace route is the information that is assigned via dhcp on a different interface.

the packets are being routed OK since it does reach it's destination 8.xxx.xxx.14

1 2 ms 1 ms <1 ms 192.168.250.1
2 6 ms 8 ms 5 ms 10.156.192.1
3 6 ms 5 ms 7 ms 68.86.105.221
4 10 ms 8 ms 8 ms 68.86.103.29
5 8 ms 7 ms 9 ms 68.86.103.146
6 7 ms 7 ms 8 ms 12.124.158.17
7 32 ms 43 ms 32 ms gbr1-p60.dvmco.ip.att.net [12.123.36.138]
8 33 ms 33 ms 34 ms gbr1-p60.la2ca.ip.att.net [12.122.1.29]
9 35 ms 34 ms 35 ms tbr2-p013301.sffca.ip.att.net [12.122.12.133]
10 32 ms 32 ms 33 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
11 33 ms 33 ms 34 ms att-gw.sea.level3.net [192.205.32.206]
12 33 ms 33 ms 34 ms ae-1-54.bbr2.SanJose1.Level3.net [4.68.123.97]
13 55 ms 55 ms 56 ms ae-0-0.bbr2.Denver1.Level3.net [64.159.1.114]
14 55 ms 55 ms 57 ms so-9-0.hsa2.Denver1.Level3.net [4.68.113.50]
15 55 ms 60 ms 55 ms clearreach.fe.level3.net [63.211.230.114]
16 55 ms 55 ms 67 ms 63.214.44.238
17 64 ms 62 ms 63 ms c-67-xxx-xxx-188.hsd1.xxxxxxxxxxx.net [xx.xxx.xx.xx]
18 127 ms 95 ms 86 ms c-67-xxx-xxx-243.hsd1.xxxxxxxxx.x.net [xx.xxx.xx.xx]
19 128 ms 127 ms 125 ms 8.xxx.xxx.14



Trace complete.

How do I make it show the information about the actual interface that the traffic is using.

Thanks

Joe

Can someone tell me how to change how my router identifies it self??

No matter what route a packet takes through my router, the router identifies it self as the interface that has dhcp client enabled.

Are your problem solved? caz i am facing the same situation. From outside i am getting extra hop before my mikrotik. but if i traceroute from the same network it's ok. any solution from any one?

I have this problem too.And when i ping client, who have ip from another subnet and computer is down, i have "reply from xx.xx.xx.xx TTL expired" but xx.xx.xx.xx isnt registred anywhere on router.it`s client ip....

So no reply from MT support. and several people have the same issue.

My issue, specifically is no matter what interface I traverse with a trace route the mikrotik returns the information that it got via dhcp on another interface.

Joe

I am not sure if it's related but I seem to have a simmilar problem using two gateways.

It seems that the way MT manages the two gateways connections to clients is wrong. I'm not using DHCP though static on both WAN interfaces.

I ahve the same issue here :/

please don't use 7 year old topics and open your own one

This thread is old but deserves an answer for the record.

When the ttl counts down to zero the reply gets it's address from the interface leaving the router.
So if a router has an interface A and B, and if the traceroute enters the router on interface A
but the route back to the traceroute source is through interface B the reply will have interface
B's address on it. AKA asymmetrical routing.