Migrate service and IP address from one pc to another, so that the other pc takes the place of the first but also retains its original IP
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I have a Cubieboard on 192.168.20.10 which serves as a DNS-server.
I also have now a new, somewhat bigger PC on 192.168.20.20 which is now hosting some services, but not DNS. I want to move the DNS server from x.x.x.10 to x.x.x.20, but have several IoT devices with hardcoded static settings.
Can I "copy" the DNS server to x.x.x.20 (would be trivial) and also move/assign the IP address x.x.x.10 to the x.x.x.20 board, so that it has has both IPs on the same interface, and power off the Cubieboard forever?
I'd also need all requests from the new PC still leave via the x.x.x.20 IP, except for the DNS replies, since they are made to the x.x.x.10 IP
A downtime of about 1 minute is acceptable.
Using DHCP on every device is not an option, also because Android 5.x has a bug in its DHCP client which causes disconnects on every DHCP refresh, and I refresh often.
ip migration
asked Nov 9 '17 at 17:26
Daniel F
16112
add a comment |Â
up vote
1
down vote
favorite
I have a Cubieboard on 192.168.20.10 which serves as a DNS-server.
I also have now a new, somewhat bigger PC on 192.168.20.20 which is now hosting some services, but not DNS. I want to move the DNS server from x.x.x.10 to x.x.x.20, but have several IoT devices with hardcoded static settings.
Can I "copy" the DNS server to x.x.x.20 (would be trivial) and also move/assign the IP address x.x.x.10 to the x.x.x.20 board, so that it has has both IPs on the same interface, and power off the Cubieboard forever?
I'd also need all requests from the new PC still leave via the x.x.x.20 IP, except for the DNS replies, since they are made to the x.x.x.10 IP
A downtime of about 1 minute is acceptable.
Using DHCP on every device is not an option, also because Android 5.x has a bug in its DHCP client which causes disconnects on every DHCP refresh, and I refresh often.
ip migration
asked Nov 9 '17 at 17:26
Daniel F
16112
1
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a Cubieboard on 192.168.20.10 which serves as a DNS-server.
I also have now a new, somewhat bigger PC on 192.168.20.20 which is now hosting some services, but not DNS. I want to move the DNS server from x.x.x.10 to x.x.x.20, but have several IoT devices with hardcoded static settings.
Can I "copy" the DNS server to x.x.x.20 (would be trivial) and also move/assign the IP address x.x.x.10 to the x.x.x.20 board, so that it has has both IPs on the same interface, and power off the Cubieboard forever?
I'd also need all requests from the new PC still leave via the x.x.x.20 IP, except for the DNS replies, since they are made to the x.x.x.10 IP
A downtime of about 1 minute is acceptable.
Using DHCP on every device is not an option, also because Android 5.x has a bug in its DHCP client which causes disconnects on every DHCP refresh, and I refresh often.
ip migration
asked Nov 9 '17 at 17:26
Daniel F
16112
I have a Cubieboard on 192.168.20.10 which serves as a DNS-server.
I also have now a new, somewhat bigger PC on 192.168.20.20 which is now hosting some services, but not DNS. I want to move the DNS server from x.x.x.10 to x.x.x.20, but have several IoT devices with hardcoded static settings.
Can I "copy" the DNS server to x.x.x.20 (would be trivial) and also move/assign the IP address x.x.x.10 to the x.x.x.20 board, so that it has has both IPs on the same interface, and power off the Cubieboard forever?
I'd also need all requests from the new PC still leave via the x.x.x.20 IP, except for the DNS replies, since they are made to the x.x.x.10 IP
A downtime of about 1 minute is acceptable.
Using DHCP on every device is not an option, also because Android 5.x has a bug in its DHCP client which causes disconnects on every DHCP refresh, and I refresh often.
ip migration
asked Nov 9 '17 at 17:26
Daniel F
16112
edited Nov 9 '17 at 18:08
asked Nov 9 '17 at 17:26
Daniel F
16112
asked Nov 9 '17 at 17:26
Daniel F
16112
asked Nov 9 '17 at 17:26
Daniel F
16112
16112
1
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04
add a comment |Â
1
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04
1
1
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict.
You can have DNS running on both hosts, and transition the hosts to use the new DNS server or, probably more wisely, transition the IoT devices to use DHCP with MAC Address reservations to give them static DHCP IP assignments and DNS Server settings. You can then use DHCP to cut DNS service from one host to the other seamlessly.
If the old device is going to be shut down and/or repurposed with a new IP Address, most devices (presumably including the new one) are capable of adding virtual interfaces (e. g. eth0 can also drive eth0:0 and eth0:1 each with their own IP stack). So once the old device is removed, you can add a new virtual interface on the old IP address, and have your DNS server listen on all (non-public-facing) interfaces.
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict.
You can have DNS running on both hosts, and transition the hosts to use the new DNS server or, probably more wisely, transition the IoT devices to use DHCP with MAC Address reservations to give them static DHCP IP assignments and DNS Server settings. You can then use DHCP to cut DNS service from one host to the other seamlessly.
If the old device is going to be shut down and/or repurposed with a new IP Address, most devices (presumably including the new one) are capable of adding virtual interfaces (e. g. eth0 can also drive eth0:0 and eth0:1 each with their own IP stack). So once the old device is removed, you can add a new virtual interface on the old IP address, and have your DNS server listen on all (non-public-facing) interfaces.
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
add a comment |Â
up vote
0
down vote
You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict.
You can have DNS running on both hosts, and transition the hosts to use the new DNS server or, probably more wisely, transition the IoT devices to use DHCP with MAC Address reservations to give them static DHCP IP assignments and DNS Server settings. You can then use DHCP to cut DNS service from one host to the other seamlessly.
If the old device is going to be shut down and/or repurposed with a new IP Address, most devices (presumably including the new one) are capable of adding virtual interfaces (e. g. eth0 can also drive eth0:0 and eth0:1 each with their own IP stack). So once the old device is removed, you can add a new virtual interface on the old IP address, and have your DNS server listen on all (non-public-facing) interfaces.
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict.
You can have DNS running on both hosts, and transition the hosts to use the new DNS server or, probably more wisely, transition the IoT devices to use DHCP with MAC Address reservations to give them static DHCP IP assignments and DNS Server settings. You can then use DHCP to cut DNS service from one host to the other seamlessly.
If the old device is going to be shut down and/or repurposed with a new IP Address, most devices (presumably including the new one) are capable of adding virtual interfaces (e. g. eth0 can also drive eth0:0 and eth0:1 each with their own IP stack). So once the old device is removed, you can add a new virtual interface on the old IP address, and have your DNS server listen on all (non-public-facing) interfaces.
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict.
You can have DNS running on both hosts, and transition the hosts to use the new DNS server or, probably more wisely, transition the IoT devices to use DHCP with MAC Address reservations to give them static DHCP IP assignments and DNS Server settings. You can then use DHCP to cut DNS service from one host to the other seamlessly.
If the old device is going to be shut down and/or repurposed with a new IP Address, most devices (presumably including the new one) are capable of adding virtual interfaces (e. g. eth0 can also drive eth0:0 and eth0:1 each with their own IP stack). So once the old device is removed, you can add a new virtual interface on the old IP address, and have your DNS server listen on all (non-public-facing) interfaces.
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
edited Nov 9 '17 at 17:44
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
answered Nov 9 '17 at 17:33
DopeGhoti
40.6k54979
40.6k54979
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
add a comment |Â
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
1
1
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
"You cannot have two devices on the same network segment using the same IP address; this is the very definition of an IP Address conflict." That is why I mention that I'm shutting down the Cubieboard forever. A downtime of 1 minute of the DNS server is something the entire network can tolerate. Like when the Cubieboard has to be rebooted. --- I'm aware of DHCP, but some devices had issues with my custom DHCP server so I did set them to static.
– Daniel F
Nov 9 '17 at 17:34
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403577%2fmigrate-service-and-ip-address-from-one-pc-to-another-so-that-the-other-pc-take%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
You can have several IPv4 addresses on the same interface, but there are some issues (e.g., which source address should be used for outgoing packets?). Hopefully, the DNS server can be configured to bind on x.x.x.10, so the whole thing may work (but I've never tried anything like this myself). As it's a home network, in your place I'd just try it, test thoroughly, and switch back if there are gotchas.
– dirkt
Nov 9 '17 at 20:04