Forum Discussion

Aspirant

Jun 11, 2020

Solved

Change DHCP Ending Address to 192.168.2.*

Hope some one can help me. In the LAN Setup of my router, I have chosen below option Use Router as DHCP Server Starting IP Address is 192.168.1.2 Ending IP Address is 192.168.1.254 ...

schumaku
Jun 12, 2020
Leaving alone the Netgear design decision for supporting /24 IP subnets only on the consumer (and some other devices): When I see a 255.0.0.0 subnet and then ....

skhaire14 wrote:
I need Private IP and Public IP in two different subnets and they need to be able to communicate with each other

Here is my setup would look like:

Node 1 / Server A - Public IP - 192.168.1.101 Private IP - 192.168.2.101
Node 2 / Server B - Public IP - 192.168.1.102 Private IP - 192.168.2.102

So I need to be able to communicate using my router any address range between 192.168.1.2 to 192.168.2.254.
If you want two subnets, you need either two physically independent networks, or two VLANs, or the one network you have plus a VM internal network for private VM communication purely in software on the host - ll these making up two dedicated broadcast domains. On each of these two networks, you configure an IP subnet each, say 192.168.1.0/24 and 192.168.2.0/24. On each network, you have a DHCP, as (to keep it simple) DHCP can cover only one broadcast domain, and one IPv4 subnet.

The communication between the two IPv4 subnets must be done on a router with two interfaces, one in the .1.0 network, one in the .2.0 network.

With a 255.0.0.0 subnet, all addresses from 192.0.0.0 - 192.255.255.255 are in the same subnet - and can obliviously communicate as-is - and I assume the router will allow the communication. It does just not allow issuing DHCP addresses beyond of the 192.168.1.x address range. And I don't know if these consumer routers are able to handle NAT in this huge scope.

Said that: These consumer routers only support one (assumingly small) IP subnet and broadcast domain.

skhaire14

Aspirant

Jun 12, 2020

Thanks for the reply.

I certainly do not need to connect more devices. My requirement is slightly different.

I am trying to set up a Two-Node Cluster using Oracle Virtual Box.

I need Private IP and Public IP in two different subnets and they need to be able to communicate with each other

Here is my setup would look like:

Node 1 / Server A - Public IP - 192.168.1.101 Private IP - 192.168.2.101

Node 2 / Server B - Public IP - 192.168.1.102 Private IP - 192.168.2.102

So I need to be able to communicate using my router any address range between 192.168.1.2 to 192.168.2.254.

Hope this helps.

I am not sure if I am breaking community guidelines but I am able to achieve DHCP from my router using another Manufacturer.

schumaku

Guru - Experienced User

Jun 12, 2020

Leaving alone the Netgear design decision for supporting /24 IP subnets only on the consumer (and some other devices): When I see a 255.0.0.0 subnet and then ....

skhaire14 wrote:
I need Private IP and Public IP in two different subnets and they need to be able to communicate with each other

Here is my setup would look like:

Node 1 / Server A - Public IP - 192.168.1.101 Private IP - 192.168.2.101
Node 2 / Server B - Public IP - 192.168.1.102 Private IP - 192.168.2.102

So I need to be able to communicate using my router any address range between 192.168.1.2 to 192.168.2.254.

If you want two subnets, you need either two physically independent networks, or two VLANs, or the one network you have plus a VM internal network for private VM communication purely in software on the host - ll these making up two dedicated broadcast domains. On each of these two networks, you configure an IP subnet each, say 192.168.1.0/24 and 192.168.2.0/24. On each network, you have a DHCP, as (to keep it simple) DHCP can cover only one broadcast domain, and one IPv4 subnet.

The communication between the two IPv4 subnets must be done on a router with two interfaces, one in the .1.0 network, one in the .2.0 network.

With a 255.0.0.0 subnet, all addresses from 192.0.0.0 - 192.255.255.255 are in the same subnet - and can obliviously communicate as-is - and I assume the router will allow the communication. It does just not allow issuing DHCP addresses beyond of the 192.168.1.x address range. And I don't know if these consumer routers are able to handle NAT in this huge scope.

Said that: These consumer routers only support one (assumingly small) IP subnet and broadcast domain.