-
Notifications
You must be signed in to change notification settings - Fork 564
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
A minor redis issue with Openwrt/Lede build (Mips32 arch) #40
Comments
INTANGD daemon exits after that last line.(no errors at the log, doest say that it actually exited, just stops after connecting to tcp dns server) Redis server still runs |
Can someone help me for the iptables rules (For Openwrt) ? I have no problem running it on my router but cant figure out the proper rules. |
You may want to try my kernel-space implementation |
Thank you, i`m going to study this. This page was very useful > https://github.com/LGA1150/netfilter-spooftcp/wiki/Usage-Examples |
I‘m using INTANG to test if I can visit sites blocked by GF, but I can not successfully, could you share the whole steps about using INTANG and setting the strategy? |
I no longer use INTANG but at the time i was using it, the strategy i used was the 5. Netfilter-spooftcp is much easier to use and it works at the router level so one does`t need to apply any rules/software to the connected devices. My router now opens all restricted sites, you just need to compile a kernel module and an iptables extension. If you struggle with the iptables rules afterwards, i can send the ones i use here. |
Hello,
I have successfully built the mips32 binary for the Lede 17.01.4 but when I fire it up, it just hangs there with a redis error at the log.
What might be the reason for this ?
INTANG_0-1_mips_mips32.zip
![intang1](https://user-images.githubusercontent.com/4885199/47267441-8c20f100-d54c-11e8-9ec8-2ced7991fd27.png)
![intang2](https://user-images.githubusercontent.com/4885199/47267444-9511c280-d54c-11e8-859a-9ce52e3f37ff.png)
intangd.zip
The text was updated successfully, but these errors were encountered: