OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of KorschanX »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

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
  • Topics
  • Attachments

Messages - KorschanX

Pages: [1]
1
Virtual private networks / Re: Wireguard is connected, but not traffic
« on: December 25, 2020, 10:49:53 am »
Quote from: allebone on December 25, 2020, 05:11:37 am
Also under endpoints tab - Allowed IPs - ensure you have both networks listed appropriately on each side. This is what is allowed to route over the tunnel.

A single client would work with only 1 entry listed. This is not appropriate for clients behind the opnsense.

Thank you! This was my mistake.

I just had to add my local net to remote sites allowed IP adresses.

2
Virtual private networks / Wireguard is connected, but not traffic
« on: December 25, 2020, 12:29:10 am »
Hi there,

I would like to connect my local opnsense to my remote opnsense using wireguard.
Successfully configured the remote site - all remote clients are reachable by using wireguard-client for windows.

Now I want to set up my local opnsense to use the same configuration - did so, wireguard seems to be connected and handshaking. I can even ping the remote clients by opnsense (interfaces / diagnoses / ping ... using wg0 interface). Just working fine.

By using a client in my local network, the remote clients are still unreachable.
WireGuard/wg0-interface firewall settings set on any/any

Dont know what to do. Using the Wireguard Windows Client is just working fine.

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2