PepVPN bridge across same topology networks


#1

Hello everybody,

an office of a customer of mine currently runs well over Balance 30, but has decided to move the production servers to a farm, task for which I have borrowed a Balance 20 to first try the config.

Essentially the idea is perfectly bridging the two local historical networks:
192.168.1/24 (notag)
192.168.70/24 (vlan70)
which run under a L3 switch whose uplink is a Balance 30 on 192.168.255/24 (notag) network, thanks to static routes, with the same topology networks under the Balance 20. Here follows a graphical explanation.

192.168.1/24 (notag)
192.168.70/24 (vlan70)
|
SWITCH L3 (192.168.255.1/24 + 192.168.1.254/24 + 192.168.70.254/24)
|
Balance 30 (192.168.255.2/24 + WAN addr)
|
Fiber Modem
|
THE INTERNET
|
Balance 20 (WAN addr + 192.168.1.253/24 + 192.168.70.253/24)
|
L2 SWITCH
|
192.168.1/24 (notag)
192.168.70/24 (vlan70)

In order to try this I first configured a normal PepVPN between the two Balance devices, but it reported a “route conflict” (a sign that local static routes on Balance 30 are working well).

When I instead tried (both with and without STP) to establish a direct L2 PepVPN using the main LAN network of each Balance device like in this example How to Configure Layer 2 SpeedFusion VPN , the connection could not be established, always reporting a “Starting…” status.

Does anybody have valuable clues to get me out of this dead end? The presence of a “bridge” functionality should allow for the same network to exist on both sides (e.g. 192.168.1/24) or am I assuming something wrong?

Also: does PepVPN just need UDP 4500 port to operate or more?

Thanks in advance,
Pasha