-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After starting SSClash port forwarding not works #4
Comments
Check what interface you are using for WAN (command: |
In my case pppoe-wan is WAN interface, so "ppp* mask had to work, but it's not. adding "pppoe-wan" is not worked. |
Is there a way to debug this chains? |
I have no idea what the cause is. "ppp*" really should cover your WAN connection. |
the same problem. I use port forwarding for telegram webhook, my wan is also pppoe-wan. and nothing helps to make it work until you disable the service |
In /opt/clash/nft.conf adding |
thx this works for me upd: add in prerouting and output: |
@zerolabnet maybe there is a possibility to put this in the config or generally take it into account during automatic generation of the config if there is one |
Does anyone know how to solve the problem with connecting to external SSH? I cannot connect to my server unless I route it through a proxy; otherwise, SSH connection requests are blocked. |
Странно, у меня никогда таких проблем нигде не было по SSH заходит на любые серверы при работающем Clash. Может настройки фаерволла на сервере специфические или ban IP? |
Именно после установки SSClash перестало по SSH к серваку подключаться, если отключить его или подключиться с другой точки доступа, то всё заходит. |
After starting SSClash port forwarding not works. So my home server is not accessible from outside. How to make, that requests from outside to some port comes into lan device directly?
The text was updated successfully, but these errors were encountered: