2nd IP address on an interface

[Tom H]

On Thu, Aug 28, 2014 at 8:32 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>
> # ip addr show
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group
> default
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UNKNOWN group default qlen 1000
>     link/ether 02:56:02:01:f3:b9 brd ff:ff:ff:ff:ff:ff
>     inet 208.83.67.163/28 brd 208.83.67.175 scope global eth0
>     inet 208.83.67.164/28 brd 208.83.67.175 scope global secondary eth0
>     inet6 fe80::56:2ff:fe01:f3b9/64 scope link
>        valid_lft forever preferred_lft forever
>
> you are right. ifconfig USE to be able to do this, but now it is just a
> shell? over ip and so...
>
> So now to undo a lot of changes and see if I can get back to everything
> working.

ip (and ss, bridge, tc, and other iproute binaries) and ifconfig (and
route, netstat, brctl, ... and other net-tools and bridge-utils
binaries) use different kernel interfaces.

AIUI, the ifconfig interface is deprecated but kept for backward compatibility.