Replies: 1 comment 3 replies
-
The network packet sent from The configuration key in your configuration for {
"outbound_bind_interface": "en0",
} You could give another try, but if I remember it clearly, bind interface doesn't work like Linux on macOS. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Forgive me, I'm new to shadowsocks and have never dug this deep into VPN's before. I'm trying to get this working as a VPN. I have a couple of challenges. First, how to configure sslocal to work? Here is my config I pass to the ssserver:
I start that process and it seems to startup just fine.
Then I start up sslocal with this config:
I'm running on a Mac, this creates a tun interface called utun6, so I create a default route to send traffic to that new interface:
sudo route add default -interface utun6
Once that is run I can then see tons of crazy logging on both ssserver and sslocal. If I run 'ping example.com' I get a ping response that's resolved to an IP address. But if I run 'curl example.com' I get: curl: (52) Empty reply from server
I have connected an outline client to the sserver instance and it works. I have also connected a shadowsocksX-NG client to ssserver and that also works. What am I doing wrong with my sslocal service?
My second challenge, is how can I run this with aead-cipher-2022 enabled? I can run ssserver with "method": "2022-blake3-aes-256-gcm" in the config and it runs, but I can't get any client to actually connect and use it.
Any help would be greatly appreciated.
PS I did try: "curl -L -m 3 example.com"
and got this: curl: (28) Operation timed out after 3006 milliseconds with 0 bytes received
Beta Was this translation helpful? Give feedback.
All reactions