I think the problem is this is in the output chain but part of an established connection do it doesn't go back through srcnat I tried marking the connection (new packets with ttl=1) to get it to flow that way, the filter catches it, but the ttl expired doesn't nat, I assume for the same reason I don't know if it can be cheated via some custom routing to mark the packet and add the source to an address list with a policy router for icmp type 10 via a loopback that NATs the packet. Seems convoluted though and probably heavy?
On Tue, Oct 6, 2015 at 1:54 PM, That One Guy /sarcasm < [email protected]> wrote: > no, just when it delivers a ttl expired > > On Tue, Oct 6, 2015 at 1:43 PM, Josh Luthman <[email protected]> > wrote: > >> Are you trying to set it so that every time the router pings something it >> comes from 1.2.3.4? >> >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> On Tue, Oct 6, 2015 at 2:31 PM, That One Guy /sarcasm < >> [email protected]> wrote: >> >>> 0 chain=output action=accept protocol=icmp icmp-options=11:0-255 >>> log=yes >>> log-prefix="icmp mangle" >>> >>> This is the traffic, I want it to always present as say 1.2.3.4, with it >>> being in theoutput chain, whats a guy got to do to control this? >>> >>> -- >>> 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. > -- 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.
