Hi Lorenz,
On 07/08/19 21:35, Lorenz wrote:
Huge thanks to both of you! I really appreciate you trying to help me.
On 8/6/19 5:59 PM, Jan Just Keijser wrote:
as you stated: your bridged setup is working, and your clients in
network B get their DHCP addresses from the server in network A. The
only thing missing is the default route for these clients.
That means it's the DHCP server in network A that is not pushing the
right default gateway to these clients. Which DHCP server software
are you using? For standard dhcpd, you'd add something like
I did not think of the DHCP server because if a computer of network B
was physically moved into network A it did get the right gateway
information and therefore added a default route. So I do not think it
is the DHCP server's fault.
I still suspect the dhcp server, or the parsing of the options that the
dhcp server is handing out to clients in network B; when you have a
fully bridged setup then both networks are 99.9% connected at the L2
(ethernet) level. Handing out IP addresses and default routes is then
not up to OpenVPN, but to the network layer above: in your case, your
DHCP server.
However, it is possible that clients in network B refuse to add the
default route offered by the DHCP server because they cannot find the
MAC address of the gateway. I'd run something like wireshark/tcpdump on
your network (e.g. on the openvpn client) and then watch the entire DHCP
message exchange to see if the right default route is offered. If it is,
I'd then investigate why the client (i.e a machine in network B) is not
applying this default route.
If the DHCP server is *not* offering the right default route for clients
in network B, then you need to investigate the dhcp server settings to
see why it does not do so.
HTH,
JJK
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
