Hello all, Thanks Mark. Your email set me on a new investigation path and I have been able to nut out the problem and resolve it.
Alas, there is no NetworkManager on my box: [root@til ~]# apt list --installed |grep -i network WARNING: apt does not have a stable CLI interface. Use with caution in scripts. glib-networking-common/testing,now 2.58.0-1 all [installed,automatic] glib-networking-services/testing,now 2.58.0-1 amd64 [installed,automatic] glib-networking/testing,now 2.58.0-1 amd64 [installed,automatic] libqt5network5/testing,now 5.11.2+dfsg-4 amd64 [installed,automatic] I'm running networking.service, which means that the commands that I was using should have had some effect as I understand it. Once this became clear to me, I power-recycled the whole system and network (which was a bit painful here for some folks which is why I was reluctant to take that step earlier), and started again. What I think happened is this: I entered the command: ip addr add 192.168.0.3 dev enp3s0 without the netmask. On checking what networking thought I'd done, it returned 192.168.0.3/32 as the ethernet's address, which was different to what I had in the config file, which was equivalent to /24. I tried to amend this with a following /24 version of the command, which looked like it was accepted. But subsequently the command to bring up the ethernet: ip link set enp3s0 up, did not, and would not work. It was only after I power-cycled the switch (along with everything else) that these two ip commands worked. So, it seems to me, that my mistake was to add the ethernet without a netmask, which let networking assign it I suppose, and that different one, the /32 which was lodged in the switch, prevented networking to bring up the network for this computer because of the conflicting netmasks (the assigned one, and the one in the /etc/interfaces config file), and hence different identities. Anyway, that's as I understand it at the moment, but I could be quite astray on details as well of course. Thanks again. ben On Sun, Nov 25, 2018, at 4:39 PM, Mark Trickett via luv-main wrote: > Hello Ben, > > On 11/24/18, Ben Nisenbaum via luv-main <[email protected]> wrote: > > Hello everyone, > > My problem is that I cannot get the ethernet card on the local network to > > get up. I'm new to debian after many years of red-hat/fedora. The machine: > > HP Compaq Elite 8300 SFF (Core i5). The system: debian buster (testing) > > > > Some information: > > > > [ben@til ~]$ systemctl status networking.service > > networking.service - Raise network interfaces > > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor > > preset: enabled) > > This tells me a lot. You have systemd, and I think NetworkManager. You > need to use those tools, not the command line, it will manage the > configuration files for you, it will overwrite any manual changes. > > I do not like NetworkManager, nor Systemd. I can tell NetworkManager > to ignore a particular ethernet interface successfully, then use ifup > and ifdown, but not for wi-fi. For that, there are the command line > tools, but there are several steps and coordinating the use of the > discovery and connection is not so trivial. > > Regards, > > Mark Trickett > _______________________________________________ > luv-main mailing list > [email protected] > https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
