thank you this was very helpful.

On Mon, Jul 28, 2014 at 5:09 PM, Orion Poplawski <[email protected]>
wrote:

> On 07/28/2014 01:49 PM, Andrew Z wrote:
>
>> I havent figured out how to manage those files..
>> The original script creates dozens of aliases - one per destination, by
>> replacing first Xxx with 127. This makes it intuitive where alias
>> "points" to.
>> Now with each file having the same name (lo:<port>) imnot sure how to
>> manage
>> these aliases.
>>
>> I want to add, that I suspect that im missing something obvious and/or
>> just
>> dont understand how network stack works now.
>> Any help is very much appreciated, since all my information is from rhel
>> one
>> page guide , some blog and just trying to get aliases to work.
>>
>>
> Manually you could do:
>
> ip addr add 127.112.113.xxx dev lo
>
>
>  On Jul 28, 2014 10:40 AM, "Orion Poplawski" <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     On 07/28/2014 08:08 AM, Andrew Z wrote:
>>
>>         I have an apple os script, that creates an lo alias ( for example
>>         127.112.113)
>>         and then ssh -p xxxx 127.112.113 <rest of the command>
>>
>>         To begin with ifconfig doesn't work on creating aliases and
>> according
>>         to rhel
>>         docs I need to copy ethXxx files if I want to create these
>> aliases.
>>         Is there a better way,  than to copy files, to achieve the same?
>>
>>
>>     What's the concern with making a new ifcfg-* file to create the alias?
>>
>>     --
>>     Orion Poplawski
>>     Technical Manager 303-415-9701 x222 <tel:303-415-9701%20x222>
>>     NWRA, Boulder/CoRA Office             FAX: 303-415-9702 <tel:
>> 303-415-9702>
>>     3380 Mitchell Lane [email protected] <mailto:[email protected]>
>>     Boulder, CO 80301 http://www.nwra.com
>>
>>
>
> --
> Orion Poplawski
> Technical Manager                     303-415-9701 x222
> NWRA, Boulder/CoRA Office             FAX: 303-415-9702
> 3380 Mitchell Lane                       [email protected]
> Boulder, CO 80301                   http://www.nwra.com
>

Reply via email to