The issue with the iptables rules not being loaded has to do with a script not being installed. On Debian it is iptables-persistent, and seems to be the same for Ubuntu. Once that is installed, you can save the rules you want reloaded by running:
iptables-save > /etc/iptables/rules.v4 ip6tables-save > /etc/iptables/rules.v6 That is the default location for the files that the init.d script will load at startup. Hope this helps and let me know if you have any more questions or I got anything wrong. Damian (The other one) On Sun, Dec 6, 2015 at 8:53 AM ZEROF <secur...@netmajstor.com> wrote: > David, low ports numbers are not good idea, he can have same issues. For > my firewall i need to use something more then 9000 to make my exit/relay to > work with my ISP. > > On 6 December 2015 at 17:46, David Schulz <c...@fu110.de> wrote: > >> Try other ports or ask the hoster, if he blocks ports?! Or try 80 and >> 443, if there are free at your server. >> >> ----------------------- >> Mit freundlichen Grüßen / Yours sincerely >> >> David Schulz <c...@fu110.de> >> >> >> Am 06.12.2015 um 17:15 schrieb Kurt Besig: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Thanks again for all the support everyone has bee extremely helpful. >>> So, I reinstalled the OS on the VPS: lsb_release -d >>> Description: Ubuntu 14.04.3 LTS >>> uname -r 2.6.32-042stab102.9 >>> >>> Finally solved all the permissions problems, paths are correct, tor >>> and arm open properly. >>> The problem now boils down to this: >>> The VPS isn't allowing Ports 9001 and 9030 >>> Should I investigate further getting my iptables up and running or >>> just contact the admin and have them allow the ports? >>> As I mentioned previously even after saving the tables upon reboot >>> iptables -L shows no rules, the file is empty. >>> >>> :~$ iptables -L >>> Chain INPUT (policy ACCEPT) >>> target prot opt source destination >>> >>> Chain FORWARD (policy ACCEPT) >>> target prot opt source destination >>> >>> Chain OUTPUT (policy ACCEPT) >>> target prot opt source destination >>> Any further suggestions would be appreciated. >>> >>> Thanks >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.22 (MingW32) >>> >>> iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs >>> HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ >>> 8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5 >>> uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb >>> KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ >>> xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s= >>> =uoin >>> -----END PGP SIGNATURE----- >>> _______________________________________________ >>> tor-relays mailing list >>> tor-relays@lists.torproject.org >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >>> >> >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays@lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> > > > > -- > http://www.backbox.org > http://www.pentester.iz.rs > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
