Re: Specifying names for tap interfaces

[Roger Pau Monné <roger.pau%entel.upc.edu@localhost>]

On Wed, Jun 20, 2012 at 11:00 PM, Jean-Yves Migeon
<jeanyves.migeon%free.fr@localhost> wrote:
> IMHO this is not the right place to fix this. First, most firewalls out
> there support variables, like macros in pf.conf. IMHO adding more
> complexity to kernel for this is questionable.

Well this might be ok with firewalls, but it's not applicable to guest
interfaces, there's still the problem with persistent interfaces for
DomUs, which this doesn't solve.

> Instead of renaming your interface inside the config files, you alias it
> in kernel. Which is anyway a dubious construct because it will not
> survive a reboot... except if you edit a config file that sets up this
> aliasing for you. Ewww. Back to square one.

I don't think it will be so difficult/awkward to create an init config
file, like the ones that already exist for bridged/vlan interfaces,
that would set up the alternative name at boot time like
<ifconfig.altname.foo> or even <ifconfig.foo>.