|
hmmm i am only backing up the checkpoint config because
i drop it on another machine as a warm spare (i haven't changed the MAC
addresses on the second machine to match the first so don't want to overwrite
these scripts)... but if you are having problems perhaps it doesn't matter
whether the script names are the same as the interface. maybe try
ifcfg-eth2-2 for the script name, that way the scripts that loop through might
hopefully still execute as I think it uses the mask ifcfg-*...
Damo
When I perform a backup, the eth2:*
entries are backed up, but will not actually unzip, like they are
corrupt.
Do you get this Damo?
sure does.
Just one other question, should the
Device="eth2" line be changed to, for example, eth2:1?
Andrew
yep. you need to add them to
/etc/sysconfig/network-scripts. just copy the existing ifcfg-eth2
file to the new names ifcfg-eth2:1 and 2 and edit the file according to
your requirements.
hth
Damo
After I add aliases, they don't
survive a reboot.
(Running
SecurePlatform)
I'm using the command
ifconfig eth2:1
192.168.2.1
ifconfig eth2:2
192.168.3.1
Should I be adding these to a file
somewhere instead of just adding via command line?
Regards,
Andrew
>Hmmmm thats weird
because I am using colons in mine and while they do not show
>up in the interfaces section
of the config, or the GUI, routing and traffic
>to/from them do appear to
work fine...
>Damo
>I don't know about the others on the list, but we ran into an
issue
>using colons for virtual interface names with FP3
Secureplatform.
>Apparently starting with FP3, colons are no
longer supported in
>interface names. Check Point has confirmed
this. Apparently it doesn't
>matter because the names of virtual
interfaces can be whatever you want
>them to be in the
interfaces tab.
>
>Frank
>
************************************************************
The information contained in this email is confidential and
may be legally privileged. If the reader of this message is
not the intended recipient you are hereby notified that any
use, dissemination, distribution, or reproduction of this
message is prohibited. If you have received this message in
error please notify the sender and delete all copies of this
message including any attachments it may contain.
The email or its content does not necessarily represent the
views of the company.
************************************************************
|
************************************************************
The information contained in this email is confidential and
may be legally privileged. If the reader of this message is
not the intended recipient you are hereby notified that any
use, dissemination, distribution, or reproduction of this
message is prohibited. If you have received this message in
error please notify the sender and delete all copies of this
message including any attachments it may contain.
The email or its content does not necessarily represent the
views of the company.
************************************************************
|
************************************************************
The information contained in this email is confidential and
may be legally privileged. If the reader of this message is
not the intended recipient you are hereby notified that any
use, dissemination, distribution, or reproduction of this
message is prohibited. If you have received this message in
error please notify the sender and delete all copies of this
message including any attachments it may contain.
The email or its content does not necessarily represent the
views of the company.
************************************************************
|
|