Hot Swap two computers on local network?

I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.

When I switch to the win10 machine, I'm currently entering the router,
changing the address reservation from 7 to 8
changing the address reservation from 10 to 7
changing the address reservation from 8 to 10
The router insists on rebooting.
That takes the phone and the security camera and the
network storage drive offline for a while.
Then I reboot both computers.
Works Great, except that the synergy software KVM server is hard wired
to an IP address that will be different.
Problem is that this is horribly inconvenient.

I need a better way.
What I'd like to happen is that when the win10 system boots, it does
all that and reverses it before shutdown.
I don't have any problem switching to fixed IP addresses.
I'm expecting that one or both computers will strenuously object
to having its IP address changed by an outside source.
And that the network connection will be lost requiring some kind
of delayed action scripting.
I'm guessing that the router DHCP server won't have an issue if
nobody from that MAC address asks for an IP address, but that's easily
fixable.

I've thought about temporarily double natting it so I can swap addresses
without taking down the whole network.
I think that means that I'd have to do the port forwarding in the
second router and run it in bridged mode with DDWRT...sounds complicated.

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

Ideas?

mike wrote:

I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.

When I switch to the win10 machine, I'm currently entering the router,
changing the address reservation from 7 to 8
changing the address reservation from 10 to 7
changing the address reservation from 8 to 10
The router insists on rebooting.
That takes the phone and the security camera and the
network storage drive offline for a while.
Then I reboot both computers.
Works Great, except that the synergy software KVM server is hard wired
to an IP address that will be different.
Problem is that this is horribly inconvenient.

I need a better way.
What I'd like to happen is that when the win10 system boots, it does
all that and reverses it before shutdown.
I don't have any problem switching to fixed IP addresses.
I'm expecting that one or both computers will strenuously object
to having its IP address changed by an outside source.
And that the network connection will be lost requiring some kind
of delayed action scripting.
I'm guessing that the router DHCP server won't have an issue if
nobody from that MAC address asks for an IP address, but that's easily
fixable.

I've thought about temporarily double natting it so I can swap addresses
without taking down the whole network.
I think that means that I'd have to do the port forwarding in the
second router and run it in bridged mode with DDWRT...sounds complicated.

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

Ideas?

Why use DHCP (upstream of your intranet hosts in the router) to assign
IP addresses (even if you use MAC addresses to have the router assign
the same IP addresses to each OS)? Is there a reason you don't use
static IP addresses in each OS, like 192.168.1.50 for Windows 7 and
192.168.1.60 for Windows 10? Despite the same MAC sent from the NIC in
the same host for both OSes, each OS would have a static IP address, not
a dynamic one that get reassigned by the router's DHCP server.

Port forwarding in the router to, say, 192.168.1.50 for Windows 7
wouldn't change whether that OS was loaded or not. If Windows 7 were
running, it would have that same IP address all the time, so the port
forwarding in the router would still point to the same host where
Windows 7 was running. If you booted to Windows 10 on that host, the
192.168.1.50 IP address would not be present, so the port forwarding in
the router would have no host to reach.

I don't remember ever having to reboot Windows to switch its IP address
whether dynamically or statically assigned. When dynamically assigned,
and after changing the IP address, I would would open a command shell
with elevated privileges to run:

ipconfig /release all
ipconfig /flush dns
ipconfig /renew

That would unbind from the IP address assigned by the DHCP server (in
the router) and request a new binding. When I switch to a static IP
address configured in the OS, no reboot is needed of the host or the
router. The Windows host starts using the new static IP address. I
might run the "ipconfig /release all" but the renew would be needed to
ask the DHCP server for a new assignment since you're using a static
address. You just have to make sure the static IP address you use is
within the range the router will support. In fact, the DHCP server
probably has a fixed range of addresses it will dynamically assigned,
like 192.168.2 to 192.168.1.100. To make sure to avoid conflicts, use a
static IP address in Windows that is outside that range, like
192.168.1.150 and 192.168.1.160.

In my router/modem, its DHCP server is configured to assign dynamic IP
addresses in the range of 10.0.0.2 to 10.0.0.253. For a host where I
wanted a static IP address, I might use 10.0.1.50 for Windows 7 and
10.0.1.60 for Windows 10. Those are outside the range for the router's
DHCP addressing to avoid any conflicts (where a host got my IP address
when that OS was off/invisible and then later I powered on that OS to
find my static IP address had already been assigned by the DHCP server).
If I didn't want to roam outside the 10.0.0.x range, I'd change the DHCP
server so its address range it could assign was 10.0.0.2 to 10.0.0.100
(I won't have 98 hosts running at home, so that is more than adequate),
and then use 10.0.0.150 and 10.0.0.160 for Windows 7 & 10.

When you are using static IP addresses, it is your job to manage which
static IP address is used by each of your intranet hosts or the OSes
each will load. DHCP eliminates the user having to do that management
but it doesn't work too well for port forwarding when the hosts come and
go and end up getting different IP addresses than before. When multi-
booting multiple OSes, each will have the hardware's MAC address, so you
cannot differentiate each OS because their MACs are the same ...

.... however, in the NIC config in Windows, you can override the MAC
address to specify your own. Go into the Device Manager (devmgmt.msc),
right-click on the network adapter, select Properties, go into the
Advanced tab, and select the "Locally administered address" attribute
for the device. You can specify a different (software) MAC than the
hardware MAC. If you are having the router's DHCP server reserve
specific IP addresses for each OS that loads on the same host which
would end up with the same hardware MAC, configure each OS to have a
different MAC, and that's what you use in the router's reservation of IP
addressing by MAC address.

While it's doable to change the MAC using the OS setting, if you
reinstall the OS then you'll probably find setting static IP addresses
(IPv4 and IPv6) easier than figuring out how to use the OS override on
the MAC address which making sure you don't step on any other host that
might have that hardware or software MAC address. In a command shell,
you can use "arp -a" to see what are the MACs for the other intranet
hosts that your host has found to know you shouldn't use any of those.

So you can use a static IP address (preferrably outside the router's
DHCP range) that is configured in each OS that you load on different
hosts or multi-boot on the same host. Or you can specify an OS override
on the MAC address, so each OS reports a different MAC although multi-
booted on the same hardware.

In article , VanguardLH
wrote:


I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.


....

Why use DHCP (upstream of your intranet hosts in the router) to assign
IP addresses (even if you use MAC addresses to have the router assign
the same IP addresses to each OS)?

because dhcp is significantly easier to manage and ip addresses are
assigned to hardware, not an os.

Is there a reason you don't use
static IP addresses in each OS, like 192.168.1.50 for Windows 7 and
192.168.1.60 for Windows 10?

he's using .7 and .10, same thing but different numbers.

Despite the same MAC sent from the NIC in
the same host for both OSes, each OS would have a static IP address, not
a dynamic one that get reassigned by the router's DHCP server.

the same mac address would not be sent unless he spoofs them, which
will cause other problems.

In article , mike
wrote:

I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.

When I switch to the win10 machine, I'm currently entering the router,
changing the address reservation from 7 to 8
changing the address reservation from 10 to 7
changing the address reservation from 8 to 10
The router insists on rebooting.
That takes the phone and the security camera and the
network storage drive offline for a while.
Then I reboot both computers.
Works Great, except that the synergy software KVM server is hard wired
to an IP address that will be different.
Problem is that this is horribly inconvenient.

some routers do not require a reboot when changing dhcp reservations
(or other settings) and you don't need to reboot the computers either,
just renew their lease.

I need a better way.

yes, you do.

why do you need forwarding at all?

and if you do need forwarding, set up two rules and switch between them.

What I'd like to happen is that when the win10 system boots, it does
all that and reverses it before shutdown.

why?

I don't have any problem switching to fixed IP addresses.

you have that.

I'm expecting that one or both computers will strenuously object
to having its IP address changed by an outside source.

that's what dhcp is, so no.

And that the network connection will be lost requiring some kind
of delayed action scripting.

only momentarily and won't affect anything.

I'm guessing that the router DHCP server won't have an issue if
nobody from that MAC address asks for an IP address, but that's easily
fixable.

I've thought about temporarily double natting it so I can swap addresses
without taking down the whole network.
I think that means that I'd have to do the port forwarding in the
second router and run it in bridged mode with DDWRT...sounds complicated.

double-nat isn't going to help and is generally a bad idea.

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

what problem are you actually trying to solve?

migrating and configuring doesn't need screwing around with ip
addresses.

On 12/7/2018 5:05 AM, nospam wrote:
In article , mike
wrote:

I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.

When I switch to the win10 machine, I'm currently entering the router,
changing the address reservation from 7 to 8
changing the address reservation from 10 to 7
changing the address reservation from 8 to 10
The router insists on rebooting.
That takes the phone and the security camera and the
network storage drive offline for a while.
Then I reboot both computers.
Works Great, except that the synergy software KVM server is hard wired
to an IP address that will be different.
Problem is that this is horribly inconvenient.

some routers do not require a reboot when changing dhcp reservations
(or other settings) and you don't need to reboot the computers either,
just renew their lease.

I need a better way.

yes, you do.

why do you need forwarding at all?

and if you do need forwarding, set up two rules and switch between them.

What I'd like to happen is that when the win10 system boots, it does
all that and reverses it before shutdown.

why?

I don't have any problem switching to fixed IP addresses.

you have that.

I'm expecting that one or both computers will strenuously object
to having its IP address changed by an outside source.

that's what dhcp is, so no.

And that the network connection will be lost requiring some kind
of delayed action scripting.

only momentarily and won't affect anything.

I'm guessing that the router DHCP server won't have an issue if
nobody from that MAC address asks for an IP address, but that's easily
fixable.

I've thought about temporarily double natting it so I can swap addresses
without taking down the whole network.
I think that means that I'd have to do the port forwarding in the
second router and run it in bridged mode with DDWRT...sounds complicated.

double-nat isn't going to help and is generally a bad idea.

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

what problem are you actually trying to solve?

migrating and configuring doesn't need screwing around with ip
addresses.

I tried to be very descriptive about what I'm doing.

I want to EASILY switch between two active computers in operation
and have the port forwarding move seamlessly to the computer I'm
currently working on...maybe several times a day.
At the current rate, it's gonna be a while before I get all the
win10 hardware and software compatibility issues resolved.

I considered port triggering, but some of the functions don't
speak unless spoken to.

Modifying port forwarding in the router is conceptually trivial,
but takes a lot of typing. This router doesn't have the convenience
of a checkbox to enable/disable a port forward.

I have several ports to manage. And the router typically checks for
errors and won't let you have ports forwarded to different computers even
if for a few seconds while configuring.

Swapping the IP address doesn't disrupt the system and its devices...
but still very annoying. I don't know how to script it as it's
changing the network that it's editing on the fly.

In article , Mike
wrote:

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

what problem are you actually trying to solve?

migrating and configuring doesn't need screwing around with ip
addresses.

I tried to be very descriptive about what I'm doing.

I want to EASILY switch between two active computers in operation
and have the port forwarding move seamlessly to the computer I'm
currently working on...maybe several times a day.

why do you have port forwarding enabled at all? what services are you
using that needs inbound access? it's a security hole that is rarely
needed.

At the current rate, it's gonna be a while before I get all the
win10 hardware and software compatibility issues resolved.

that shouldn't be dependent on networking.

I considered port triggering, but some of the functions don't
speak unless spoken to.

which ones, specifically?

Modifying port forwarding in the router is conceptually trivial,
but takes a lot of typing.

not really, unless you're configuring it via the command line, in which
case, you would only need to type it once and make a minor edit.

This router doesn't have the convenience
of a checkbox to enable/disable a port forward.

then get one that does. if you're tied to port forwarding, it's money
well spent.

or, if your current router supports it, install an alternative firmware.

On 12/7/2018 2:31 AM, VanguardLH wrote:
mike wrote:

I have a windows 7 computer on 192.168.1.7.
I'm migrating/configuring a windows 10 computer on 192.168.1.10.
I have ports forwarded to the windows 7 machine.

I switch back and forth debugging the win10 system.

Both computers are set for DHCP and the addresses are reserved
in the router.

When I switch to the win10 machine, I'm currently entering the router,
changing the address reservation from 7 to 8
changing the address reservation from 10 to 7
changing the address reservation from 8 to 10
The router insists on rebooting.
That takes the phone and the security camera and the
network storage drive offline for a while.
Then I reboot both computers.
Works Great, except that the synergy software KVM server is hard wired
to an IP address that will be different.
Problem is that this is horribly inconvenient.

I need a better way.
What I'd like to happen is that when the win10 system boots, it does
all that and reverses it before shutdown.
I don't have any problem switching to fixed IP addresses.
I'm expecting that one or both computers will strenuously object
to having its IP address changed by an outside source.
And that the network connection will be lost requiring some kind
of delayed action scripting.
I'm guessing that the router DHCP server won't have an issue if
nobody from that MAC address asks for an IP address, but that's easily
fixable.

I've thought about temporarily double natting it so I can swap addresses
without taking down the whole network.
I think that means that I'd have to do the port forwarding in the
second router and run it in bridged mode with DDWRT...sounds complicated.

Is this something I'll be able to do, or should I just give up
on fast IP address switching.

Ideas?

Why use DHCP (upstream of your intranet hosts in the router) to assign
IP addresses (even if you use MAC addresses to have the router assign
the same IP addresses to each OS)? Is there a reason you don't use
static IP addresses in each OS, like 192.168.1.50 for Windows 7 and
192.168.1.60 for Windows 10? Despite the same MAC sent from the NIC in
the same host for both OSes, each OS would have a static IP address, not
a dynamic one that get reassigned by the router's DHCP server.

Port forwarding in the router to, say, 192.168.1.50 for Windows 7
wouldn't change whether that OS was loaded or not. If Windows 7 were
running, it would have that same IP address all the time, so the port
forwarding in the router would still point to the same host where
Windows 7 was running.

That's not what I want. I want the port forwarding to go to the hardware
running windows 10 or the hardware running windows 7 at different
times, easily swapped with both machines continuing to function in all
other respects.

If you booted to Windows 10 on that host, the
192.168.1.50 IP address would not be present, so the port forwarding in
the router would have no host to reach.

I don't remember ever having to reboot Windows to switch its IP address
whether dynamically or statically assigned. When dynamically assigned,
and after changing the IP address, I would would open a command shell
with elevated privileges to run:

ipconfig /release all
ipconfig /flush dns
ipconfig /renew



That would unbind from the IP address assigned by the DHCP server (in
the router) and request a new binding. When I switch to a static IP
address configured in the OS, no reboot is needed of the host or the
router. The Windows host starts using the new static IP address. I
might run the "ipconfig /release all" but the renew would be needed to
ask the DHCP server for a new assignment since you're using a static
address. You just have to make sure the static IP address you use is
within the range the router will support. In fact, the DHCP server
probably has a fixed range of addresses it will dynamically assigned,
like 192.168.2 to 192.168.1.100. To make sure to avoid conflicts, use a
static IP address in Windows that is outside that range, like
192.168.1.150 and 192.168.1.160.

In my router/modem, its DHCP server is configured to assign dynamic IP
addresses in the range of 10.0.0.2 to 10.0.0.253. For a host where I
wanted a static IP address, I might use 10.0.1.50 for Windows 7 and
10.0.1.60 for Windows 10. Those are outside the range for the router's
DHCP addressing to avoid any conflicts (where a host got my IP address
when that OS was off/invisible and then later I powered on that OS to
find my static IP address had already been assigned by the DHCP server).
If I didn't want to roam outside the 10.0.0.x range, I'd change the DHCP
server so its address range it could assign was 10.0.0.2 to 10.0.0.100
(I won't have 98 hosts running at home, so that is more than adequate),
and then use 10.0.0.150 and 10.0.0.160 for Windows 7 & 10.

When you are using static IP addresses, it is your job to manage which
static IP address is used by each of your intranet hosts or the OSes
each will load. DHCP eliminates the user having to do that management
but it doesn't work too well for port forwarding when the hosts come and
go and end up getting different IP addresses than before. When multi-
booting multiple OSes, each will have the hardware's MAC address, so you
cannot differentiate each OS because their MACs are the same ...

... however, in the NIC config in Windows, you can override the MAC
address to specify your own. Go into the Device Manager (devmgmt.msc),
right-click on the network adapter, select Properties, go into the
Advanced tab, and select the "Locally administered address" attribute
for the device. You can specify a different (software) MAC than the
hardware MAC. If you are having the router's DHCP server reserve
specific IP addresses for each OS that loads on the same host which
would end up with the same hardware MAC, configure each OS to have a
different MAC, and that's what you use in the router's reservation of IP
addressing by MAC address.

While it's doable to change the MAC using the OS setting, if you
reinstall the OS then you'll probably find setting static IP addresses
(IPv4 and IPv6) easier than figuring out how to use the OS override on
the MAC address which making sure you don't step on any other host that
might have that hardware or software MAC address. In a command shell,
you can use "arp -a" to see what are the MACs for the other intranet
hosts that your host has found to know you shouldn't use any of those.

So you can use a static IP address (preferrably outside the router's
DHCP range) that is configured in each OS that you load on different
hosts or multi-boot on the same host. Or you can specify an OS override
on the MAC address, so each OS reports a different MAC although multi-
booted on the same hardware.

Thanks for trying to help. There are likely many ways to skin this cat.
I'm looking for something that is easy to accurately configure.
I might do this several times a day.

I use DHCP with address reservation because it solves the problem of
taking your tablet to Starbucks and having it connect to their hotspot.
I'm willing to change these two computers to fixed addresses if it
helps, but I've not yet heard anything that it fixes in this case.

Changing the port forwarding in the router is the best way to fix this,
but it's a lot of typing. Swapping IP addresses is less hassle.

Mike wrote:

There are likely many ways to skin this cat.
I'm looking for something that is easy to accurately configure.
I might do this several times a day.

Stop using DHCP on the win7 and win10 machines, create batch files to
swap the IP addresses using netsh.exe

https://www.howtogeek.com/103190/change-your-ip-address-from-the-command-prompt/

or get really trendy and use powershell

https://www.howtogeek.com/112660/how-to-change-your-ip-address-using-powershell/

Mike wrote:

I want the port forwarding to go to the hardware
running windows 10 or the hardware running windows 7 at different
times, easily swapped with both machines continuing to function in all
other respects.

I thought you were multi-booting but now noticed that you said "two
computers". I'd need to know about why you are port forwarding through
your router. Obviously if you can define one port forwarding rule then
you could define another; however, port forwarding goes to a particular
host based on the port used to connect to the WAN-side of the router.
Why can't you use a different port number to the WAN-side of the router
to determine to which host that incoming traffic gets directed? You
decide from your external host to which internal host you get directed
based on the port you specify from the external host.

To use DHCP for dynamic IP addressing instead of static IP addresses,
does the router let you assign (reserve) an IP address for a particular
MAC address? Otherwise, how would the router know to which host it
would assign the reserved IP address?

I use DHCP with address reservation because it solves the problem of
taking your tablet to Starbucks and having it connect to their hotspot.
I'm willing to change these two computers to fixed addresses if it
helps, but I've not yet heard anything that it fixes in this case.

Why do you care which IP address their DHCP server gives your host?

Changing the port forwarding in the router is the best way to fix this,
but it's a lot of typing. Swapping IP addresses is less hassle.

You won't be using your router at Starbucks' wi-fi hotspot.

External hosts won't be seeing the IP addresses of your intranet hosts.
They only see the WAN-side IP address of the router which can be static
or dynamically assigned by the upstream DHCP server (at your ISP, at
Starbuck's, or wherever you connect).

Andy Burns wrote:

Mike wrote:

There are likely many ways to skin this cat.
I'm looking for something that is easy to accurately configure.
I might do this several times a day.

Stop using DHCP on the win7 and win10 machines, create batch files to
swap the IP addresses using netsh.exe

https://www.howtogeek.com/103190/change-your-ip-address-from-the-command-prompt/

or get really trendy and use powershell

https://www.howtogeek.com/112660/how-to-change-your-ip-address-using-powershell/

That goes back to using static IP addresses which, for some as yet
unknown reason, the OP doesn't want to use.

It appears these hosts wander from home to Starbucks. At home, the OP
has a router. At Starbucks, the OP is using a wi-fi hotspot. With
static IP addresses on his hosts, Starbucks may not allow him to use
their network, so he's stuck using DHCP at Starbuck's to get whatever IP
address that Starbuck's gives him. However, that also means he doesn't
get a DHCP reserved IP address just for his host. He gets whatever
Starbuck's DHCP server decides to give him.

For the OP to use DHCP away from home, like at hotspots, but punch a
hole through his router at home (perhaps for remote access to his hosts
when they are at home), he should be configuring the router to assign
the reserved IP address by MAC address. The MAC address from the
hardware doesn't change regardless of whether his host is at home or at
Starbucks (except as I noted in the NIC properties for a software
override by the OS).

With his hosts using DHCP to get a dynamically assigned IP address to
use his hosts at home or elsewhere, and with a router that allows
specific IP addressing based on MAC address, I don't see why the OP has
to do any changes in IP config on his hosts or in his router. As for
port forwarding through his home router, that is based on, well, the
port number used for the WAN-side connection. He could define more than
one port forwarding rule, like port 8810 goes to the router-assigned IP
address for his Win7 host and port 8811 goes to the router-assigned IP
address for his Win10 host.

In his hosts, continue using DHCP. Lets him use his local network at
home with its router along with letting him connect elsewhere, like
wi-fi hotspots. At home, his hosts get an IP address from his home
router. His router assigns the reserved IP addresses by MAC address.
Define 2 port forwarding rules: one rule on a port for the router's IP
address assigned to the MAC address for his Win7 host and another rule
on a different port for the router's IP address assigned to the MAC
address for his Win10 host. Obviously he won't get any port forwarding
to drill remotely to his host when connected to Starbucks' network since
he has no control over their router setup. Port forwarding is an issue
only at his home when using his router. As the feature's name
indicates, it forwards based on the port number (which also opens a hole
in the router's firewall, so the target host better be DMZ'ed), so use a
different port in each forwarding rule.

VanguardLH wrote:

It appears these hosts wander from home to Starbucks.

so have another batch file to reset them back to DHCP ...

At home, the OP
has a router. At Starbucks, the OP is using a wi-fi hotspot. With
static IP addresses on his hosts, Starbucks may not allow him to use
their network, so he's stuck using DHCP at Starbuck's to get whatever IP
address that Starbuck's gives him. However, that also means he doesn't
get a DHCP reserved IP address just for his host. He gets whatever
Starbuck's DHCP server decides to give him.

For the OP to use DHCP away from home, like at hotspots, but punch a
hole through his router at home (perhaps for remote access to his hosts
when they are at home), he should be configuring the router to assign
the reserved IP address by MAC address. The MAC address from the
hardware doesn't change regardless of whether his host is at home or at
Starbucks (except as I noted in the NIC properties for a software
override by the OS).

yes, but he's said he wants to swap and change which ports get
redirected to which machine. Ho knows how to do the .7 to .8 and .10 to
..7 and .8 to .10 shuffle manually, creating batch files to automate the
tedious shuffling would make sense.

On 12/7/2018 10:41 AM, Andy Burns wrote:
Mike wrote:

There are likely many ways to skin this cat.
I'm looking for something that is easy to accurately configure.
I might do this several times a day.

Stop using DHCP on the win7 and win10 machines, create batch files to
swap the IP addresses using netsh.exe

https://www.howtogeek.com/103190/change-your-ip-address-from-the-command-prompt/


or get really trendy and use powershell

https://www.howtogeek.com/112660/how-to-change-your-ip-address-using-powershell/

Thank you.
Relevant information.
With examples.

On 12/7/2018 11:19 AM, VanguardLH wrote:
Mike wrote:

I want the port forwarding to go to the hardware
running windows 10 or the hardware running windows 7 at different
times, easily swapped with both machines continuing to function in all
other respects.

I thought you were multi-booting but now noticed that you said "two
computers". I'd need to know about why you are port forwarding through
your router.

To get the external ports to the right computer.

Obviously if you can define one port forwarding rule then
you could define another; however, port forwarding goes to a particular
host based on the port used to connect to the WAN-side of the router.
Why can't you use a different port number to the WAN-side of the router
to determine to which host that incoming traffic gets directed?

Because external forces don't know that they have to connect to a different
external port...sometimes...

You
decide from your external host to which internal host you get directed
based on the port you specify from the external host.

To use DHCP for dynamic IP addressing instead of static IP addresses,
does the router let you assign (reserve) an IP address for a particular
MAC address?

Yes, as described in my original missive. And again three lines down.

Otherwise, how would the router know to which host it
would assign the reserved IP address?

I use DHCP with address reservation because it solves the problem of
taking your tablet to Starbucks and having it connect to their hotspot.
I'm willing to change these two computers to fixed addresses if it
helps, but I've not yet heard anything that it fixes in this case.

Why do you care which IP address their DHCP server gives your host?

Because of port forwarding.
Because of local network linkages defined by IP address, security
cameras, printers, mapped network drives, shortcuts...

Changing the port forwarding in the router is the best way to fix this,
but it's a lot of typing. Swapping IP addresses is less hassle.

You won't be using your router at Starbucks' wi-fi hotspot.

But I might be using my tablet or laptop. IF they have a fixed IP
address of 192.168.1.6, how do they connect? DHCP with address
reservation gives me a fixed address at home and allows normal
DHCP at Starbucks.

External hosts won't be seeing the IP addresses of your intranet hosts.
They only see the WAN-side IP address of the router which can be static
or dynamically assigned by the upstream DHCP server (at your ISP, at
Starbuck's, or wherever you connect).

The issue is mapping external ports to the correct port on the correct
computer hardware when it comes through my router.

On 07/12/2018 21.05, Mike wrote:
On 12/7/2018 11:19 AM, VanguardLH wrote:
Mike wrote:


Changing the port forwarding in the router is the best way to fix this,
but it's a lot of typing.Â* Swapping IP addresses is less hassle.

You won't be using your router at Starbucks' wi-fi hotspot.

But I might be using my tablet or laptop.Â* IF they have a fixed IP
address of 192.168.1.6, how do they connect?Â* DHCP with address
reservation gives me a fixed address at home and allows normal
DHCP at Starbucks.

But nothing stops you to keep using DHCP on the tablet or whatever; just
use fixed IPs on these two computers and switch them fast when needed,
that's all.


External hosts won't be seeing the IP addresses of your intranet hosts.
They only see the WAN-side IP address of the router which can be static
or dynamically assigned by the upstream DHCP server (at your ISP, at
Starbuck's, or wherever you connect).

The issue is mapping external ports to the correct port on the correct
computer hardware when it comes through my router.

I fail to see the problem, sorry. Or rather, what it is you want to achieve.

From outside, you would connect to myhouse.org:10900, which would go to
192.168.0.100:500 inside, or to myhouse.org:10910, which would go to
192.168.0.110:500 inside - for example. Arbitrary numbers.


--
Cheers, Carlos.

On 07/12/2018 19.14, Mike wrote:

Modifying port forwarding in the router is conceptually trivial,
but takes a lot of typing.Â* This router doesn't have the convenience
of a checkbox to enable/disable a port forward.

Many routers are also accessible via telnet or ssh, and you can possibly
create a script that talks to the router and does the change.

--
Cheers, Carlos.