Ip Filter: How to block a range of IP ?

[nqk18469]

Recently I put up a small FTP server, running under the Xp64 to exchange files between some family here in Japan and relatives who live in Brazil.

It happens about 2 times already, I found an "intruder" tried login as "administrator" on the server. Obviously I have a "Banned" them and putting their IP's in the filter of FileZilla:



I got the range of IP possibly used by the provider, the "intruders" and was wanting to block their IP's:
65.80.0.0 to 65.83.255.255
and
60.166.0.0 to 60.175.255.255.

Following the guidelines in another forum, set up as follows:
65.80.0.0 to 65.83.255.255

Code: Select all

65.80.*.*
65.81.*.*
65.82.*.*
65.83.*.*

To block the IP's between 60.166.0.0 to 60.175.255.255, there another way to do it without being the way down?

60.166.*.*
60.167.*.*
60.168.*.*
60.169.*.*
60.170.*.*
60.171.*.*
60.172.*.*
60.173.*.*
60.174.*.*
60.175.*.*


P.S.:

Sorry, but I don't speak English.
I used the Google Tranlsator to post this topic.

[botg]

Try 60.166.0.0-60.175.255.255

[nqk18469]

Try 60.166.0.0-60.175.255.255

Thank you very much !!

[JAY-_-Z]

Sorry for using this thread, but I have the same question.

I have FZ Server 0.9.39. I put in the range like "60.166.0.0-60.175.255.255" without the quotation marks. But it won't work. Always the message: Invalid IP address/range/mask.

But what is my mistake? I put instead of "-" a "/" or with blanks. Always the same message.

Thanks for helping and greets,

JAY.

[boco]

Since server version 0.9.38, ranges entered like that are no more supported. I will quote the relevant piece of the changelog:

Range, wildcard, regular expression and dot-decimal notation subnet IP address filters have been removed. These filter rules need to be recreated using CIDR notation.

You will need to enter your IP ranges in CIDR notation. Only that and single IPs are supported.

Of course features are not removed just for fun. It has to do with the new IPv6 support.

[JAY-_-Z]

Thanks for your answer.
But what can I do now, to block those IPs i won't let connect? Wildcards are not allowed too?

[boco]

But what can I do now, to block those IPs i won't let connect?

Enter the range in CIDR notation. Needs two entries.

Code: Select all

60.166.0.0/15
60.168.0.0/13

Wildcards are not allowed too?

No.

But actually you can use the following website (I did, too, for your range): http://ip2cidr.com/ .

@botg: Would it be hard to get a small converter into the server? Or at least a link to the website?

[botg]

Not everything can be converted into CIDR, e.g. *.23.*.42 would require 65k lines or so. Such filters make no sense, but as they were possible, users must have had them. Regex based filters cannot be converted into CIDR at all.

Long story short, a converter would be much work and would fail all too easily.


I won't link to that website as it contains user tracking (Google) and advertisement (Google).

[JAY-_-Z]

@boco: Damn, thank you. I do not understand any of the senseless IP6... But the converter does^^

I hope it works...

Thanks to you all and good night

[boco]

I do not understand any of the senseless IP6... But the converter does^^

CIDR is not IPv6.

Example of an IPv6 address:

2001:459a:2240:afcd:202:7aff:fe30:cdfe

Try to remember that. If you have Windows Vista or Windows 7, you already have at least a link local IPv6 address per network interface, possibly without even knowing it.