IN fails to start after renaming "out" interface

[Dmitry@Rivermine]

For some reason if I rename "out" interface the IN appliance fails to start. Has this been posted somewhere before?

[PeterNic]

Dmitry,

I assume you have branched the IN gateway in order to rename its 'out' terminal.

1. Why did you have to do that? The IN gateway is intended as a ready-to-use type of appliance... while it is perfectly OK to branch it and create a different gateway based on it, in most cases this is not necessary. I just want to make sure you are branching it for the right reasons.

2. If you change the boundary of an appliance in some way -- rename a property or a terminal, for example -- you will also have to change the interior because it now needs to use the new names. For the IN gateway, most likely you will need to review the various scripts that configure the IP network, routing, NAT, etc., inside the IN gateway and adjust them to use the new name(s). All of these files reside in the /appliance directory on its boot volume.

#2 above applies for any appliance that you branch and modify.

Let me know if #1 or #2 helps.

Regards,
-- Peter