This turned out well for me, editing /etc/networks/interfaces does seem to work just fine - I was basically criticizing the documentation, which has some gaps...
On 10/30/2014 10:52 PM, Chuck wrote:
I don't like the way NetworkManager interacts with Debian's default network configuration. I found it to always do crap like what you describe. I have switched to Wicd and do not plan on looking back. The only "down-side" is that it also has its own configuration files, /etc/wicd/, and therefore doesn't honor changes to files in /etc/network/. I'd be willing to evaluate any GUI tool that leverages Debian's existing configuration though.On Tue, 2014-10-21 at 14:16 -0400, M. Knisely wrote:I use multiple NICs on my laptop all the time. I have the onboard NIC and up to three additional USB NICs and as of yet have not experienced this issue. Each NIC gets a new name in NetworkManager for me. I have labled my USB NICs with the last 2 of their MAC so I can easily identify them. I am running Ubuntu, so there should be little difference from my experience to yours.If you make any reference to an interface in /etc/network/interfaces, NetworkManager then will exclude that device from any management so you don't have an issue with management overlap.Michael K. On Tue, Oct 21, 2014 at 12:21 PM, Mike <bellyacres@xxxxxxxxx <mailto:bellyacres@xxxxxxxxx>> wrote:On 10/21/2014 10:40 AM, Larry DiGioia wrote:Hi guys, I built a standard Debian machine on old hardware, for the purpose of running BandwidthD. It is all done and pretty much works great. But with a second NIC added in a slot (in addition to the one on the system board) - setting IP becomes a nightmare: I can play all day with those settings in the GUI tool in the upper-right corner. What I actually want is DHCP on the system board NIC and a static on the 3Com in the slot. If I manage to set it that way, it eventually makes both NICs the same, including the "custom" name that I set to tell them apart. Sometimes they are both DHCP, others they are both static. It just treats them as if there were only one. The only way I can really tell them apart is from the MACs. I checked documentation <https://www.debian.org/doc/manuals/debian-reference/ch05.en.html> and so on - and the short version of what that says is, "there is a modern way, and a legacy way..." and I just hate doing anything the legacy way - /etc/network/interfaces has basically nothing in it. But the modern way doesn't work. Yeah, I know, it also says: Note Do not use these automatic network configuration tools for servers. These are aimed primarily for mobile desktop users on laptops. What am I missing? How would you do it?PS: what language was this translated from anyway?!What is the new way? NetworkManager? 9 times out of 10 that piece just gets in my way. Yes, I know I'm old, stubborn, and set in my ways... I've tried over and over to use it, typically the result is epic FAIL. I think you answered your own question. Use /etc/networking/interfaces, legacy or not, you'd already be done with it, moving on. Mike
--
"On Planet D, everything is black and white.
If you get far enough away, it just looks grey."
Dev