On Wednesday 08 April 2015 10:10:33 dave wrote: > being very lazy I usually just use dhclient. > I only use ifconfig if dhclient doesn't work. ;-) > > Dave
ifconfig, to me is the hard way. Arcane syntax I have to look up every time. This Just Works the instant the machine has approximately booted. No monkey business waiting for NM or dhclient to think it over. If the machine is booted far enough to put a login requester on its own screen, the networking just works. I can issue thru an ssh -Y circuit, a "sudo reboot" to one of those machines from this easy chair, hit a ctl+d to close the existing session, start a ping to the machine, kill the ping on 1st response and login with another ssh -Y session, probably before it is 100% booted out there. Both of those machine will be pouinding on the hard drive after the login pops up, 45 seconds or more before they quiet down & start waiting for me to issue a command. At the end of the discussion, it is still whatever floats _Your_ boat. ;-) > On 04/08/2015 06:24 AM, Gene Heskett wrote: > > On Wednesday 08 April 2015 07:26:31 John Thornton wrote: > >> /etc/network/interfaces contains two lines: > >> auto lo > >> iface lo inet loopback > >> > >> JT > > > > Luverly, just luverly I say. NetworkManager has been there and > > destroyed the reference copy. Here is the outline of how mine Just > > Works(TM) > > > > Expunge NM and be done with it. > > > > Here is the interfaces file from this machine, with some addresses > > hidden. > > --------------------- > > # This file describes the network interfaces available on your > > system # and how to activate them. For more information, see > > interfaces(5). # > > # list of interfaces to ayto activate > > auto lo eth0 > > # interface lo > > iface lo inet loopback > > address 127.0.0.1 > > netmask 255.0.0.0 > > # interface eth0 > > iface eth0 inet static > > address 192.168.xx.3 > > netmask 255.255.255.0 > > gateway 192.168.xx.1 > > ------------------------ > > (the eth0 address in each machines interfaces file is of course that > > machines address. All completely arbitrary, set by you on each > > machine on ypur local network. > > > > /etc/resolv.conf is a real file, not a link, and contains one line: > > nameserver (same ipv4 addr as gateway above, let the router sort dns > > query stuff) > > ----------------- > > If not using dhcp for obtaining a local address (I've yet to figure > > out how to do local dns searches by names when dhcp obtained the > > address, probably my stupidity, but there it is) and are using an > > /etc/hosts file for local dns resolution, it should resemble this on > > every machine on your local network(add more machines as required, > > up to 254 IIRC): > > > > gene@coyote:/opt/nitros9$ cat /etc/hosts > > 127.0.0.1 localhost > > 192.168.xx.1 router.coyote.den router > > 192.168.xx.3 coyote.coyote.den coyote > > 192.168.xx.4 shop.coyote.den shop > > 192.168.xx.5 lathe.coyote.den lathe > > 192.168.xx.6 lappy.coyote.den lappy > > > > # The following lines are desirable for IPv6 capable hosts > > > > ::1 localhost ip6-localhost ip6-loopback > > > > ff02::1 ip6-allnodes > > ff02::2 ip6-allrouters > > -------------- > > > > All hostnames above were set once by (example for this machine) > > $hostname coyote.coyote.den > > etc etc for the other machines when they were installed. > > > > And you just did me a favor John, my lappy could not login the last > > time I plugged it in, its line was "lappy.coyote,den". Error now > > obvious. > > > > I suspect it will Just Work the next time I power it up. If the > > battery isn't crowbared by now, its the OEM battery yet, and about > > 13 years old. :( > > > > Perhaps not the way you were doing it, but "It works for me" :) > > > >> On 4/8/2015 6:17 AM, Andreas Pettersson wrote: > >>> You would prob. need to activate the card in the config. > >>> You will find the config file under /etc/network/interfaces > >>> > >>> Prob. is the pci card on eth1 instead of eth0 - even if its > >>> deactivated in the bios. > >>> it usually "adresses" it self, just not useable. > >>> > >>> // A > >>> > >>> John Thornton skrev den 2015-04-08 13:12: > >>>> I have a Debian Wheezy install on a computer down here in the > >>>> Beer Cave and the other day the power blinked and I lost network > >>>> connectivity on that computer. After some fumbling around I see > >>>> that I had a red light on the router for that line instead of a > >>>> green one. So I put a network card in the PCI slot and plugged > >>>> that in. Now I have a green light on the router. I went to the > >>>> bios and turned off the Ethernet on the motherboard. I still > >>>> don't have a connection to the LAN from that computer. Any clues > >>>> as to what I need to do? > >>>> > >>>> Thanks > >>>> JT Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
