#cidr — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cidr, aggregated by home.social.
-
Как технически устроена DPI-фильтрация у российских провайдеров и как её детектировать: разбор open-source инструментов
В последние пару лет любой пользователь рунета научился различать “интернет дома” и “интернет в гостях у бабушки”. На одном провайдере YouTube открывается, на другом нет. Это ощущается как непредсказуемость, но за каждой такой деградацией стоят вполне конкретные технические механизмы. Запустил open-source инструмент dpi-checkers на трёх своих подключениях, разобрался с методами TCP 16-20 и CIDR-вайтлистами и расскажу, что технически происходит с вашим трафиком на L4 — от SNI-фильтрации до QUIC-блокировок.
https://habr.com/ru/articles/1033456/
#DPI #deep_packet_inspection #TCP #TLS #SNI #CIDR #цензура #OONI #сетевая_фильтрация
-
Как технически устроена DPI-фильтрация у российских провайдеров и как её детектировать: разбор open-source инструментов
В последние пару лет любой пользователь рунета научился различать “интернет дома” и “интернет в гостях у бабушки”. На одном провайдере YouTube открывается, на другом нет. Это ощущается как непредсказуемость, но за каждой такой деградацией стоят вполне конкретные технические механизмы. Запустил open-source инструмент dpi-checkers на трёх своих подключениях, разобрался с методами TCP 16-20 и CIDR-вайтлистами и расскажу, что технически происходит с вашим трафиком на L4 — от SNI-фильтрации до QUIC-блокировок.
https://habr.com/ru/articles/1033456/
#DPI #deep_packet_inspection #TCP #TLS #SNI #CIDR #цензура #OONI #сетевая_фильтрация
-
Как технически устроена DPI-фильтрация у российских провайдеров и как её детектировать: разбор open-source инструментов
В последние пару лет любой пользователь рунета научился различать “интернет дома” и “интернет в гостях у бабушки”. На одном провайдере YouTube открывается, на другом нет. Это ощущается как непредсказуемость, но за каждой такой деградацией стоят вполне конкретные технические механизмы. Запустил open-source инструмент dpi-checkers на трёх своих подключениях, разобрался с методами TCP 16-20 и CIDR-вайтлистами и расскажу, что технически происходит с вашим трафиком на L4 — от SNI-фильтрации до QUIC-блокировок.
https://habr.com/ru/articles/1033456/
#DPI #deep_packet_inspection #TCP #TLS #SNI #CIDR #цензура #OONI #сетевая_фильтрация
-
Как технически устроена DPI-фильтрация у российских провайдеров и как её детектировать: разбор open-source инструментов
В последние пару лет любой пользователь рунета научился различать “интернет дома” и “интернет в гостях у бабушки”. На одном провайдере YouTube открывается, на другом нет. Это ощущается как непредсказуемость, но за каждой такой деградацией стоят вполне конкретные технические механизмы. Запустил open-source инструмент dpi-checkers на трёх своих подключениях, разобрался с методами TCP 16-20 и CIDR-вайтлистами и расскажу, что технически происходит с вашим трафиком на L4 — от SNI-фильтрации до QUIC-блокировок.
https://habr.com/ru/articles/1033456/
#DPI #deep_packet_inspection #TCP #TLS #SNI #CIDR #цензура #OONI #сетевая_фильтрация
-
One Open-source Project Daily
CIDR Calculator and Subnetting Visualizer
https://github.com/yuvadm/cidr.xyz
#1ospd #opensource #cidr #cidrrange #hacktoberfest #ip #javascript #network #nextjs #react -
One Open-source Project Daily
CIDR Calculator and Subnetting Visualizer
https://github.com/yuvadm/cidr.xyz
#1ospd #opensource #cidr #cidrrange #hacktoberfest #ip #javascript #network #nextjs #react -
One Open-source Project Daily
CIDR Calculator and Subnetting Visualizer
https://github.com/yuvadm/cidr.xyz
#1ospd #opensource #cidr #cidrrange #hacktoberfest #ip #javascript #network #nextjs #react -
One Open-source Project Daily
CIDR Calculator and Subnetting Visualizer
https://github.com/yuvadm/cidr.xyz
#1ospd #opensource #cidr #cidrrange #hacktoberfest #ip #javascript #network #nextjs #react -
One Open-source Project Daily
CIDR Calculator and Subnetting Visualizer
https://github.com/yuvadm/cidr.xyz
#1ospd #opensource #cidr #cidrrange #hacktoberfest #ip #javascript #network #nextjs #react -
Command-and-control IPv4 map, 2026-02-26 to 2026-03-11 #CIDR
https://abjuri5t.github.io/SarlackLab/43.249.172[.]0/22
23.248.208[.]0/21
156.234.56[.]0/23
178.16.52[.]0/22
103.41.6[.]0/23
158.94.208[.]0/22
43.240.239[.]0/24
103.39.16[.]0/22
185.213.60[.]0/23
23.226.48[.]0/23 -
Command-and-control IPv4 map, 2026-02-24 to 2026-03-09 #CIDR
https://abjuri5t.github.io/SarlackLab/43.249.172[.]0/22
23.248.208[.]0/21
178.16.52[.]0/22
23.226.58[.]0/23
156.234.56[.]0/23
43.240.239[.]0/24
103.39.16[.]0/22
158.94.208[.]0/22
185.213.60[.]0/23
23.226.48[.]0/23 -
Command-and-control IPv4 map, 2026-02-20 to 2026-03-05 #CIDR
https://abjuri5t.github.io/SarlackLab/43.249.172[.]0/22
178.16.52[.]0/22
23.226.58[.]0/23
156.234.56[.]0/23
158.94.208[.]0/22
43.240.239[.]0/24
103.39.16[.]0/22
23.226.48[.]0/23
23.248.208[.]0/21
103.41.6[.]0/23 -
Command-and-control IPv4 map, 2026-02-12 to 2026-02-25 #CIDR
https://abjuri5t.github.io/SarlackLab/178.16.52[.]0/22
158.94.208[.]0/22
91.92.240[.]0/22
148.178.64[.]0/19
207.56.192[.]0/19
102.117.128[.]0/18
148.178.32[.]0/19
45.114.106[.]0/24
156.234.94[.]0/24 -
For the first time since #CIDR moved to Chaminade, my arrival has not been delayed by a landslide.
-
@kilostere@kilostere @[email protected] @[email protected] @[email protected] @[email protected]
WorldStream.com is hereby banned from any of my services for being inresponsible and the network of185.184.192.0/24are blacklisted all over.
#blacklist #banned #networksecurity #cidr #firewall #WorldStream #noc #abuse -
Ever tried to find one specific book from inside a ginormous, single-roomed library? That's a network without subnets. Subnetting (FLSM/VLSM) is like having sections, floors, and aisles. CIDR notation (/24) is the library plan. It brings order to chaos, making routing efficient and secure. I finally "got it" when I started thinking binary. It's gorgeous, I promise!
-
Command-and-control IPv4 map, 2025-08-30 to 2025-09-12 #CIDR
https://abjuri5t.github.io/SarlackLab/154.89.184[.]0/21
104.233.252[.]0/22
178.16.52[.]0/22
45.192.192[.]0/20
38.32.0[.]0/11
124.220.0[.]0/14
43.136.0[.]0/13
38.128.0[.]0/9
47.92.0[.]0/14
3.64.0[.]0/12 -
Command-and-control IPv4 map, 2025-08-22 to 2025-09-04 #CIDR
https://abjuri5t.github.io/SarlackLab/104.233.252[.]0/22
178.16.52[.]0/22
124.220.0[.]0/14
43.136.0[.]0/13
38.32.0[.]0/11
45.192.192[.]0/20
38.128.0[.]0/9
47.92.0[.]0/14
3.64.0[.]0/12
202.95.8[.]0/21
101.42.0[.]0/15 -
net/netip в Go 1.25
Привет, Хабр! Go ценят за предсказуемость и простые решения в стандартной библиотеке, а в сервисах чаще всего упираемся в IP, разбор host:port, CIDR и сериализацию. Сегодня это удобно закрывается стандартным net/netip : компактные value-типы, корректный парсинг адресов и портов, работа с зонами, проверка принадлежности сетям и быстрые операции без лишних аллокаций. В статье рассмотрим этот пакет подробнее.
-
net/netip в Go 1.25
Привет, Хабр! Go ценят за предсказуемость и простые решения в стандартной библиотеке, а в сервисах чаще всего упираемся в IP, разбор host:port, CIDR и сериализацию. Сегодня это удобно закрывается стандартным net/netip : компактные value-типы, корректный парсинг адресов и портов, работа с зонами, проверка принадлежности сетям и быстрые операции без лишних аллокаций. В статье рассмотрим этот пакет подробнее.
-
net/netip в Go 1.25
Привет, Хабр! Go ценят за предсказуемость и простые решения в стандартной библиотеке, а в сервисах чаще всего упираемся в IP, разбор host:port, CIDR и сериализацию. Сегодня это удобно закрывается стандартным net/netip : компактные value-типы, корректный парсинг адресов и портов, работа с зонами, проверка принадлежности сетям и быстрые операции без лишних аллокаций. В статье рассмотрим этот пакет подробнее.
-
net/netip в Go 1.25
Привет, Хабр! Go ценят за предсказуемость и простые решения в стандартной библиотеке, а в сервисах чаще всего упираемся в IP, разбор host:port, CIDR и сериализацию. Сегодня это удобно закрывается стандартным net/netip : компактные value-типы, корректный парсинг адресов и портов, работа с зонами, проверка принадлежности сетям и быстрые операции без лишних аллокаций. В статье рассмотрим этот пакет подробнее.
-
Command-and-control IPv4 map, 2025-07-27 to 2025-08-09 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
43.136.0[.]0/13
101.42.0[.]0/15
38.128.0[.]0/9
38.32.0[.]0/11
196.251.84[.]0/22
1.94.0[.]0/16
106.52.0[.]0/14
39.104.0[.]0/14
8.134.0[.]0/15
101.200.0[.]0/15 -
Command-and-control IPv4 map, 2025-07-23 to 2025-08-05 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
43.136.0[.]0/13
101.42.0[.]0/15
38.128.0[.]0/9
1.94.0[.]0/16
196.251.84[.]0/22
38.32.0[.]0/11
106.52.0[.]0/14
39.104.0[.]0/14
101.200.0[.]0/15
1.14.0[.]0/15 -
Command-and-control IPv4 map, 2025-06-05 to 2025-06-18 #CIDR
https://abjuri5t.github.io/SarlackLab/38.128.0[.]0/9
43.136.0[.]0/13
124.220.0[.]0/14
1.94.0[.]0/15
47.92.0[.]0/14
39.104.0[.]0/14
111.229.0[.]0/16
101.42.0[.]0/15
106.52.0[.]0/14
176.65.140[.]0/23
3.128.0[.]0/11 -
Command-and-control IPv4 map, 2025-06-03 to 2025-06-16 #CIDR
https://abjuri5t.github.io/SarlackLab/38.128.0[.]0/9
43.136.0[.]0/13
124.220.0[.]0/14
1.94.0[.]0/15
47.92.0[.]0/14
39.104.0[.]0/14
111.229.0[.]0/16
176.65.140[.]0/23
13.48.0[.]0/12
62.60.226[.]0/24
47.100.0[.]0/14 -
Command-and-control IPv4 map, 2025-06-01 to 2025-06-14 #CIDR
https://abjuri5t.github.io/SarlackLab/38.128.0[.]0/9
43.136.0[.]0/13
1.94.0[.]0/15
124.220.0[.]0/14
47.92.0[.]0/14
111.229.0[.]0/16
39.104.0[.]0/14
176.65.140[.]0/23
62.60.226[.]0/24
3.128.0[.]0/11
47.100.0[.]0/14 -
Command-and-control IPv4 map, 2025-05-20 to 2025-06-02 #CIDR
https://abjuri5t.github.io/SarlackLab/38.128.0[.]0/9
124.220.0[.]0/14
1.94.0[.]0/15
43.136.0[.]0/13
176.65.140[.]0/23
47.92.0[.]0/14
111.229.0[.]0/16
106.52.0[.]0/14
196.251.116[.]0/23
39.104.0[.]0/14 -
Command-and-control IPv4 map, 2025-04-04 to 2025-04-17 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
196.251.116[.]0/23
1.94.0[.]0/15
147.185.221[.]0/24
13.48.0[.]0/12
196.251.72[.]0/23
196.251.84[.]0/22
38.128.0[.]0/9
101.42.0[.]0/15
113.44.0[.]0/16 -
#OPNsense users, it is time to migrate your legacy #IPSEC VPN tunnels to the new connection setup. The Legacy IPSEC feature will be deprecated in 26.1.
I have updated my IPSEC post [1] with the new connection settings. The migration was not straightforward and required some changes, but it is not complicated either.
A little gem here is the #CIDR subnet mask notation used for Policy Based Routing, which allows multiple subnets (#VLANs) on both sides to be automatically routed, without the need for ongoing changes to tunnel settings.
[1]: https://du.nkel.dev/blog/2021-11-19_pfsense_opnsense_ipsec_cgnat/
-
#OPNsense users, it is time to migrate your legacy #IPSEC VPN tunnels to the new connection setup. The Legacy IPSEC feature will be deprecated in 26.1.
I have updated my IPSEC post [1] with the new connection settings. The migration was not straightforward and required some changes, but it is not complicated either.
A little gem here is the #CIDR subnet mask notation used for Policy Based Routing, which allows multiple subnets (#VLANs) on both sides to be automatically routed, without the need for ongoing changes to tunnel settings.
[1]: https://du.nkel.dev/blog/2021-11-19_pfsense_opnsense_ipsec_cgnat/
-
#OPNsense users, it is time to migrate your legacy #IPSEC VPN tunnels to the new connection setup. The Legacy IPSEC feature will be deprecated in 26.1.
I have updated my IPSEC post [1] with the new connection settings. The migration was not straightforward and required some changes, but it is not complicated either.
A little gem here is the #CIDR subnet mask notation used for Policy Based Routing, which allows multiple subnets (#VLANs) on both sides to be automatically routed, without the need for ongoing changes to tunnel settings.
[1]: https://du.nkel.dev/blog/2021-11-19_pfsense_opnsense_ipsec_cgnat/
-
#OPNsense users, it is time to migrate your legacy #IPSEC VPN tunnels to the new connection setup. The Legacy IPSEC feature will be deprecated in 26.1.
I have updated my IPSEC post [1] with the new connection settings. The migration was not straightforward and required some changes, but it is not complicated either.
A little gem here is the #CIDR subnet mask notation used for Policy Based Routing, which allows multiple subnets (#VLANs) on both sides to be automatically routed, without the need for ongoing changes to tunnel settings.
[1]: https://du.nkel.dev/blog/2021-11-19_pfsense_opnsense_ipsec_cgnat/
-
Here's a networking problem that I came across today. An ISP has a /19 netblock. Is there any technical reason why they shouldn't give out the last address in that block (xxx.xxx.255.255) as a customer address? #networking #ipv4 #cidr
-
Any ideas how to use a cidr[] array column in Postgres with Sequel and have access to the original values?
The Sequel Ruby gem supports that via the pg_array and pg_inet extensions. It converts the items of the array to IPAddr instances, but I just need access to the original CIDR value (String).
Not using the pg_inet extension does not work, because pg_array does seem not understand the "cidr[]" type. -
Command-and-control IPv4 map, 2024-12-31 to 2025-01-13 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
47.96.0[.]0/13
101.42.0[.]0/15
43.136.0[.]0/13
1.94.0[.]0/16
213.159.64[.]0/20
39.104.0[.]0/14
121.40.0[.]0/15
38.128.0[.]0/9
101.34.0[.]0/15
47.92.0[.]0/14 -
Command-and-control IPv4 map, 2024-11-25 to 2024-12-08 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
47.96.0[.]0/13
43.136.0[.]0/13
101.42.0[.]0/15
47.92.0[.]0/14
106.52.0[.]0/14
213.159.64[.]0/20
39.104.0[.]0/14
47.120.0[.]0/15
81.68.0[.]0/14
121.40.0[.]0/15 -
Command-and-control IPv4 map, 2024-11-23 to 2024-12-06 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
47.96.0[.]0/13
101.42.0[.]0/15
43.136.0[.]0/13
47.92.0[.]0/14
106.52.0[.]0/14
213.159.64[.]0/20
39.104.0[.]0/14
175.178.0[.]0/16
47.120.0[.]0/15
81.68.0[.]0/14 -
Command-and-control IPv4 map, 2024-11-01 to 2024-11-14 #CIDR
https://abjuri5t.github.io/SarlackLab/124.220.0[.]0/14
101.42.0[.]0/15
47.96.0[.]0/13
47.120.0[.]0/15
106.52.0[.]0/14
1.14.0[.]0/15
39.104.0[.]0/14
43.136.0[.]0/13
47.92.0[.]0/14
106.14.0[.]0/15
111.229.0[.]0/16 -
Did you know about this interactive IP address and CIDR range visualizer?
-
A new tool is out : an IPv4 subnet calculator ! 🥳
Parse your IPv4 CIDR blocks and get all the info you need about your sub network.
https://it-tools.tech/ipv4-subnet-calculator
#ittools #javascript #typescript #vue #json #developers #tool #free #opensource #online #github #ip #cidr #netmask
-
FAQ:
Are all these #CIDR blocks and #subdomains 100% malicious? - No, but they do host a SUBSTANTIAL amount of #C2 infrastructure
What’s the grid thingy? - A #HilbertCurve map of #IPv4 space
You spelled #sarlacc wrong! - The name is intentional🤓DM @Abjuri5t for more info
-
Old subnetting notes I had to dig up and refresh on while studying tonight. Enjoy!
Subnetting:
The representations of IP’s and prefixes (our masks) exist for each range. Whenever we see a /8, /16, or /24, the /number is a prefix, so 10.10.10.1 /24 is an address with a prefix. The classes listed for IPv4 aren't actually too scary when you space out exactly what is going on.
Let’s say we have a 255.255.255.0 mask
Try to look at it this way: Class A is X.Y.Y.Y Y being the hosts by number
If we have a /24 and need to understand how this translates:
255.255.255.0 is the value we end up with because the binary equivalent to 255 is 11111111
If we do this for every portion of our mask we get:
11111111.11111111.11111111.00000000
We end up with /24 because we are counting each set of 1's (11111111 + 11111111 + 11111111 = 24).
All we're essentially doing here when we subnet is counting the bits and looking at a mask.
If you look at it this way then the 2n-2 formula makes a lot more sense and becomes clearer.What would be a /26 ? 11111111.11111111.11111111.11000000 or 24 +2
We added 2 bits to the sum we had when we converted and if we convert 11000000 again, we get 192 as a number. Then we subtract.
Resources:
https://subnetting.org
https://www.youtube.com/watch?v=ZxAwQB8TZsM -
Old subnetting notes I had to dig up and refresh on while studying tonight. Enjoy!
Subnetting:
The representations of IP’s and prefixes (our masks) exist for each range. Whenever we see a /8, /16, or /24, the /number is a prefix, so 10.10.10.1 /24 is an address with a prefix. The classes listed for IPv4 aren't actually too scary when you space out exactly what is going on.
Let’s say we have a 255.255.255.0 mask
Try to look at it this way: Class A is X.Y.Y.Y Y being the hosts by number
If we have a /24 and need to understand how this translates:
255.255.255.0 is the value we end up with because the binary equivalent to 255 is 11111111
If we do this for every portion of our mask we get:
11111111.11111111.11111111.00000000
We end up with /24 because we are counting each set of 1's (11111111 + 11111111 + 11111111 = 24).
All we're essentially doing here when we subnet is counting the bits and looking at a mask.
If you look at it this way then the 2n-2 formula makes a lot more sense and becomes clearer.What would be a /26 ? 11111111.11111111.11111111.11000000 or 24 +2
We added 2 bits to the sum we had when we converted and if we convert 11000000 again, we get 192 as a number. Then we subtract.
Resources:
https://subnetting.org
https://www.youtube.com/watch?v=ZxAwQB8TZsM -
Old subnetting notes I had to dig up and refresh on while studying tonight. Enjoy!
Subnetting:
The representations of IP’s and prefixes (our masks) exist for each range. Whenever we see a /8, /16, or /24, the /number is a prefix, so 10.10.10.1 /24 is an address with a prefix. The classes listed for IPv4 aren't actually too scary when you space out exactly what is going on.
Let’s say we have a 255.255.255.0 mask
Try to look at it this way: Class A is X.Y.Y.Y Y being the hosts by number
If we have a /24 and need to understand how this translates:
255.255.255.0 is the value we end up with because the binary equivalent to 255 is 11111111
If we do this for every portion of our mask we get:
11111111.11111111.11111111.00000000
We end up with /24 because we are counting each set of 1's (11111111 + 11111111 + 11111111 = 24).
All we're essentially doing here when we subnet is counting the bits and looking at a mask.
If you look at it this way then the 2n-2 formula makes a lot more sense and becomes clearer.What would be a /26 ? 11111111.11111111.11111111.11000000 or 24 +2
We added 2 bits to the sum we had when we converted and if we convert 11000000 again, we get 192 as a number. Then we subtract.
Resources:
https://subnetting.org
https://www.youtube.com/watch?v=ZxAwQB8TZsM -
Old subnetting notes I had to dig up and refresh on while studying tonight. Enjoy!
Subnetting:
The representations of IP’s and prefixes (our masks) exist for each range. Whenever we see a /8, /16, or /24, the /number is a prefix, so 10.10.10.1 /24 is an address with a prefix. The classes listed for IPv4 aren't actually too scary when you space out exactly what is going on.
Let’s say we have a 255.255.255.0 mask
Try to look at it this way: Class A is X.Y.Y.Y Y being the hosts by number
If we have a /24 and need to understand how this translates:
255.255.255.0 is the value we end up with because the binary equivalent to 255 is 11111111
If we do this for every portion of our mask we get:
11111111.11111111.11111111.00000000
We end up with /24 because we are counting each set of 1's (11111111 + 11111111 + 11111111 = 24).
All we're essentially doing here when we subnet is counting the bits and looking at a mask.
If you look at it this way then the 2n-2 formula makes a lot more sense and becomes clearer.What would be a /26 ? 11111111.11111111.11111111.11000000 or 24 +2
We added 2 bits to the sum we had when we converted and if we convert 11000000 again, we get 192 as a number. Then we subtract.
Resources:
https://subnetting.org
https://www.youtube.com/watch?v=ZxAwQB8TZsM -
Old subnetting notes I had to dig up and refresh on while studying tonight. Enjoy!
Subnetting:
The representations of IP’s and prefixes (our masks) exist for each range. Whenever we see a /8, /16, or /24, the /number is a prefix, so 10.10.10.1 /24 is an address with a prefix. The classes listed for IPv4 aren't actually too scary when you space out exactly what is going on.
Let’s say we have a 255.255.255.0 mask
Try to look at it this way: Class A is X.Y.Y.Y Y being the hosts by number
If we have a /24 and need to understand how this translates:
255.255.255.0 is the value we end up with because the binary equivalent to 255 is 11111111
If we do this for every portion of our mask we get:
11111111.11111111.11111111.00000000
We end up with /24 because we are counting each set of 1's (11111111 + 11111111 + 11111111 = 24).
All we're essentially doing here when we subnet is counting the bits and looking at a mask.
If you look at it this way then the 2n-2 formula makes a lot more sense and becomes clearer.What would be a /26 ? 11111111.11111111.11111111.11000000 or 24 +2
We added 2 bits to the sum we had when we converted and if we convert 11000000 again, we get 192 as a number. Then we subtract.
Resources:
https://subnetting.org
https://www.youtube.com/watch?v=ZxAwQB8TZsM
