Re: [SOLVED] Re: Migrating Debian installation to a new motherboard
On Thu 01 Nov 2018 at 20:03:05 (-0600), Joe Pfeiffer wrote:
> local10 <email@example.com> writes:
> > Nov 1, 2018, 1:57 PM by firstname.lastname@example.org:
> >> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote:
> >> That means it's down. Note that you said enp3so above, that should
> >> be enp3s0 (zero); which did you put in interfaces? Also, there
> >> should be either "auto enp3s0" or "allow-hotplug enp3s0". Assuming
> >> that's all right, try manually running "ifup -v enp3s0".
> > That was it. I did have "allow-hotplug" but it was still pointing to enp2s0, not paying attention obviously. After changing "allow-hotplug enp3s0" the network came back, everything works.
> > So my experience indicates that it is quite possible to replace the
> > motherboard, stick the old hard disk in and the only change that's
> > required (in my case) was to change "/etc/network/interfaces" to
> > reflect the new interface name from enp2s0 to enp3s0 . No need to
> > change NIC MAC address.
> > Thanks to everyone who responded.
> For what it's worth, I'm running network-manager and my ethernet port
> (enp4s0 in my case) isn't listed in /etc/network/interfaces at all. All
> that's in there is lo (the loopback interface).
FWIW if it were listed in /e/n/i, then nm would not manage it, would it.
I expect you've got the interface name stored in nm's connection
BTW in a network set up like my own, the place where the MAC would be
relevant is in the DHCP server (here, the router) because that is how
the IP number is assigned. An unassigned MAC will get given an IP
address 192.168.1.200+, and it will conect to the Internet, but other
machines on the LAN would not recognise it. (Although the router can
hand out IP numbers, it doesn't run a nameserver.)