Skip to content
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

Open
Jon811 opened this issue Dec 22, 2024 · 11 comments
Open

After starting SSClash port forwarding not works #4

Jon811 opened this issue Dec 22, 2024 · 11 comments

Comments

@Jon811
Copy link

Jon811 commented Dec 22, 2024

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?

@zerolabnet
Copy link
Owner

Check what interface you are using for WAN (command: ip a). Most likely it is not in the list I made, add the interface to the RESERVED_IFACE array in the nft.conf file.

@Jon811
Copy link
Author

Jon811 commented Dec 23, 2024

In my case pppoe-wan is WAN interface, so "ppp* mask had to work, but it's not. adding "pppoe-wan" is not worked.
13: pppoe-wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN qlen 3
link/ppp
inet ... peer ******/32 scope global pppoe-wan
valid_lft forever preferred_lft forever

@Jon811
Copy link
Author

Jon811 commented Dec 24, 2024

Is there a way to debug this chains?

@zerolabnet
Copy link
Owner

I have no idea what the cause is. "ppp*" really should cover your WAN connection.

@absid89
Copy link

absid89 commented Jan 10, 2025

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

@Jon811
Copy link
Author

Jon811 commented Jan 10, 2025

In /opt/clash/nft.conf adding
oifname $RESERVED_IFACE return
ip saddr LANIP tcp sport LANPort return
#Redirect traffic to TPROXY
Helped me

@absid89
Copy link

absid89 commented Jan 11, 2025

In /opt/clash/nft.conf adding oifname $RESERVED_IFACE return ip saddr LANIP tcp sport LANPort return #Redirect traffic to TPROXY Helped me

thx this works for me

upd:
for me the request locally to external address did not work, had to add more rules

add in prerouting and output:
ip daddr != 192.168.1.0/24 tcp dport PORT return
(192.168.1.0 if needed replace with your local network)

@absid89
Copy link

absid89 commented Jan 11, 2025

@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

@ma3uk
Copy link

ma3uk commented Jan 13, 2025

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.

@fildunsky
Copy link

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?

@ma3uk
Copy link

ma3uk commented Jan 14, 2025

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 к серваку подключаться, если отключить его или подключиться с другой точки доступа, то всё заходит.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants