Possible Bug? Default Keepalive Setting on EoIP Interface

Working on creating some scripts for deployment, currently working with an RB3011, running 6.40.4. In the terminal if I enter the command:

/interface eoip add name="eoip to ABC" mtu=1500 tunnel-id=30006 remote-address=xx.xx.xxx.xx

The interface is created but never shows the status of Running. If I manually create the interface it immediately shows a Running status. Looked a little deeper and discovered the manually created interface has no keepalive set, however the command line created interface has a keepalive defined. When I disable the keepalive, the status immediately changes to running.

Am I missing something? Don’t think this should be the default behavior.

With keepalive on, the interface will become running when it can contact the other side of the connection.
When you define a single side with keepalive it is not running, without keepalive it is running but of course it still is a black hole.
It can sometimes be convenient to have interfaces that are black holes to be not in the running state (e.g. when you use equal cost multipath or bonding),
but it really is your own choice and preference.

Thanks for the information, good to know.