I am trying to get a EoIP tunnel from a controller running 3.2.210 (local) to a controller running 18.104.22.168 (anchor). My client can connect and it seems to work briefly, but the connection dies every time the mobility keep-alive interval hits on the anchor. I have confirmed this with debugs.
Is there a way to disable mobility keep-alives in 4.1 code? Since keep-alives are not an option on the controller running 3.2, I am pretty sure this is the issue.
I am stuck with 3.2 code on my local controllers because I have some 4100s which only support up to 3.2.