database64128

Thank you for rebasing and keeping this PR up-to-date! It's in much better shape now that the route calls are implemented in code. Still, I have some concerns with the...

> > Does the network interface change? Would it work for you if I add an option to bind to a specific interface? > > I can fix the IP...

> Please correct me If I am wrong, I am assuming that this approach assumes that we could get to send out packets successfully and we get to parse the...

> I surely can set the `pktinfo` via the socket control message, but it still cannot solve `no route` problem ? I mean specifying the outgoing networking interface is not...

> Actually I tried this, it threw routing errors (could not route to the proxy server). It did not work. > > https://github.com/lsgrep/swgp-go/tree/macos-routes2 Sorry I didn't describe it clearly. The...

@lsgrep I just tested the pktinfo approach with some minimal test code on my MacBook and did not see `no route to host` errors. Could you adapt the following code...

@lsgrep Hi, I just finished implementing this feature for the BSDs. Can you give it a try? It's on the main branch. Add `"proxyAutoPickInterface": true` to your client config to...

@lsgrep Can you post all relevant log messages, especially the ones from the interface picker? I tested this on my MacBook and it worked perfectly.

> `newAddr=192.168.1.5 newIfindex=15` Is this the right interface to send packets from? What’s the configuration of your WireGuard tunnel? I’m using the WireGuard app from the App Store. My allowed...

Your routing table does not match your `AllowedIPs`. `0.0.0.0/0` should result in a default IPv4 route on the tunnel interface, but you instead have `0/1` and `128.0/1`. `::/0` should result...