Forum :: Lounge :: IP Blocking?

is it possible to block someones IP from the start of it? For example 74.? is it possible to ban that part? And possibly blocking there PC Name or something?

What is this?! Aaahh.. I'd love it if you were more specific. (sadface)

Are you trying to block an IP from a site of yours? Are you trying to block if from your e-mail address? Private server? Router? Network? (frustratedface)

---
"Natalia"

I think he means eoserv. And yes that's possible if you mean eoserv.

Hollow posted: (9th Sep 2011, 11:24 am)

I think he means eoserv. And yes that's possible if you mean eoserv.

If he means EOserv, the topic should be under EOserv.

---
"Natalia"

Natalia posted: (9th Sep 2011, 12:34 pm)

Hollow posted: (9th Sep 2011, 11:24 am)

I think he means eoserv. And yes that's possible if you mean eoserv.

If he means EOserv, the topic should be under EOserv.

Some people are retarded you know. (I don't mean lolss just in the public) And people might be mistaken about where they post, Or he might actually mean something else.

There's several standard ways to represent the range of IP addresses from 74.0.0.0 to 74.255.255.255. They may or may not come with the implication that it specifies the address range of an actual network (which also implies that the first and last addresses have special meaning). For the purposes of banning addresses, it's not really relevant, but then again, you probably don't want to ban a block of IP addresses which spans multiple networks.

The most common form is CIDR, where you specify the range simply as 74.0.0.0/8 -- The address on the left usually specifies the network identity address, and the 8 on the right represents the number of bits in an address from the most significant bit an address has to match to the network identity to be considered part of the network, which happens exactly cover one octet on this case, other common values are 16, 24 and 32 to cover 2, 3 or 4 octets. The majority of networks, however, aren't assigned in terms of classes (e.g. a small network could be 10.1.2.208 to 10.1.2.224, represented by 10.1.2.216/28). The "/8" part can be converted to the subnet mask 255.0.0.0 (0xFF000000, first 8 bits set) covered below:

That CIDR bit range can be mapped directly a "subnet mask", instead. A count of "28" means an address with 28 '1' bits, followed by '0' bits: 255.255.255.240 (0xFFFFFFF0), which is then used to mask an address, e.g. 10.1.2.212 (0x0A0102D4), with bitwise operations: 0xFFFFFFF0 & 0xA0102D4 = 0xA0102D0, or 10.1.2.208, which is the network identity address.

You can usually do a network lookup to find information on public Internet networks if you're looking to ban an ISP or country. This also only allows specifying address blocks which actually make sense as networks. Though you're probably doing something wrong if you need to hold an exact range that isn't aligned to a network, just holding the two addresses and doing a less than [or equal to] compare with them both on a given third address is possible, and maybe more human friendly.

Sausage posted: (9th Sep 2011, 01:23 pm)

There's several standard ways to represent the range of IP addresses from 74.0.0.0 to 74.255.255.255. They may or may not come with the implication that it specifies the address range of an actual network (which also implies that the first and last addresses have special meaning). For the purposes of banning addresses, it's not really relevant, but then again, you probably don't want to ban a block of IP addresses which spans multiple networks.

The most common form is CIDR, where you specify the range simply as 74.0.0.0/8 -- The address on the left usually specifies the network identity address, and the 8 on the right represents the number of bits in an address from the most significant bit an address has to match to the network identity to be considered part of the network, which happens exactly cover one octet on this case, other common values are 16, 24 and 32 to cover 2, 3 or 4 octets. The majority of networks, however, aren't assigned in terms of classes (e.g. a small network could be 10.1.2.208 to 10.1.2.224, represented by 10.1.2.216/28). The "/8" part can be converted to the subnet mask 255.0.0.0 (0xFF000000, first 8 bits set) covered below:

That CIDR bit range can be mapped directly a "subnet mask", instead. A count of "28" means an address with 28 '1' bits, followed by '0' bits: 255.255.255.240 (0xFFFFFFF0), which is then used to mask an address, e.g. 10.1.2.212 (0x0A0102D4), with bitwise operations: 0xFFFFFFF0 & 0xA0102D4 = 0xA0102D0, or 10.1.2.208, which is the network identity address.

You can usually do a network lookup to find information on public Internet networks if you're looking to ban an ISP or country. This also only allows specifying address blocks which actually make sense as networks. Though you're probably doing something wrong if you need to hold an exact range that isn't aligned to a network, just holding the two addresses and doing a less than [or equal to] compare with them both on a given third address is possible, and maybe more human friendly.

I wonder if he'll understand any of that.

Sausage posted: (9th Sep 2011, 01:23 pm)

There's several standard ways to represent the range of IP addresses from 74.0.0.0 to 74.255.255.255. They may or may not come with the implication that it specifies the address range of an actual network (which also implies that the first and last addresses have special meaning). For the purposes of banning addresses, it's not really relevant, but then again, you probably don't want to ban a block of IP addresses which spans multiple networks.

The most common form is CIDR, where you specify the range simply as 74.0.0.0/8 -- The address on the left usually specifies the network identity address, and the 8 on the right represents the number of bits in an address from the most significant bit an address has to match to the network identity to be considered part of the network, which happens exactly cover one octet on this case, other common values are 16, 24 and 32 to cover 2, 3 or 4 octets. The majority of networks, however, aren't assigned in terms of classes (e.g. a small network could be 10.1.2.208 to 10.1.2.224, represented by 10.1.2.216/28). The "/8" part can be converted to the subnet mask 255.0.0.0 (0xFF000000, first 8 bits set) covered below:

That CIDR bit range can be mapped directly a "subnet mask", instead. A count of "28" means an address with 28 '1' bits, followed by '0' bits: 255.255.255.240 (0xFFFFFFF0), which is then used to mask an address, e.g. 10.1.2.212 (0x0A0102D4), with bitwise operations: 0xFFFFFFF0 & 0xA0102D4 = 0xA0102D0, or 10.1.2.208, which is the network identity address.

You can usually do a network lookup to find information on public Internet networks if you're looking to ban an ISP or country. This also only allows specifying address blocks which actually make sense as networks. Though you're probably doing something wrong if you need to hold an exact range that isn't aligned to a network, just holding the two addresses and doing a less than [or equal to] compare with them both on a given third address is possible, and maybe more human friendly.

TL;DR
If you want to block all addresses that start with "74", you would specify 74.0.0.0/8 or 74.0.0.0 with a subnet mask of 255.0.0.0 (I think eoserv likes /8 better).

---
class EOSERV {
Programmer | Oldbie
Open source EO Client: https://github.com/ethanmoffat/EndlessClient
};

Didn't you mention DDoS attacks being directed towards you in another thread? Keep in mind that blocking/firewalling IPs does NOT generally stop those types of attacks.

---
Wish upon a star!

Hollow posted: (9th Sep 2011, 11:24 am)

I think he means eoserv. And yes that's possible if you mean eoserv.

No I didn't.
And Sausage thanks for a useful reply.

lolss posted: (9th Sep 2011, 04:45 pm)

Hollow posted: (9th Sep 2011, 11:24 am)

I think he means eoserv. And yes that's possible if you mean eoserv.

No I didn't.
And Sausage thanks for a useful reply.

Than be more specific next time :3

Hollow posted: (9th Sep 2011, 04:47 pm)

lolss posted: (9th Sep 2011, 04:45 pm)

Hollow posted: (9th Sep 2011, 11:24 am)

I think he means eoserv. And yes that's possible if you mean eoserv.

No I didn't.
And Sausage thanks for a useful reply.

Than be more specific next time :3

Alright sorry, but this topic doesn't matter anymore thanks for the help guys.

ethanmoffat posted: (9th Sep 2011, 03:34 pm)

Sausage posted: (9th Sep 2011, 01:23 pm)

There's several standard ways to represent the range of IP addresses from 74.0.0.0 to 74.255.255.255. They may or may not come with the implication that it specifies the address range of an actual network (which also implies that the first and last addresses have special meaning). For thepurposes of banning addresses, it's not really relevant, but then again, you probably don't want to ban a block of IP addresses which spans multiple networks.

The most common form is CIDR, where you specify the range simply as 74.0.0.0/8 -- The address on the left usually specifies the network identity address, and the 8 on the right represents the number of bits in an address from the most significant bit an address has to match to the networkidentity to be considered part of the network, which happens exactly cover one octet on this case, other common values are 16, 24 and 32 to cover 2, 3 or 4 octets. The majority of networks, however, aren't assigned in terms of classes (e.g. a small network could be 10.1.2.208 to 10.1.2.224,represented by 10.1.2.216/28). The "/8" part can be converted to the subnet mask 255.0.0.0 (0xFF000000, first 8 bits set) covered below:

That CIDR bit range can be mapped directly a "subnet mask", instead. A count of "28" means an address with 28 '1' bits, followed by '0' bits: 255.255.255.240 (0xFFFFFFF0), which is then used to mask an address, e.g. 10.1.2.212 (0x0A0102D4), with bitwise operations: 0xFFFFFFF0 & 0xA0102D4 =0xA0102D0, or 10.1.2.208, which is the network identity address.

You can usually do a network lookup to find information on public Internet networks if you're looking to ban an ISP or country. This also only allows specifying address blocks which actually make sense as networks. Though you're probably doing something wrong if you need to hold an exact rangethat isn't aligned to a network, just holding the two addresses and doing a less than [or equal to] compare with them both on a given third address is possible, and maybe more human friendly.

TL;DR
If you want to block all addresses that start with "74", you would specify 74.0.0.0/8 or 74.0.0.0 with a subnet mask of 255.0.0.0 (I think eoserv likes /8 better).

EOSERV doesn't like either better since it doesn't support IP address ranges.