/etc/init.d/networking does not start everything in /etc/network/interfaces
Greetings all;
32 bit Debian wheezy, updated at least daily.
This fact was brought to my attention because I needed a path to a router
I needed to do a hard reset on, and reconfigure to do my stuff, but my
normal home network isn't on the usual 192.168.1.1 class C, and a hard
reset puts the router back to the 1.1 address.
So in order to use eth1 as a path to this router, I have to do a separate
sudo ifconfig eth1 up
as a sudo service networking restart will not restart the second eth1
stanza in my interfaces file, starting only eth0.
Normally the interface is not even graced with a cat5 in the socket, and
ATM it is but the far end of 5 feet of cat5 is laying on the floor.
Is it possible to make this init.d/networking script start everything it
finds in the interfaces file?
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>
Reply to: