Hi all,
I want when the clients in my network run the Tracert command, they can’t see the internal hops(how many routers, Firewalls) of my LAN. they just see only the external hops. how can i do that with Mikrotik?
also i want to change the actual TTL and ping time values to our desire numbers like time=95 and TTL=20.for example when users issue the ping www.yahoo.com command, they see the time number equal 95 and TTL equal 20. how can i do that? please give me the Mikrotik commands that i can implement on my Mikrotik RouterOS.
any help would be appreciated. thanks in advanced.
Yes you can change the TTL using a command like that. The TTL field helps avoid routing loops so manually changing it should only be done with a full understanding of the potential impact.
ok CelticComms , but when i use above command, when ICMP packets from user’s pc reach to my router dropped, I want their ICMP packets only show routers that exist out of my network. in fact, the ICMP packet jump out of my network and does not show my internal router(s). what’s your suggestion?
Use a tunnel between customer point of acces and yor external gateway router. Or live wit the fact that they ca deduce your number of internal hops. That is what TTL was intended for by design.
Thanks for your post docmarius,
All i want is do the job only with change TTL parameters, no with other way like Tunneling. I want to know how can i hide my internal hops with TTL. one of my co-worker do the same thing in their network with Mikrotik, but he does not give the clue to me. when i run the tracert www.yahoo.com command, the first hop shown was the first external router. please give me Mikrotik command(s) to do that. any help would be appreciated.
Dear dosh,
With your suggestion, users cannot ping external hops. because my internal router(Mikrotik) drops any ICMP packets received from LAN(users). i want users be able to ping only external hops and all internal hops hidden to them. please give your suggestion.
Drop on input chain will drop only requests to the router itself. External requests are managed by the forward chain and will be passed from LAN to WAN. So the behavior will be as you want it.
And of course you can refine the rules to drop only requests that you do not want to appear using e.g. the interface and dst address fields.
With my suggestion, users cant ping only your routers and trace doesnt show internal routers because the firewall is in the input chain. they can ping external addresses.