On Sunday 13 December 2020 at 21:42:50, Simon Hobson wrote:
> Hendrik Boom <hend...@topoi.pooq.com> wrote:
> > I had to solve it by assigning new names to the interfaces (thus not eth0
> > or eth1) and modifying all the config files mentioning those interface
> > names (I found them with grep) to use the new names instead.
>
> Not for the OPs reason, but a long time ago I started to use "meaningful
> names" like ethext, ethint, and so on. Making it clearer in config files
> what each interface is.
Ironically enough, that is precisely what I have done on my own routers, which
have interfaces named "Internet", "Clients", "Phones", "PubServers" and
"PriServers".
I did that because by default they create VLAN interfaces called eth0.0,
eth0.1, eth0.2 etc, and so I used the rename facility in
/etc/network/interfaces to give them names which meant something to me.
> I think removing the need to remember something is better than being good
> at remembering it (which I'm not anyway !)
I completely agree with that, however in this case (wanting eth0 to be on the
motherboard and eth1/2 to be the PCI card), is close enough to "familiar" for
me not to get confused about it (once I get the machine to agree on the
names).
Antony.
--
I know I always wanted to be somebody, but I guess I should have been more
specific.
Please reply to the list;
please *don't* CC me.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
