Hello Thanks for the project! I do have a small question about MTU. My MTU values are like this:

• Server Internet: 1500
• Home Internet: 1500
• Server's Wireguard Interface: 1420
• Both swgp-go's: 1500 With this setup, Wireguard connects to internet however, I get this warning on my client's swgp-go and the speed is terrible:

2022-11-18T07:44:34.763+0330 WARN service/client.go:353 Failed to write swgpPacket to proxyConn {"client": "client", "wgListen": "127.0.0.1:20222", "clientAddress": "127.0.0.1:54883", "proxyAddress": "X.X.X.X:Y", "error": "write udp [::]:55084->X.X.X.X:Y: wsasendto: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself."}

Server acknowledges the new UDP session and there is no log afterwards.

My server is Ubuntu 22 and my PC is Windows 10. I also use the zero overhead mode.

I'd be glad if you could help me. Thanks

Hello there,

I try to set up wireguard over shadowsocks my opnsense firewall, but no luck... Now found this project and it is very interisting! It possible to use it with freebsd based system, like OPNsense?

func NewZeroOverheadHandler(psk []byte) (Handler, error) {
	cb, err := aes.NewCipher(psk)
	if err != nil {
		return nil, err
	}

	aead, err := chacha20poly1305.NewX(psk)
	if err != nil {
		return nil, err
	}

so seems psk is 32 bytes, AES-256 is selected.

simple generator:

python3 -c 'import os,base64; print(base64.b64encode(os.urandom(32)).decode("ascii"))'

my wg server on ubuntu was working well until the country decide to activate the dpi.now it s impossible to get wireguard get working. i have windows and android in client side. can you provide a step by step guide so it can help people wich are in my case as well

thank you for your time

Hello, In some ISP's or countries most UDP connection ports are blocked. can you please develop proxy in TCP mode? also i can't understand how to integrate proxy config with wireguard? can you please explain about config for clients and config for servers? you send only one sample config and i don't know this is for server only or client only or may seprate to using each other?

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | go (source) | golang | minor | 1.18 -> 1.19 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | golang.org/x/sys | require | digest | 5a39038 -> 2296e01 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | go.uber.org/zap | require | minor | v1.21.0 -> v1.22.0 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | golang.org/x/crypto | require | digest | 0559593 -> 630584e |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | golang.org/x/sys | require | digest | 1c4a2a7 -> fbc7d0a |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | golang.org/x/crypto | require | digest | 793ad66 -> 0559593 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

Hi, thank you for your outstanding work.

Regarding the disallow unknown fields in config under this commit c9ba810585243590329a44df2a7d24644f7c6ae1 , could you change it to just prompt a warn than throwing a fetal error when encountering an unknown field?

I usually write some notes in json using the unknown fields, like below, and now they are all unavailable.

{
    "interfaces": [
        {
            "Note1": "This is my wireguard server.",
            "name": "wg1",
            "proxyListen": "0.0.0.0:8444",
            "proxyMode": "zero-overhead",
            "proxyPSK": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=",
            "proxyFwmark": 0,
            "wgEndpoint": "127.0.0.1:8443",
            "wgFwmark": 0,
            "mtu": 1492,
            "batchMode": ""
        }
    ],
    "peers": [
        {
            "Note1": "This is my note.",
            "Note2": "This peer was peer to somewhere",
            "name": "name",
            "wgListen": "0.0.0.0:20222",
            "wgFwmark": 0,
            "proxyEndpoint": "1.1.1.1:4444",
            "proxyMode": "zero-overhead",
            "proxyPSK": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=",
            "proxyFwmark": 0,
            "mtu": 1492,
            "batchMode": ""
        }
    ]
}

Or is it possible to support a more human readable format like jsonc(json with comment) or toml?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• [ ] Check this box to trigger a request for Renovate to run again on this repository