Recent content by sverker

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. S

    OpenVPN LAN to LAN: bad source address from client [172.26.1.78], packet dropped

    Ok, I figured it out. Common Name is "client", and I thought it would use the username as CN. That's why my ccd file wasn't read. Adding directive username-as-common-name as custom configuration on server side solved the issue.
  2. S

    OpenVPN LAN to LAN: bad source address from client [172.26.1.78], packet dropped

    Indeed the issue was that the file in ccd wasn't read, because when I copied it to a DEFAULT file in the same folder then the iroute statement was activated and the traffic works between the lan's. Another issue is that on the client router I need to add a rule to POSTROUTE chain otherwise...
  3. S

    OpenVPN LAN to LAN: bad source address from client [172.26.1.78], packet dropped

    Client side: Network: 172.26.1.0/24 Router: Asus RT-N66U with Merlin fw 380.70 Generated openvpn config: admin@RT-N66U-ED68:/tmp/home/root# cat /etc/openvpn/client5/config.ovpn # Automatically generated configuration daemon client dev tun15 proto udp remote xxxxxx 1194 resolv-retry infinite...
  4. S

    OpenVPN LAN to LAN: bad source address from client [172.26.1.78], packet dropped

    I'm attempting to set up a lan to lan vpn between two Asus routers running Merlin firmware. I've read through numerous threads on this topic in the forum but none seems to match the issue I see. Server side: Network: 172.26.2.0/24 Router: Asus RT-AC3200 with Merlin fw 384.13_10 Generated...
Top