File: alias.txt

package info (click to toggle)
linux 4.9.228-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 814,720 kB
  • sloc: ansic: 14,532,095; asm: 289,032; makefile: 35,316; perl: 27,556; sh: 17,027; python: 13,390; cpp: 6,103; yacc: 4,354; lex: 2,440; awk: 1,212; pascal: 231; lisp: 218; sed: 21
file content (40 lines) | stat: -rw-r--r-- 1,181 bytes parent folder | download | duplicates (26)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

IP-Aliasing:
============

IP-aliases are an obsolete way to manage multiple IP-addresses/masks
per interface. Newer tools such as iproute2 support multiple
address/prefixes per interface, but aliases are still supported
for backwards compatibility.

An alias is formed by adding a colon and a string when running ifconfig.
This string is usually numeric, but this is not a must.

o Alias creation.
  Alias creation is done by 'magic' interface naming: eg. to create a
  200.1.1.1 alias for eth0 ...
  
    # ifconfig eth0:0 200.1.1.1  etc,etc....
                   ~~ -> request alias #0 creation (if not yet exists) for eth0

    The corresponding route is also set up by this command. 
    Please note: The route always points to the base interface.
	

o Alias deletion.
  The alias is removed by shutting the alias down:

    # ifconfig eth0:0 down
                 ~~~~~~~~~~ -> will delete alias

  		   		   
o Alias (re-)configuring

  Aliases are not real devices, but programs should be able to configure and
  refer to them as usual (ifconfig, route, etc).


o Relationship with main device

  If the base device is shut down the added aliases will be deleted 
  too.