Re: set srcIP for ICMP replies, or for locally sourced connections?



Phil Begriffenfeldt wrote:
I'd like to block traffic to my routers from outside my network; but still to allow my routers to traceroute/ping to hosts outside my

To address the ICMP requirements for the return path of a traceroute or ping, see my other response.

network; and reply to traceroutes sourced outside the network.

If the traceroute is inbound from a Windows host, ICMP echo requests will be used to carry out the traceroute. See my other response.

If the traceroute is from another Cisco device, UDP will be used to carry out the traceroute (as indicated by another post responder).

When I captured a Cisco traceroute, I noticed that the initial UDP source and destination port numbers were random, and that they were incremented with each and every packet sent.

Accommodating inbound traceroute from an external Cisco device appears to require very permissive ACLs.


Is there a way to force ICMP replies to come from a particular IP address? For example, something like "ip icmp source-interface loopback2", where the ICMP messages generated by my routers would come from a source IP that I can specify? That would help to hide interface IPs from casual miscreants.

Don't know of a means to deviate from the default behavior.


Alternatively, I could try to block all packets entering my network with destination IPs of my internal links. But that would block replies from simple outbound pings and traceroutes from router CLI sessions. If

Include layer 4 matching criteria in the ACEs (Accesses Control Entries) of your ACLs.

there were a way to bind locally-sourced ping and traceroute to a particular source IP on each router, then that would also be helpful.

The extended mode of both ping and traceroute, permit you to define the source IP address.


Perhaps blocking at the network edge is not productive, and I should be using Control Plane Policing for this? Router platform is mix of VXR and 3BXL.


--
Best Regards,
News Reader
.



Relevant Pages

  • Re: set srcIP for ICMP replies, or for locally sourced connections?
    ... I just performed a traceroute from a Windows XP host through my IPSec+ GRE VPN, and captured it with Wireshark to confirm my beliefs. ... The router that gets the packet with a TTL of 1 will reply with an ICMP TTL exceeded message. ... Extended ping permits you to specify the source IP address that will be used in the outbound ping, which then becomes the destination IP address in the reply packet. ... But that would block replies from simple outbound pings and traceroutes from router CLI sessions. ...
    (comp.dcom.sys.cisco)
  • Re: set srcIP for ICMP replies, or for locally sourced connections?
    ... Traceroute doesn't use ICMP, it sends udp packets on port 16667, ... will reply with an ICMP TTL exceeded message. ... simple outbound pings and traceroutes from router CLI sessions. ...
    (comp.dcom.sys.cisco)
  • Re: set srcIP for ICMP replies, or for locally sourced connections?
    ... I just performed a traceroute from a Windows XP host through my IPSec+ ... He said he wants to "allow my routers to traceroute/ping to hosts". ... will reply with an ICMP TTL exceeded message. ... simple outbound pings and traceroutes from router CLI sessions. ...
    (comp.dcom.sys.cisco)
  • Re: tcp_mtu_discover causes traceroute problems on aix 4.3.3
    ... > (because the traceroute fails). ... However, a severe misunderstanding is, that "Path MTU Discovery" ... Let's have a look on how PMTU discovery works. ... If a router is well behaved, i.e. it politefully obeys all the ...
    (comp.unix.aix)
  • Re: Strange web site loading/DNS problem
    ... If the site sends out packets of 1500 bytes, and there is a router between ... When I can't get to the site, I get the typical traceroute: ... I have also changed the DNS server info in my router, ...
    (microsoft.public.windows.server.dns)