Using a 2nd Sonicwall to extend network with same IP subnet?
I have a client that needs to "extend" their IP subnet to a 2nd location. Let me explain - The IP Subnet at their HQ is 192.168.1.0. They have a 2nd location with a POS system and printer that requires that the POS and the Server that runs the POS be on the same Subnet. What I am trying to figure out is, can I use a 2nd SonicWall (They already have one at HQ) VPN connected to primary SonicWall at HQ to "stretch" their subnet over to that second location so that the POS and Printer would also be on 192.168.1.0 and visible to the POS Server across the VPN as 192.168.1.X?
Is this crazy? According to the client this is the ONLY way it will work per the POS vendor.
Answers
POS, indeed!
No, Sonicwall cannot bridge L2 networks across L3.
If the POS system is Windows, you could install GVC on it and "get" an IP from the 1st location subnet. It would then be "in" the same subnet.
I am unfamiliar with GVC - can you tell me more about it?
oh! You mean Global VPN Client
Would an SSLVPN be the same thing here? Just using the SW NetExtender?
No, I specifically mentioned GVC because it can [or will by default? Can't remember] assign the client an IP out of the firewall's X0 subnet.
Ah! Excellent info! I assume that GVC being its own standalone installed client means that it would negate the need for the Sonicwall at the 2nd location?
That's correct.
I suggest you test this first before celebrating, however. There may be some wrinkle with how this POS software expects the L2 aspect(s) of this connection to work. E.g. there may be some non-IP traffic that GVC doesn't carry. I'm just guessing here though, I don't understand the L2 requirement in the first place!