Neighbor command under the eigrp process will give you a ttl of 2. You can use that as a work around on 3945.

Would like to add that neighbor command need to be added on both routers as eigrp router stops listening on multicast address 224.0.0.10 once neighbor command is added.

This should resolve your issue as the device in the middle is decrementing the ttl by 1.

Router eigrp 1

neighbor x.x.x.x outgoing interface

You will need this on both routers. I hope this helps you.

Hi

Take in consideration that using neighbor command it will create unicast relationship, now if there is other router or others will be included in a future you could need to disable the split-horizon in order to avoid problems between the routers.

:-)

Julio - You are right that it may require disabling split horizon if more eigrp speaking routers are added out the same interface. Shouldn't have any negative impact as eigrp uses feasibility condition to prevent routing loops.

In my understanding other options would be to create a tunnel between 2 routers to bypass the filtering devices, but this defeats the purpose of going through that device in the first place. BGP peering can be created between these routers and then redistribute eigrp over BGP, this design over complicates the whole topology. May be you can think of something else in order to overcome this problem.

Hi Cofee@0400

I agree with you, the neighbor command could work and set the TTL to 2. I remember EIGRP usually set TTL to 2. 

Hi Mayra could you please try the configuration mentioned by Cofee, it should be: 

Edger router:

neighbor 172.21.48.1 G0/0

Internal router:

neighbor 172.21.48.2 G0/0

Assuming these IP addresses are able to communicate, It should be an option. 

I like the idea to use iBGP instead Eigrp and redistribute into EIGRP, there are other ways like configure a Proxy on the hosts.