combined.sh errors in CentOS 7 #40
Replies: 19 comments
-
Hi, First please type in terminal:
and let me know what it shows. Also type:
to get rid of the ipsets that the first run of the script created. Let me know and we'll take it from there. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
It seems that the iptables rules are in effect at least partially and are using the ipsets, which is strange because the script wipes the rules in mangle table before applying the rules in the script. A few more questions: Have you set up any other ipsets for your own projects? perhaps in the filter table? Type:
and see if the ipsets are there. Do you see any other ipsets beside tor-ddos, tor-ddos6, allow-list, allow-list6 and tor-authorities? type:
if it shows 20, the rule is already applied. If it shows 60 then edit your sysctl.conf using nano or vi
add:
and save the file. Then type:
That should reload the conf and apply the setting. Let me know if you have any other ipsets or if you have applied any specific iptables rules for your other apps or projects and we'll go to the next step. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your help!
|
Beta Was this translation helpful? Give feedback.
-
Okay, the rules were applied, at least partially. The easiest way to reset all the iptables rules to the original state in CentOS is to type:
then
That should clean everything. edit combined.sh and comment out line 9 "echo 20 > /proc/sys/net/ipv4/tcp_fin_timeout" by putting a # to the left, save and run the script. IT should work. As for the fin_timeout, I'm not sure why it shouldn't be there if you're running an unmodified CentOS 7. Do the above and let me know if the script works. We can try to figure out the fin_timeout next. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure about "unmodified" since it's a webhost-provided image... In fact I'm getting "command not found" on firewall-cmd, which could mean firewall is not installed... With this webhost I'm provided an external firewall controlled from their panel, so this kind of makes sense. What would be the best course of action in this case? |
Beta Was this translation helpful? Give feedback.
-
Okay so it is modified. Try this:
See if ipset destroy works after that. |
Beta Was this translation helpful? Give feedback.
-
Seems like it did work. ipset -L is returning nothing. |
Beta Was this translation helpful? Give feedback.
-
Sounds good. Now edit combined.sh as I suggested above and comment out the line and run the script. |
Beta Was this translation helpful? Give feedback.
-
Got this: net.ipv4.ip_local_port_range = 10000 65000 |
Beta Was this translation helpful? Give feedback.
-
It seems that your iptables may not even have the mangle table?? Not sure why or how much they've modified the OS. Try this:
see if it returns any listings. |
Beta Was this translation helpful? Give feedback.
-
-P PREROUTING ACCEPT |
Beta Was this translation helpful? Give feedback.
-
I obviously don't know enough, but maybe I can just install all the missing stuff to be sure? |
Beta Was this translation helpful? Give feedback.
-
I don't see any of the conntrack rules. It seems that your iptables doesn't accept any conntrack rules which is the basis for our rule sets. try
to see the version. |
Beta Was this translation helpful? Give feedback.
-
iptables v1.4.21 Got it. Well, if this is beyond reasonable help because of how hacked the OS is, I can't expect you to keep guessing. Unless I can just update/install the missing stuff and go around again? |
Beta Was this translation helpful? Give feedback.
-
The iptables version is correct. That's what you get in CentOS 7. I'm really not sure why it's not accepting conntrack rules. Do you have this file:
|
Beta Was this translation helpful? Give feedback.
-
Yes, it's empty though. |
Beta Was this translation helpful? Give feedback.
-
If Tor is running that file should have thousands of lines and be updating constantly. To be honest with you I'm out of guesses. Not sure how your system is set up and how to begin troubleshooting it. Your options are either to follow up with your provider, they may have some clues as how the system is set up and may be they can tell you what's missing and whether it's possible to get it working by installing a package or two. Or perhaps ask them for a standard version of CentOS if it's possible. I'm sorry I couldn't be of much help. Still if you find some sort of an answer and want to run it by me, I'll be glad to answer any questions you may have. |
Beta Was this translation helpful? Give feedback.
-
Absolutely. Thank you very much for your help. This should honestly just work, up until now I was simply unaware I had a heavily modified OS here. I'll investigate and get back to you, if only to say things are fiiine. |
Beta Was this translation helpful? Give feedback.
-
Hi, I run two relays on different OSs. combined.sh executed fine in Ubuntu, but in CentOS 7 I'm getting this output:
net.ipv4.ip_local_port_range = 10000 65000
./combined.sh: line 9: /proc/sys/net/ipv4/tcp_fin_timeout: No such file or directory
ipset v7.1: Set cannot be created: set with the same name already exists
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ipset v7.1: Set cannot be created: set with the same name already exists
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
What can I do to make this work?
Beta Was this translation helpful? Give feedback.
All reactions