ascrod / pfsense-pkg-wireguard Goto Github PK

Installed latest wireguard and wireguard-go packages, installed the prebuilt package.

Can ping external addresses from WAN interface in pfsense, but can't ping from LAN interface using pfsense diagnostics ping.

If you need me specific info, let me know.

https://github.com/Ashus/pfSense-pkg-wireguard/releases/download/v1.0.1/pfSense-pkg-wireguard-1.0.1-freebsd11-amd64.txz

As pfSense is used by commercial entities who might be interested in the WG Package. It would be ideal if you can enable sponsorship for the project.

Hello, I have configured both ends. It is found that the routing table and IP seem to be normal but there is no UDP packet, which may be caused by a firewall mechanism. How should I configure it?

Routing table on VPS
[root@seoul-kr-1 ~]# ip -6 r ::1 dev lo proto kernel metric 256 pref medium 2401:c080:1c01:60e::/64 dev ens3 proto ra metric 202 mtu 1500 pref medium 2602:feda:ab3:fff1::/68 dev home-1 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium default via fe80::fc00:3ff:fe01:dc59 dev ens3 proto ra metric 202 mtu 1500 pref medium
Configuration file on VPS
`[Interface]
PrivateKey = eMRpt7xAFb/=
Address = 2602:feda:ab3:fff1:1::/68
ListenPort = 5247

[Peer]
PublicKey = /jwi4GY=
#AllowedIPs = 2602:feda:ab3:fff2::/64

pfsense

But I found that there are no UDP packets on the VPS. why？
`

As per the readme, the current model only support one interface.

If there is a need for more interfaces, add the tunwg1.conf or more files with incremental interface number to /usr/local/etc/wireguard/. Unfortunately those cannot be currently edited via GUI, and everytime you add more, you need to reinstall this package or wireguard service. Each time the service is reinstalled, all tunnels are detected from files again, so they could persist across reboots and could be reloaded from GUI all at once.

It would be ideal if multiple interfaces can be supported using the GUI. This can include multiple server setups or as client peer.

Sponsor Budget: 50-100$

Thanks for doing this! Really cool, and works well.

On a VPN server, it's useful to know what IPs are already reserved, so I hacked it in the overview with:

<columnitem>
    <fielddescr>Allowed IPs</fielddescr>
    <fieldname>allowedips</fieldname>
    <encoding>base64</encoding>
</columnitem>

But I'm not sure how you feel about this, and if you use a long list there for example?

@Ashus With the whole wireguard/freeBSD kernel fiasco. I think focus will shift to this project for folks who like the simplicity and speed of WG.

Any thoughts on if you are going to do any more dev on this, to get it ready for pfsense 2.5.x when they will most likely remove the wg kenrel code.

Hi , will this work on my alix 2d13 running pfsense 2.3?or it is for x64 only?