Hi all-
I have an application where:
- I have a fixed system with a pre-determined, static, network (say, 192.168.2.0/24).
- That system needs to have "peer to peer" communication to devices on mobile equipment with the constraint that we don't want to reconfigure the IP addresses each time.
- There will be up to 4 mobile systems with the same IP configuration.
These mobile systems will not always be the same, and will come and go. However, we can guarantee the private IP addresses will always be the same.
- There is an edge device on each system to aggregate data up to AWS (Edge device has a 4G Sim card) but that connection is segregated from the rest of the system.
I have the ability to reserve a physical switchport to each mobile system in order to differentiate. I'm thinking this would be an appropriate application to implement a NAT solution to reserve addresses on on "Fixed System" network for any device that plugs into the Fixed System switch (with a pre-determined "Private" address).
I have not encountered this "one to many" NAT scenario, so I am not sure how to implement it. I've always deployed NAT devices at the individual equipment level - but we can't do that since the mobile systems could be plugged into any port on the "Fixed" system.
Looking for some guidance to get pointed in the right direction. The end goal is to have these mobile systems plug into the fixed system network, and the fixed system recognizes the devices as we have NATed the connections, based on the incoming access port.
I've attached a diagram to help illustrate.
Thanks!
I have an application where:
- I have a fixed system with a pre-determined, static, network (say, 192.168.2.0/24).
- That system needs to have "peer to peer" communication to devices on mobile equipment with the constraint that we don't want to reconfigure the IP addresses each time.
- There will be up to 4 mobile systems with the same IP configuration.
These mobile systems will not always be the same, and will come and go. However, we can guarantee the private IP addresses will always be the same.
- There is an edge device on each system to aggregate data up to AWS (Edge device has a 4G Sim card) but that connection is segregated from the rest of the system.
I have the ability to reserve a physical switchport to each mobile system in order to differentiate. I'm thinking this would be an appropriate application to implement a NAT solution to reserve addresses on on "Fixed System" network for any device that plugs into the Fixed System switch (with a pre-determined "Private" address).
I have not encountered this "one to many" NAT scenario, so I am not sure how to implement it. I've always deployed NAT devices at the individual equipment level - but we can't do that since the mobile systems could be plugged into any port on the "Fixed" system.
Looking for some guidance to get pointed in the right direction. The end goal is to have these mobile systems plug into the fixed system network, and the fixed system recognizes the devices as we have NATed the connections, based on the incoming access port.
I've attached a diagram to help illustrate.
Thanks!