Closed wouam31200 closed 8 months ago
Hi, thanks for reporting. New version fixing the issue will be available shortly.
v0.2.7 should fix this issue (please confirm), along with a few additional bugs.
BTW the command iptables -L
shows you the default table which is called filter
. geoip-shell uses an "earlier" table called mangle
. To see the rules in iptables directly (which will also display an additional chain used to select the traffic from your network interface ens3
), use the command iptables -L -t mangle
. If you want to see network interfaces the rules apply to, use iptables -vL -t mangle
. For ipv6 rules, use same commands, except replace iptables
with ip6tables
.
Hi, I just removed v0.2.6 and installed v0.2.7 Everything went well, I'm waiting tonight to see if the cron is working correctly.
Thank you so much
Perfect, please let me know. Also if you want to test right away, you can temporarily set the update schedule to ' ' which will run an update every minute. The command is `geoip-shell schedule -s " ". You can later change the schedule back to default with this command:
geoip-shell schedule -s "15 4 *"`. Ripe updates ip lists once a day and geoip-shell will not download and apply an ip list until it's actually updated, so till the next update on the server, you should see log messages like this
geoip-shell-run.sh: Starting action 'update'.
geoip-shell-fetch.sh: Ip lists '...' are already up-to-date with the RIPE server.
geoip-shell-run.sh: Firewall reconfiguration isn't required.
Also when updating to a new version, you don't really need to manually run the uninstaller, although it's not a bad practice. The -install script automatically uninstalls an existing version (if any) before going ahead with the installation.
In the meanwhile, I have verified that v0.2.7 fixes the issue on my iptables-based Debian system.
Hi, Great the problem is solved on ubuntu! thanks again
Hi, Yesterday I installed it to test on a VPS under Ubuntu.
You did a great job!
This morning I wanted to check if the cron went well and I got this error:
Thanks again for your work!!