#cidr — Public Fediverse posts

IP подов кончились, а обычные решения не подошли: как мы расширили сеть на проде, не пересоздавая кластер (кейс + гайд)

Штатная ситуация оказалась задачей со звёздочкой: кластер кинул алерт о том, что заканчивается сеть подов, но ни одно решение «из методички» не подходило, а вытаскивать кластер из прода было нельзя. В статье расскажу, как мы не просто расширили подсеть подов, но сделали это на работающем кластере и не потеряли при этом данные. Что важно — трюк сработает на любом дистрибутиве Kubernetes и CNI.

https://habr.com/ru/companies/flant/articles/1045872/

#kubernetes #cilium #сеть #cidr #etcd

creates semantic nodes and clusters #CIDR FM semantic-search.headlines-world.com/advanced-sea... #ARNAUD DE #CERVOLE chatgpt.com?prompt=Analy... AÉPIOT: INDEPENDENT SEMANTIC WEB 4.0 INFRASTRUCTURE (EST. 2009): headlines-world.com

MultiSearch Tag Explorer

Как технически устроена 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

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.

For the first time since #CIDR moved to Chaminade, my arrival has not been delayed by a landslide.

i have nothing against the vast majority of chinese but the botnets are really crazy - 80% of my traffic is from china #asn #cidr #ipset #fail2ban

i have nothing against the vast majority of chinese but the botnets are really crazy - 80% of my traffic is from china #asn #cidr #ipset #fail2ban

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-типы, корректный парсинг адресов и портов, работа с зонами, проверка принадлежности сетям и быстрые операции без лишних аллокаций. В статье рассмотрим этот пакет подробнее.

https://habr.com/ru/companies/otus/articles/937362/

#golang #Go #Addr #AddrPort #Prefix #IP #IPv4 #IPv6 #CIDR

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/

The #CIDR House Rules

https://www.ducktyped.org/p/the-cidr-house-rules

The #CIDR House Rules

https://www.ducktyped.org/p/the-cidr-house-rules

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

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.

#ruby #sequel #postgres #cidr

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

What is your favorite #ipv4 #LAN #CIDR?

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

Watch out, y'all, pretty large 🦣 🧵 data dump on #CIDR block ownership incoming...

(I'm sorry for writing such a long thread - I didn't have time to write a shorter one.)

合併 GitHub Actions 的 IP address

在 GitHub 官方文件「About GitHub's IP addresses」中，是有提到 https://api.github.com/meta 這組 API endpoint，可以取得當下的 GitHub Actions 所使用的連外 IP address，不過如果你實際掃下來後會發現量相當大，以現在的情況來說，IPv4 address 有 3708 筆，IPv6 address 則有 801 筆：

$ cat

https://blog.gslin.org/archives/2024/06/06/11834/%e5%90%88%e4%bd%b5-github-actions-%e7%9a%84-ip-address/

#Computer #Murmuring #Network #Programming #Service #Software #actions #address #cidr #github #ip #ipv4 #ipv6 #netmask #network

Python - szybkie dopasowanie adresu IP do klasy adresu CIDR ( https://nfsec.pl/hacks/6434 ) #python #ip #cidr #script #trie #twittermigration

Did you know about this interactive IP address and CIDR range visualizer?

#python #networking #ipaddresses #CIDR #routing #linux

https://cidr.xyz/

@alex A trick that I like to use for consolidating activity sources in logs is to look at the ASN.

You can get this by querying the Routeviews DNS server, using a reversed dotted-quad lookup. For example, using social.alexschroeder.ch:

$ host -t txt 237.50.209.178.asn.routeviews.org
237.50.209.178.asn.routeviews.org descriptive text "29691" "178.209.32.0" "19"

So, you're on ASN 29691, CIDR 178.209.32.0/19.

If you're seeing a large amount of non-organic traffic from a specific AS, CIDR block, or set of related CIDR blocks, you might choose to rate-limit, restrict, or block those entirely.

https://www.routeviews.org/routeviews/

Since this is DNS-lookup-based, what I typically do for recording is to flood-query a large number of IPs first, to seed my cache (you are running a caching DNS server, right), then do the reporting run. It's still generally useful to run parallel queries to avoid blocking.

You can also grab and host the zone maps themselves, I believe, documented on the Routeviews site ... somewhere.

#Routeviews #ASN #CIDR #BGP

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

quicktip #20: convert an IP range to its exact CIDR subnets with the Linux `netmask` utility.

#linux #cidr #ip #network #ipv4 #netmask #subnet #router

#Network #Subnetting

#Networking #Subnet #IPv4 #CIDR #CheatSheet