Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #201420 > unrolled thread

Migrating Debian installation to a new motherboard

Started bylocal10 <local10@tutanota.com>
First post2018-10-18 23:40 +0200
Last post2018-10-20 00:50 +0200
Articles 20 on this page of 41 — 14 participants

Back to article view | Back to linux.debian.user


Contents

  Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-18 23:40 +0200
    Re: Migrating Debian installation to a new motherboard Felix Miata <mrmazda@earthlink.net> - 2018-10-19 00:50 +0200
      Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-19 01:20 +0200
        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 17:40 +0100
        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 21:20 +0100
          Re: Migrating Debian installation to a new motherboard Dan Ritter <dsr@randomstring.org> - 2018-10-31 23:10 +0100
            Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-10-31 23:50 +0100
              Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 00:40 +0100
                Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 15:20 +0100
                  Re: Migrating Debian installation to a new motherboard Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-11-01 15:20 +0100
                    Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 17:20 +0100
                      Re: Migrating Debian installation to a new motherboard Dan Ritter <dsr@randomstring.org> - 2018-11-01 17:20 +0100
                        Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 17:50 +0100
                          Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 19:00 +0100
                            [SOLVED] Re: Migrating Debian installation to a new motherboard local10 <local10@tutanota.com> - 2018-11-01 19:30 +0100
                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Brian <ad44@cityscape.co.uk> - 2018-11-01 20:10 +0100
                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-02 03:30 +0100
                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-02 04:20 +0100
                                  Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-02 05:00 +0100
                                  Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-02 12:10 +0100
                                    Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 02:30 +0100
                                      Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-03 04:20 +0100
                                        Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 05:00 +0100
                                          Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-03 07:10 +0100
                                            Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-04 16:30 +0100
                                              Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Christensen <dpchrist@holgerdanske.com> - 2018-11-05 01:50 +0100
                                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard David Wright <deblis@lionunicorn.co.uk> - 2018-11-05 16:20 +0100
                                                Re: [SOLVED] Re: Migrating Debian installation to a new motherboard Celejar <celejar@gmail.com> - 2018-11-05 19:50 +0100
                            Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-02 08:30 +0100
                              Re: Migrating Debian installation to a new motherboard Felix Miata <mrmazda@earthlink.net> - 2018-11-02 08:40 +0100
                                Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-02 09:00 +0100
                                  Re: Migrating Debian installation to a new motherboard Curt <curty@free.fr> - 2018-11-02 10:00 +0100
                                  Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-02 12:20 +0100
                                    Re: Migrating Debian installation to a new motherboard mick crane <mick.crane@gmail.com> - 2018-11-03 03:00 +0100
                                      Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-03 12:50 +0100
                                        Re: Migrating Debian installation to a new motherboard Curt <curty@free.fr> - 2018-11-03 18:30 +0100
                                          Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-03 19:10 +0100
                              Re: Migrating Debian installation to a new motherboard Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-11-03 05:10 +0100
                      Re: Migrating Debian installation to a new motherboard Michael Stone <mstone@debian.org> - 2018-11-01 19:00 +0100
    Re: Migrating Debian installation to a new motherboard Patrick Bartek <nemommxiv@gmail.com> - 2018-10-19 18:50 +0200
    Re: Migrating Debian installation to a new motherboard songbird <songbird@anthive.com> - 2018-10-20 00:50 +0200

Page 1 of 3  [1] 2 3  Next page →


#201420 — Migrating Debian installation to a new motherboard

Fromlocal10 <local10@tutanota.com>
Date2018-10-18 23:40 +0200
SubjectMigrating Debian installation to a new motherboard
Message-ID<wKobn-2Qi-1@gated-at.bofh.it>
Hi,

Am looking for an easy way to move my Debian PC to a new motherboard, that is without reinstalling all the packages and config settings. All the hardware with the exception of the motherboard will remain the same, I have a spare hard drive, the same model as my working HD, which I can use as a setup area if needed. I did a similar migration with success some years back and used the "Shockingly easy server upgrade" writeup from Debian Planet as guide, which was available at http://www.debianplanet.org/node.php?id=875 <http://www.debianplanet.org/node.php?id=875> but it's no longer there and I can't find it.

Any ideas? Thanks

[toc] | [next] | [standalone]


#201421

FromFelix Miata <mrmazda@earthlink.net>
Date2018-10-19 00:50 +0200
Message-ID<wKph7-3rv-1@gated-at.bofh.it>
In reply to#201420
local10 composed on 2018-10-18 23:36 (UTC+0200):

> Am looking for an easy way to move my Debian PC to a new motherboard, that is without
> reinstalling all the packages and config settings. All the hardware with the exception of the
> motherboard will remain the same, I have a spare hard drive, the same model as my working HD,
> which I can use as a setup area if needed. I did a similar migration with success some years
> back and used the "Shockingly easy server upgrade" writeup from Debian Planet as guide, which
> was available at http://www.debianplanet.org/node.php?id=875
> <http://www.debianplanet.org/node.php?id=875> but it's no longer there and I can't find it.

https://web.archive.org/web/20060924185146/http://www.debianplanet.org/node.php?id=875

Just how old is the old motherboard? What model? Has it a UEFI BIOS?

Just how new is the new motherboard? What model?

I do a relative lot of cloning and moving disks among PCs. By keeping the old HD, there could be
little to do but reconfigure networking for the change in MAC address, if the NIC is a
motherboard component, and if not, nothing to do. Having the extra HD you could safely test by
cloning first and using the clone.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]


#201422

Fromlocal10 <local10@tutanota.com>
Date2018-10-19 01:20 +0200
Message-ID<wKpK9-3QR-1@gated-at.bofh.it>
In reply to#201421
Oct 18, 2018, 6:42 PM by mrmazda@earthlink.net:

> https://web.archive.org/web/20060924185146/http://www.debianplanet.org/node.php?id=875 <https://web.archive.org/web/20060924185146/http://www.debianplanet.org/node.php?id=875>
>

Ah, thanks, appreciate it.


> Just how old is the old motherboard? What model? Has it a UEFI BIOS?
>
> Just how new is the new motherboard? What model?
>

I will be moving a Debian Buster system from GigaByte GA-MA785GT-UD3H to Gigabyte GA-78LMT-USB3 rev6.0 The later mb I believe does have a UEFI BIOS.

Thanks

[toc] | [prev] | [next] | [standalone]


#201944

Fromlocal10 <local10@tutanota.com>
Date2018-10-31 17:40 +0100
Message-ID<wP1Hb-63Y-1@gated-at.bofh.it>
In reply to#201422

[Multipart message — attachments visible in raw view] — view raw

> Oct 18, 2018, 6:42 PM by > mrmazda@earthlink.net <mailto:mrmazda@earthlink.net>> :
>
>>> By keeping the old HD, there could be 
>>> little to do but reconfigure networking for the change in MAC address, if the NIC is a 
>>> motherboard component







How did you reconfigure the MAC address after the migration? I'm gettig "network is unreachable " even for local IPs so I guess I'll need to do that too. Thanks

[toc] | [prev] | [next] | [standalone]


#201952

Fromlocal10 <local10@tutanota.com>
Date2018-10-31 21:20 +0100
Message-ID<wP585-8a0-1@gated-at.bofh.it>
In reply to#201422

[Multipart message — attachments visible in raw view] — view raw


31. Oct 2018 12:38 by local10@tutanota.com <mailto:local10@tutanota.com>:


>     
>> Oct 18, 2018, 6:42 PM by >> mrmazda@earthlink.net <mailto:mrmazda@earthlink.net>>> :
>>
>>>> By keeping the old HD, there could be 
>>>> little to do but reconfigure networking for the change in MAC address, if the NIC is a 
>>>> motherboard component
>
>
>
>
>
>
>
> How did you reconfigure the MAC address after the migration? I'm gettig "network is unreachable " even for local IPs so I guess I'll need to do that too. Thanks
>







More info:

1. I'm runnig Buster

2. Motherboard NIC is Realtec RTL8111

3. Dont have any files in /etc/udev/rules.d/




Thanks

[toc] | [prev] | [next] | [standalone]


#201955

FromDan Ritter <dsr@randomstring.org>
Date2018-10-31 23:10 +0100
Message-ID<wP6Qy-Md-11@gated-at.bofh.it>
In reply to#201952
On Wed, Oct 31, 2018 at 09:10:06PM +0100, local10 wrote:
> >
> > How did you reconfigure the MAC address after the migration? I'm gettig "network is unreachable " even for local IPs so I guess I'll need to do that too. Thanks
> >
> 
> 1. I'm runnig Buster
> 
> 2. Motherboard NIC is Realtec RTL8111
> 
> 3. Dont have any files in /etc/udev/rules.d/

Can you show us the output of 
ip -l

and 

ip -r

?

-dsr-

[toc] | [prev] | [next] | [standalone]


#201957

Fromlocal10 <local10@tutanota.com>
Date2018-10-31 23:50 +0100
Message-ID<wP7tf-103-7@gated-at.bofh.it>
In reply to#201955

[Multipart message — attachments visible in raw view] — view raw

31. Oct 2018 18:05 by dsr@randomstring.org <mailto:dsr@randomstring.org>:

>
> Can you show us the output of 
> ip -l
>
> and 
>
> ip -r
>
> ?
>
> -dsr-







Both "ip -l" and "ip -r" return the same output  as "ip --help". Something is missing, pwrhaps? Thanks

[toc] | [prev] | [next] | [standalone]


#201959

FromMichael Stone <mstone@debian.org>
Date2018-11-01 00:40 +0100
Message-ID<wP8fD-1uG-1@gated-at.bofh.it>
In reply to#201957
On Wed, Oct 31, 2018 at 11:48:47PM +0100, local10 wrote:
>31. Oct 2018 18:05 by dsr@randomstring.org:
>
>
>    Can you show us the output of
>    ip -l
>
>    and
>
>    ip -r
>
>    ?
>
>    -dsr-
>
>
>
>Both "ip -l" and "ip -r" return the same output  as "ip --help". Something is
>missing, pwrhaps? Thanks

There shouldn't be a -

"ip a" is probabably more interesting than ip l.

[toc] | [prev] | [next] | [standalone]


#201963

Fromlocal10 <local10@tutanota.com>
Date2018-11-01 15:20 +0100
Message-ID<wPlZf-1lf-1@gated-at.bofh.it>
In reply to#201959

[Multipart message — attachments visible in raw view] — view raw


31. Oct 2018 19:37 by mstone@debian.org <mailto:mstone@debian.org>:

> There shouldn't be a -
>
> "ip a" is probabably more interesting than ip l.




"ip a" shows two interfaces:

1. lo

...

2. enp3s0 (broadcast, multicast, up,...)

    link/ether "address here"

    inet6 "address here"/64 scope link noprefixroute

         valid-lft forever preferred-lft forefer




Note that the 2nd interface is enp3s0 not enp2s0 as I have  in /etc/network/interfaces. This, as I understnd it, is due to the motherboard migration (I replaced the mb in my Buster PC, the system booted and seems to work fine, except for the networking).




Sorry for typos, posting from my phone. Thanks

 

[toc] | [prev] | [next] | [standalone]


#201964

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2018-11-01 15:20 +0100
Message-ID<wPlZf-1lf-9@gated-at.bofh.it>
In reply to#201963
Le 01/11/2018 à 15:10, local10 a écrit :
> 
> Note that the 2nd interface is enp3s0 not enp2s0 as I have  in /etc/network/interfaces. This, as I understnd it, is due to the motherboard migration (I replaced the mb in my Buster PC, the system booted and seems to work fine, except for the networking).

All you should need to do is update the interface name in 
/etc/network/interfaces.

[toc] | [prev] | [next] | [standalone]


#201969

Fromlocal10 <local10@tutanota.com>
Date2018-11-01 17:20 +0100
Message-ID<wPnRn-2rX-1@gated-at.bofh.it>
In reply to#201964

[Multipart message — attachments visible in raw view] — view raw

1. Nov 2018 10:18 by pascal@plouf.fr.eu.org <mailto:pascal@plouf.fr.eu.org>:


> Le 01/11/2018 à 15:10, local10 a écrit :
>>
>> Note that the 2nd interface is enp3s0 not enp2s0 as I have  in /etc/network/interfaces. This, as I understnd it, is due to the motherboard migration (I replaced the mb in my Buster PC, the system booted and seems to work fine, except for the networking).
>
> All you should need to do is update the interface name in /etc/network/interfaces.




Changed enp2s0 in /etc/network/interfaces to enp3s0, rebooted, still getting "Network is unreachable". Someone in this thread (

 http://debian.2.n7.nabble.com/Migrating-Debian-installation-to-a-new-motherboard-td4403474.html <http://debian.2.n7.nabble.com/Migrating-Debian-installation-to-a-new-motherboard-td4403474.html> ) mentioned that the MAC address needs to be changed to reflect the new NIC MAC address on the new mb. Not sure how to do that, I looked but what I found does not apply well to Debian.




Regards,

[toc] | [prev] | [next] | [standalone]


#201970

FromDan Ritter <dsr@randomstring.org>
Date2018-11-01 17:20 +0100
Message-ID<wPnRn-2rX-7@gated-at.bofh.it>
In reply to#201969
On Thu, Nov 01, 2018 at 05:12:35PM +0100, local10 wrote:
> 1. Nov 2018 10:18 by pascal@plouf.fr.eu.org <mailto:pascal@plouf.fr.eu.org>:
> 
> 
> > Le 01/11/2018 à 15:10, local10 a écrit :
> >>
> >> Note that the 2nd interface is enp3s0 not enp2s0 as I have  in /etc/network/interfaces. This, as I understnd it, is due to the motherboard migration (I replaced the mb in my Buster PC, the system booted and seems to work fine, except for the networking).
> >
> > All you should need to do is update the interface name in /etc/network/interfaces.
> 
> 
> 
> 
> Changed enp2s0 in /etc/network/interfaces to enp3s0, rebooted, still getting "Network is unreachable". Someone in this thread (
> 
>  http://debian.2.n7.nabble.com/Migrating-Debian-installation-to-a-new-motherboard-td4403474.html <http://debian.2.n7.nabble.com/Migrating-Debian-installation-to-a-new-motherboard-td4403474.html> ) mentioned that the MAC address needs to be changed to reflect the new NIC MAC address on the new mb. Not sure how to do that, I looked but what I found does not apply well to Debian.
> 

OK, now try 
ip l

Look for enp3s0 and see if it's up or down. Up is good. Down
probably means a bad ethernet cable -- or maybe it just isn't
plugged in properly on one end or the other.

-dsr-

[toc] | [prev] | [next] | [standalone]


#201971

Fromlocal10 <local10@tutanota.com>
Date2018-11-01 17:50 +0100
Message-ID<wPokp-2Bc-3@gated-at.bofh.it>
In reply to#201970

[Multipart message — attachments visible in raw view] — view raw

1. Nov 2018 12:17 by dsr@randomstring.org <mailto:dsr@randomstring.org>:


>> OK, now try 
>>
> ip l
>
> Look for enp3s0 and see if it's up or down. Up is good. Down
> probably means a bad ethernet cable -- or maybe it just isn't
> plugged in properly on one end or the other.




 Under enp3so I see only BROADCAST and MULTICAST, no UP or DOWN. Thanks

[toc] | [prev] | [next] | [standalone]


#201973

FromMichael Stone <mstone@debian.org>
Date2018-11-01 19:00 +0100
Message-ID<wPpq9-3cz-9@gated-at.bofh.it>
In reply to#201971
On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote:
> Under enp3so I see only BROADCAST and MULTICAST, no UP or DOWN. Thanks

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".

[toc] | [prev] | [next] | [standalone]


#201974 — [SOLVED] Re: Migrating Debian installation to a new motherboard

Fromlocal10 <local10@tutanota.com>
Date2018-11-01 19:30 +0100
Subject[SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPpTc-3B7-3@gated-at.bofh.it>
In reply to#201973
Nov 1, 2018, 1:57 PM by mstone@debian.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.

[toc] | [prev] | [next] | [standalone]


#201975 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

FromBrian <ad44@cityscape.co.uk>
Date2018-11-01 20:10 +0100
SubjectRe: [SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPqvU-432-9@gated-at.bofh.it>
In reply to#201974
On Thu 01 Nov 2018 at 19:21:24 +0100, local10 wrote:

> Nov 1, 2018, 1:57 PM by mstone@debian.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.

I've done that myself - changing a parameter on one line but not on
another. Well done for listening to and exploring the advice you were
given.

-- 
Brian.
 

[toc] | [prev] | [next] | [standalone]


#201978 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2018-11-02 03:30 +0100
SubjectRe: [SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPxnH-7Zl-3@gated-at.bofh.it>
In reply to#201974
local10 <local10@tutanota.com> writes:

> Nov 1, 2018, 1:57 PM by mstone@debian.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).

[toc] | [prev] | [next] | [standalone]


#201979 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2018-11-02 04:20 +0100
SubjectRe: [SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPya5-8y-1@gated-at.bofh.it>
In reply to#201978
On Thu 01 Nov 2018 at 20:03:05 (-0600), Joe Pfeiffer wrote:
> local10 <local10@tutanota.com> writes:
> > Nov 1, 2018, 1:57 PM by mstone@debian.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
profile instead.

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.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#201981 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2018-11-02 05:00 +0100
SubjectRe: [SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPyMN-lv-5@gated-at.bofh.it>
In reply to#201979
David Wright <deblis@lionunicorn.co.uk> writes:

> On Thu 01 Nov 2018 at 20:03:05 (-0600), Joe Pfeiffer wrote:
>> local10 <local10@tutanota.com> writes:
>> > Nov 1, 2018, 1:57 PM by mstone@debian.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
> profile instead.
>
> 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.)

Though in my case my DHCP server is dnsmasq on another machine, which
happily associates hostnames with the IP addresses so my machines can
indeed find each other.

[toc] | [prev] | [next] | [standalone]


#201987 — Re: [SOLVED] Re: Migrating Debian installation to a new motherboard

FromMichael Stone <mstone@debian.org>
Date2018-11-02 12:10 +0100
SubjectRe: [SOLVED] Re: Migrating Debian installation to a new motherboard
Message-ID<wPFuV-4xi-17@gated-at.bofh.it>
In reply to#201979
On Thu, Nov 01, 2018 at 10:12:36PM -0500, David Wright wrote:
>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.)

If you do something strange on your network, the assumption is that 
you're responsible for updating it for new machines. It's not something 
that needs to be in a general guide.

[toc] | [prev] | [next] | [standalone]


Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user


csiph-web