OPENVPN SAYS CONNECTED. THE INTRANET WIKI SAYS NOTHING. WHAT'S GOING ON??

dnsroutingvpn7 replies 路 282 views 路 started
  1. so annoyed rn i set up OpenVPN for our small team. the connection establishes, handshake looks good, but no traffic gets to the intranet wiki:

    pings to internal IPs time out. im suree the server side is running. what am i overlooking?

    the server and client configs were copied from a guide, adjusted for our network... the tunnel clearly comes up, so keys and ports seem fine. smth after that point is wrong, but i cant tell what. im about to throw this thing out the window lol

    1
  2. been there man MTU issues cause connects but big things hang: pings work, websites half-load, file copies stall, lower the tunnel MTU (WireGuard MTU = 1380, for example) and test with ping -f -l 1350 <ip> on Windows to find teh working size.

    1 2 helpful
  3. @ibanerjee_45 nah thats not it, routing has notihng to do with it

    1 3 helpful
  4. ok update: did what @cron_garage said and its fine now seriously made my day 馃槶馃檹

    15 2 helpful
  5. separate routing from DNS. try the internal IP directly: if teh IP works but the name fails, its DNS. check which DNS servers are in use while connected (ipconfig /all on Windows, resolvectl status on Linux, scutil --dns on macOS).

    5 4 helpful
  6. Hotel and guest networks sometimes block UDP or specific ports. If the client calims connected but no handshake data flows, try the TCP/443 fallback mode if your VPN offers one.

    0 1 helpful
  7. @cron_garage Added teh internal DNS server and search domain to the OpenVPN config. Names resolve and the intranet wiki opens. thank u thank u thank u

    2 0 helpful

Reply to this topic

Sign in or create an account to reply.