When I add the loopback IP as the gateway for the traceroute mark it says unreachable
On Thu, Oct 22, 2015 at 6:37 AM, Mike Hammett <[email protected]> wrote: > I haven't found a method of IP conservation I'm happy with while still > routing at each tower. If I have MPLS underneath and use tunnels > everywhere, I now have a bunch of IPs for tunnels between each PE to each > tower instead of just between each router. At some number of PEs, I'll have > more IPs in use there than if I just routed tower to tower. > > *shrugs* > > > > ----- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > ------------------------------ > *From: *"That One Guy /sarcasm" <[email protected]> > *To: *[email protected] > *Sent: *Thursday, October 22, 2015 1:40:02 AM > *Subject: *[AFMUG] still trying to get traceroute to reply from loopback > > > Im still working at getting traceroutes from any direction to reply from > the same IP, would prefer it be the loopback that is used for OSPF router > IDs too. There are two reasons, one is to conserver our ARIN allocation and > to not have our internal IP space visible to customers (we are using 172. > stuff) > > with mangle in the prerouting chain I can identify it by looking at ttl of > 1. > > I can set the action to increment by one and get it to forward up to the > next hop so the response of that and the second look duplicated. > > Ive tried marking the packet and setting the gateway to the loopback ip, > but it doesnt seem to work, depending on what i do it either continues to > go to the next hop or it just kills the traceroute. > > Im wondering if its got to do with the loopback being /32 or if its that > im stupid, probably a little of both. > > Where is butch at? > > -- > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. > > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
