Subject: bin/2670: Can't get aliasese out of ifconfig?
To: None <gnats-bugs@NetBSD.ORG>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
List: netbsd-bugs
Date: 08/01/1996 16:56:53
>Number:         2670
>Category:       bin
>Synopsis:       Can't get aliasese out of ifconfig?
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Aug  1 20:05:03 1996
>Originator:     Jonathan Stone
>Release:        1.2_BETA
System: NetBSD Cup.DSG.Stanford.EDU 1.2_BETA NetBSD 1.2_BETA (DSG) #47: Mon Jul 29 12:05:57 PDT 1996 jonathan@Cup.DSG.Stanford.EDU:/aga/n1/src/NetBSD/IP-PLUS/src/sys/arch/i386/compile/DSG i386


ifconfig supports adding aliases (multiple addresses within a single
protocol family) to interfaces. However, it has no way to show such
aliases. One can find aliases by using netstat -r and looking for
non-host routes out the interface in question.

However, that's not an exact way to find aliases. I don't see how
to distinguish routes caused by aliases from routes added qua routes.

There's also a philosophical issue. I think the tool used to add an
alias to an interface should also be capable of displaying the
aliases.  ifconfig has historically been both the tool to change
interfaces and to show interface state (unlike, say, netstat -r and route.)
Interface aliases seem to break that model; I'd like to see that fixed.


Confiugre an alias, or several aliases, by hand (rather than in a script.)
Forget which addresses were aliases.


Patch ifconfig to find all addresses in an interface and report
them, rather than just the primary one.