Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - umggc

Pages: [1]
1
Yeah, it is not difficult to implement as far as I can tell, if only I know enough about using command lines.  :-[ 

In terms of DHCP, I guess as long as the option of blocking DHCP across tunnel is ticked in openvpn, there shouldn't be much problem. In addtion, if the tunnel is always on, one could potentially leave just one DHCP server active and allow DHCP across tunnel.

5
Just to clarify. Both sites begin with the same 192.168.0.0/24 LAN, the assignment of IPs are planned ahead so that there is no conflict. Indeed the whole function of openvpn is to create a switch in this case.

6
Christian,

I saw your note in IdeaTorrent. Thanks for responding.

What I am trying to get is slightly different. The current way of zentyal to zentyal tunnel is something like this:

Zentyal A acting as server: LAN 192.168.0.0/24, VPN 196.168.160.0/24;
Zentyal B acting as client: LAN 192.168.1.0/24.
When connected, A will have 195.168.160.1, B 195.168.160.2, and traffic between two sites are routed (at layer 3?).

What I am hoping to get is to bridge the two sites (at layer 2?) so that everything is on 192.168.0.0/24 (for instance server A is 192.168.0.1 with some connected workstations occupying 192.168.0.10-20, and VPN clients in 192.168.0.200-220; whereas server B is 192.168.0.101 (and a possibly another ip assigned by the VPN), with some other clients occupying 192.168.0.110-120.)

Pages: [1]