I came against a new problem. I was trying to install votifier but it wont work.
I tried to open my ports and I set up some rules:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp – !localhost.localdomain anywhere tcp dpt:8192
DROP tcp – !omgserv-66923 anywhere tcp dpts:25566:25580
ACCEPT tcp – anywhere anywhere tcp dpt:8192
If doing so makes votifier work, you know the mod itself is working. If it doesn’t work, then your problem lies somewhere other than the firewall.
If the mod is working, you can then reapply each rule in succession until it stops working and you’ll find out which rule was the offending one. Based on the rules you’re showing though, unless votifier is in the DROP tcp rule (which it probably isn’t), it suggests the problem isn’t the firewall to begin with.
^ this means ‘let everything through’ unless it’s dropped in a rule below. In other words, it’s probably not the firewall, but instead the service that you’re running is probably not reaching your server (port forwarding in your router is most likely).
Opening ports has nothing to do with whether or not cracked clients can join. Ports have to be open to let in legitimate traffic too. You and I have been over this before.
There is a really easy fix for that. In your server.properties set this setting to true: online-mode=true
This setting cheks EVERY user agains Mojang (and Minecraft’s) user base to see if the client has a valid mojang username and login. This also means you have to demand that everyone connecting yo your server has an original, bougth client, even though it has been modded.
In addition to onlinemode, activate white-listing: white-list=true
This means that no one other than the client’s you have authorized, and that has a valid Mojang Account, can access your server.
I would most definately say that a game all of you play enough to need your own private server, at least when you have been playing it for this long, is worth the price to buy it.