Two routers in same(LAN) network

Product Discussion
1

I’m trying to find out if there’s a way to bridge two LAN networks that are 1 mile apart.
Both properties will have a PepWave UBR router with T-Mobile, and both sites have a gate access system that require internet.

Due to several reasons these gate access systems need to be linked to the same account to give our clients access to both of these properties.
To that end these gate systems have to be on the same local LAN network to operate.

So I’m curious is there a way to link these routers and get both properties on the same network / IP subnet,

For reference:
Property #1 has multiple cameras and other devices that get IPs via DHCP on router #A
There is at least one device that has a static IP and a hard-coded host name.

Property #2 is where our issues arise. (we plan on installing router #B here)
This has the gate system that needs to be on the same IP range as property #1.
In addition this ALSO has the same device that the other property #1 has. So it has the same static IP and the same hard-coded host name.

So this is what is causing me to ask the question.
If there is a way to bridge these routers, there’s going to be 2 devices with the same IPs and the same host names on the same network.
Obviously that’s going to be a problem
I also assume that only one of the routers can be used for DHCP.

EDIT: we “may” have the ability to change static IPs and fix the first problem of conflicting IPs/host names.
But we still need to bridge these two properties to be on same network.

Anyone have ideas or suggestions?

I would also be curious to know if any suggested solution would require the PepWave Prime Care?

Thanks

2

“Same LAN” is incredibly vague and could mean many things. A LAN could be all of RFC1918. A LAN could be a single /24 subnet. In all likelihood the “same LAN” requirement of your gate software is really just “need private IP networking access between host A and B.” Meaning it doesnt work over the internet thru firewalls.

Using the same subnets on two distinct networks which are actually unique is ill advised.

Each network should have its own adrress space. Then you should “bridge” them in a way which does not restrict traffic - effectively allowing “direct communication”.

Design it properly and youll have better success.

If you try making same address space in two networks and connect them not only would that be unnecessary, you likely will not succeed.

3

Sorry if that was not clear… They need to be on the same subnet.

The gate access device at both locations need to be on the default 192.160.50.x subnet.

So what are the options to bridge these two locations?

4

Do they really need to be in the same subnet? Or do they just need to be able to talk to each other?

One answer to your question is a site to site VPN. Speedfusion may be another answer, this is at the limits of my technical ability. Might be a good question for your Peplink reseller.