If i am phisically logged the behavior are like to be the same. Em sex, 23 de nov de 2018 às 11:09, Luciano Andress Martini <analistau...@gmail.com> escreveu: > > Thank you Greg i would not like to use NetworkManager, i just tried it > because all the other ways that i tried did not worked in new Debian > Versions, after a fresh install so i am searching for a correct way of > doing things.. (i read documentation, but maybe i am missing > something) > > ifdown and ifup work partially instead of changing the ip, and it is > adding a new ip to the interface. > > service networking restart - just brokes the network connection. > Em sex, 23 de nov de 2018 às 11:02, Greg Wooledge > <wool...@eeg.ccf.org> escreveu: > > > > On Fri, Nov 23, 2018 at 10:31:28AM -0200, Luciano Andress Martini wrote: > > > Then I edited /etc/network/interfaces and restart the system, to see > > > if the ip was changed. And yes, it worked. So this file is still being > > > used in some way - humm that seems to be the correct place to > > > configure my interface isn't? > > > > /etc/network/interfaces is the primary, supported means of configuring > > network interfaces in Debian. It's the best choice for standard server > > and workstation setups. > > > > Network-Manager may also be installed (it's optional). As you've already > > seen, it is installed when choosing a "desktop environment" during the > > Debian installation, and skipped if no DE is chosen. N-M is apparently > > the tool of choice for configuring wireless interfaces on laptops. > > > > Interfaces that are configured in /e/n/i are skipped by N-M. Thus, > > you could think of it as "/e/n/i has priority, and N-M gets whatever > > /e/n/i didn't get". > > > > Then there's some bizarre systemd network interface thing. It's not > > used by default in Debian. I can't imagine anyone ever using it. > > You can simply ignore it. > > > > > -- > Luciano Andress Martini - Analista UNIX
-- Luciano Andress Martini - Analista UNIX