Country block doesnt work for me anymore since 2.0 release
-
Embedded?
-
Nope. 386 build
-
Can you run```
/usr/local/www/packages/countryblock/execute.sh -
Can you run```
/usr/local/www/packages/countryblock/execute.sh[2.0-RELEASE][root@sentinel.localdomain]/root(1): /usr/local/www/packages/countr yblock/execute.sh
1 table deleted.
107
16
rm: /tmp/rules.debug.tmp: No such file or directory
rm: /tmp/rules.debug.tmp: No such file or directory
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154 -
That looks normal to me. Are you sure you can get it working?
-
This is in my log
Oct 1 21:34:35 root: Countryblock was found not running
-
That doesn't mean that you can't get countryblock running. Can you get it running in your GUI? screenshot?
-
OK, gui says its running. I tested some proxies and i think i am good now. thanks for all the help. Now if I can get ip-blocklist i will be set
-
What changed from when it was not working to working???
-
To get rid of the error rm: /tmp/rules.debug.tmp: No such file or directory,
Edit /usr/local/www/packages/countryblock/execute.sh
Find the lines
rm /tmp/rules.debug.tmpReplace With
if [ -f /tmp/rules.debug.tmp ] then rm /tmp/rules.debug.tmp fiStill looking to see why the error log is showing that countryblock is not running when pfctl shows that it is…
-
Still looking to see why the error log is showing that countryblock is not running when pfctl shows that it is…
Just tested some sites:
www.visitkorea.or.kr
211.178.9.106www.chinadaily.com.cn
209.177.94.85For testing China and Korea are enabled in CountryBlock, but I can still get to them. Something isn't working right even with pfctl listing it is. I have reloaded CountryBlock, and have tried it on a fresh system.
PFSense 2.0 i386
-
Are you sure those IPs are in the country list that you have checked? Even if those IPs are in a country they could belong to another list.
I know countryblock works great on 2.0 but we have another package coming out for pfsense 2.0 called pfblocker. This will replace countryblock on 2.0. The new package will be released sometime in the near future.
-
Should CountryBlock block pings to an IP that is guranteed to be on the list? Those two were examples that I thought might be on the list, but I have a few IP's that are physically in the countries I am blocking.
Since time is relative, what kind of estimate do you give for "near future?" ;D
-
It will block all traffic.
pfblocker 1.4 is only BETA but is fully functional and is available now.