#ipam — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ipam, aggregated by home.social.
-
Sensor de baixo custo vai monitorar qualidade do ar em Terras IndÃgenasÂ
-
[Перевод] Настройка сети в Kubernetes: основы CNI
Kubernetes-кластер без сети — не кластер, а просто набор несвязанных компонентов. Чтобы «оживить» его, важно понимать, что такое Container Network Interface (CNI) и как он работает. В статье — детальный разбор механизма CNI: что такое CNI-плагин, как он запускается и какие операции выполняет в кластере. В конце работа CNI демонстрируется на примере кастомного плагина. Для желающих глубже погрузиться в тему есть список дополнительных материалов.
https://habr.com/ru/companies/flant/articles/1015810/
#сеть #cni #cniплагин #Container_Network_Interface #ipam #containerd #vxlan #static_routing #iptables
-
[Перевод] Настройка сети в Kubernetes: основы CNI
Kubernetes-кластер без сети — не кластер, а просто набор несвязанных компонентов. Чтобы «оживить» его, важно понимать, что такое Container Network Interface (CNI) и как он работает. В статье — детальный разбор механизма CNI: что такое CNI-плагин, как он запускается и какие операции выполняет в кластере. В конце работа CNI демонстрируется на примере кастомного плагина. Для желающих глубже погрузиться в тему есть список дополнительных материалов.
https://habr.com/ru/companies/flant/articles/1015810/
#сеть #cni #cniплагин #Container_Network_Interface #ipam #containerd #vxlan #static_routing #iptables
-
[Перевод] Настройка сети в Kubernetes: основы CNI
Kubernetes-кластер без сети — не кластер, а просто набор несвязанных компонентов. Чтобы «оживить» его, важно понимать, что такое Container Network Interface (CNI) и как он работает. В статье — детальный разбор механизма CNI: что такое CNI-плагин, как он запускается и какие операции выполняет в кластере. В конце работа CNI демонстрируется на примере кастомного плагина. Для желающих глубже погрузиться в тему есть список дополнительных материалов.
https://habr.com/ru/companies/flant/articles/1015810/
#сеть #cni #cniплагин #Container_Network_Interface #ipam #containerd #vxlan #static_routing #iptables
-
[Перевод] Настройка сети в Kubernetes: основы CNI
Kubernetes-кластер без сети — не кластер, а просто набор несвязанных компонентов. Чтобы «оживить» его, важно понимать, что такое Container Network Interface (CNI) и как он работает. В статье — детальный разбор механизма CNI: что такое CNI-плагин, как он запускается и какие операции выполняет в кластере. В конце работа CNI демонстрируется на примере кастомного плагина. Для желающих глубже погрузиться в тему есть список дополнительных материалов.
https://habr.com/ru/companies/flant/articles/1015810/
#сеть #cni #cniплагин #Container_Network_Interface #ipam #containerd #vxlan #static_routing #iptables
-
Infoblox erweitert DDI-Portfolio: Neue Integrationen für Multi-Cloud und stärkere Automatisierung
Die Updates adressieren konkrete Betriebsprobleme: von überlappenden IP-Adressbereichen in Cloud-Deployments über fragmentierte DNS-Verwaltung bis hin zu aufwendigen Upgrade-Prozessen in lokalen Infrastrukturen.
-
Baleias, Caatinga e Cerrado no ‘Repórter Eco’
-
Baleias, Caatinga e Cerrado no ‘Repórter Eco’
-
Baleias, Caatinga e Cerrado no ‘Repórter Eco’
-
Baleias, Caatinga e Cerrado no ‘Repórter Eco’
-
Explore the latest in AWS VPC & IP addressing for 2025. Learn best practices to design secure, scalable cloud networks. A must-read for DevOps & cloud engineers.
Read more: https://medium.com/@ismailkovvuru/aws-vpc-ip-address-secrets-what-every-engineer-must-know-in-2025-8166818d3589#AWS #VPC #CloudNetworking #DevOps #IPAM #IPv6 #AWSBestPractices #tech #security
-
Explore the latest in AWS VPC & IP addressing for 2025. Learn best practices to design secure, scalable cloud networks. A must-read for DevOps & cloud engineers.
Read more: https://medium.com/@ismailkovvuru/aws-vpc-ip-address-secrets-what-every-engineer-must-know-in-2025-8166818d3589#AWS #VPC #CloudNetworking #DevOps #IPAM #IPv6 #AWSBestPractices #tech #security
-
Explore the latest in AWS VPC & IP addressing for 2025. Learn best practices to design secure, scalable cloud networks. A must-read for DevOps & cloud engineers.
Read more: https://medium.com/@ismailkovvuru/aws-vpc-ip-address-secrets-what-every-engineer-must-know-in-2025-8166818d3589#AWS #VPC #CloudNetworking #DevOps #IPAM #IPv6 #AWSBestPractices #tech #security
-
Explore the latest in AWS VPC & IP addressing for 2025. Learn best practices to design secure, scalable cloud networks. A must-read for DevOps & cloud engineers.
Read more: https://medium.com/@ismailkovvuru/aws-vpc-ip-address-secrets-what-every-engineer-must-know-in-2025-8166818d3589#AWS #VPC #CloudNetworking #DevOps #IPAM #IPv6 #AWSBestPractices #tech #security
-
Explore the latest in AWS VPC & IP addressing for 2025. Learn best practices to design secure, scalable cloud networks. A must-read for DevOps & cloud engineers.
Read more: https://medium.com/@ismailkovvuru/aws-vpc-ip-address-secrets-what-every-engineer-must-know-in-2025-8166818d3589#AWS #VPC #CloudNetworking #DevOps #IPAM #IPv6 #AWSBestPractices #tech #security
-
IPAM-системы: почему Excel больше не спасает и что выбрать в России
Любая сеть растёт быстрее, чем ты успеваешь её документировать. Сначала у тебя десяток серверов и пара коммутаторов, можно вести учёт адресов в табличке. Но как только устройств становится сотни, а IP‑адресов тысячи, Excel превращается в минное поле. Проблемы начинаются банально: Один инженер раздал IP вручную, второй занял тот же диапазон под тест, подсеть легла. Забыли зафиксировать, кому выдан адрес, и теперь никто не понимает, что за «сервер Х» висит в мониторинге. Конфликт VLAN и вся смена сидит без CRM. Классика. Если нет централизованного учёта, сеть рано или поздно начнёт «жечь костры». Именно для этого придумали IPAM (IP Address Management) — системы, которые берут на себя:
https://habr.com/ru/articles/939852/
#ipam #vlan #импортозамещение_по #планирование_сети #netbox #сетевые_инженеры #ipадресация #учёт_серверов #dcim
-
IPAM-системы: почему Excel больше не спасает и что выбрать в России
Любая сеть растёт быстрее, чем ты успеваешь её документировать. Сначала у тебя десяток серверов и пара коммутаторов, можно вести учёт адресов в табличке. Но как только устройств становится сотни, а IP‑адресов тысячи, Excel превращается в минное поле. Проблемы начинаются банально: Один инженер раздал IP вручную, второй занял тот же диапазон под тест, подсеть легла. Забыли зафиксировать, кому выдан адрес, и теперь никто не понимает, что за «сервер Х» висит в мониторинге. Конфликт VLAN и вся смена сидит без CRM. Классика. Если нет централизованного учёта, сеть рано или поздно начнёт «жечь костры». Именно для этого придумали IPAM (IP Address Management) — системы, которые берут на себя:
https://habr.com/ru/articles/939852/
#ipam #vlan #импортозамещение_по #планирование_сети #netbox #сетевые_инженеры #ipадресация #учёт_серверов #dcim
-
IPAM-системы: почему Excel больше не спасает и что выбрать в России
Любая сеть растёт быстрее, чем ты успеваешь её документировать. Сначала у тебя десяток серверов и пара коммутаторов, можно вести учёт адресов в табличке. Но как только устройств становится сотни, а IP‑адресов тысячи, Excel превращается в минное поле. Проблемы начинаются банально: Один инженер раздал IP вручную, второй занял тот же диапазон под тест, подсеть легла. Забыли зафиксировать, кому выдан адрес, и теперь никто не понимает, что за «сервер Х» висит в мониторинге. Конфликт VLAN и вся смена сидит без CRM. Классика. Если нет централизованного учёта, сеть рано или поздно начнёт «жечь костры». Именно для этого придумали IPAM (IP Address Management) — системы, которые берут на себя:
https://habr.com/ru/articles/939852/
#ipam #vlan #импортозамещение_по #планирование_сети #netbox #сетевые_инженеры #ipадресация #учёт_серверов #dcim
-
IPAM-системы: почему Excel больше не спасает и что выбрать в России
Любая сеть растёт быстрее, чем ты успеваешь её документировать. Сначала у тебя десяток серверов и пара коммутаторов, можно вести учёт адресов в табличке. Но как только устройств становится сотни, а IP‑адресов тысячи, Excel превращается в минное поле. Проблемы начинаются банально: Один инженер раздал IP вручную, второй занял тот же диапазон под тест, подсеть легла. Забыли зафиксировать, кому выдан адрес, и теперь никто не понимает, что за «сервер Х» висит в мониторинге. Конфликт VLAN и вся смена сидит без CRM. Классика. Если нет централизованного учёта, сеть рано или поздно начнёт «жечь костры». Именно для этого придумали IPAM (IP Address Management) — системы, которые берут на себя:
https://habr.com/ru/articles/939852/
#ipam #vlan #импортозамещение_по #планирование_сети #netbox #сетевые_инженеры #ipадресация #учёт_серверов #dcim
-
Kubernetes: шестимесячный марафон по прокачке dBrain.cloud
За последние полгода наши инженеры проделали значительную работу по развитию и оптимизации платформы dBrain.cloud , ключевым инструментом которой является Kubernetes. В этой статье мы подробно расскажем об изменениях, произошедших в инфраструктуре, о внедрении новых функций и фишках, которые, мы надеемся, будут интересны DevOps-сообществу.
https://habr.com/ru/companies/dbraincloud/articles/931798/
#gpu #slicing #s3 #cilium #metallb #ipam #cgroup_v2 #kubernetes #dbrain #devops
-
Kubernetes: шестимесячный марафон по прокачке dBrain.cloud
За последние полгода наши инженеры проделали значительную работу по развитию и оптимизации платформы dBrain.cloud , ключевым инструментом которой является Kubernetes. В этой статье мы подробно расскажем об изменениях, произошедших в инфраструктуре, о внедрении новых функций и фишках, которые, мы надеемся, будут интересны DevOps-сообществу.
https://habr.com/ru/companies/dbraincloud/articles/931798/
#gpu #slicing #s3 #cilium #metallb #ipam #cgroup_v2 #kubernetes #dbrain #devops
-
Kubernetes: шестимесячный марафон по прокачке dBrain.cloud
За последние полгода наши инженеры проделали значительную работу по развитию и оптимизации платформы dBrain.cloud , ключевым инструментом которой является Kubernetes. В этой статье мы подробно расскажем об изменениях, произошедших в инфраструктуре, о внедрении новых функций и фишках, которые, мы надеемся, будут интересны DevOps-сообществу.
https://habr.com/ru/companies/dbraincloud/articles/931798/
#gpu #slicing #s3 #cilium #metallb #ipam #cgroup_v2 #kubernetes #dbrain #devops
-
Kubernetes: шестимесячный марафон по прокачке dBrain.cloud
За последние полгода наши инженеры проделали значительную работу по развитию и оптимизации платформы dBrain.cloud , ключевым инструментом которой является Kubernetes. В этой статье мы подробно расскажем об изменениях, произошедших в инфраструктуре, о внедрении новых функций и фишках, которые, мы надеемся, будут интересны DevOps-сообществу.
https://habr.com/ru/companies/dbraincloud/articles/931798/
#gpu #slicing #s3 #cilium #metallb #ipam #cgroup_v2 #kubernetes #dbrain #devops
-
I learned something about using Python today, and this might influence how I write other parts of my code. I'm also open to ideas on the best way to go about this.
I'm now most of the way through a refactor where I'm switching to Postgres for my database and also using SQLModel over SQLAlchemy. I have all my classes written/rewritten and was running into an issue on the IPAM side of things when creating a new network. See if you can spot the bug as I write it out here.
Each API call in FastAPI will map to one function, with each class having their functions in their own file, for the sake of modularity/organization. I have a subnet.py file and ipRecords.py for those respective classes.
When a new subnet is created, I make the subnet in the database and then populate all of the IP addresses in the IpAddress table before returning to the FastAPI call. This means that one function call is chained to another one. Specifically subnet.createSubnet calls Iprecords.createIpRecord.
Both functions have a Session object coming in like this. Note that Depends comes from SQLModel and getDb() returns a database session, via yield.
myFunction( input1: int, input2, str, db: Session = Depends(getDb))
This means that when a new subnet is added, and then we call iprecords.createIpRecord, that doesn't get the proper result for getDb and we can't talk to the database.
My fix was to pass the db from one function to another so I can keep using it, and not pull it in via getDb on the inner function call.
Now that I'm through that mess, I can carry on with the rest of my refactor and get back to the main branch.
#pebkac #rackroot #programming #fastapi #python #ipam #homelab #opensource #sqlmodel
-
I learned something about using Python today, and this might influence how I write other parts of my code. I'm also open to ideas on the best way to go about this.
I'm now most of the way through a refactor where I'm switching to Postgres for my database and also using SQLModel over SQLAlchemy. I have all my classes written/rewritten and was running into an issue on the IPAM side of things when creating a new network. See if you can spot the bug as I write it out here.
Each API call in FastAPI will map to one function, with each class having their functions in their own file, for the sake of modularity/organization. I have a subnet.py file and ipRecords.py for those respective classes.
When a new subnet is created, I make the subnet in the database and then populate all of the IP addresses in the IpAddress table before returning to the FastAPI call. This means that one function call is chained to another one. Specifically subnet.createSubnet calls Iprecords.createIpRecord.
Both functions have a Session object coming in like this. Note that Depends comes from SQLModel and getDb() returns a database session, via yield.
myFunction( input1: int, input2, str, db: Session = Depends(getDb))
This means that when a new subnet is added, and then we call iprecords.createIpRecord, that doesn't get the proper result for getDb and we can't talk to the database.
My fix was to pass the db from one function to another so I can keep using it, and not pull it in via getDb on the inner function call.
Now that I'm through that mess, I can carry on with the rest of my refactor and get back to the main branch.
#pebkac #rackroot #programming #fastapi #python #ipam #homelab #opensource #sqlmodel
-
I learned something about using Python today, and this might influence how I write other parts of my code. I'm also open to ideas on the best way to go about this.
I'm now most of the way through a refactor where I'm switching to Postgres for my database and also using SQLModel over SQLAlchemy. I have all my classes written/rewritten and was running into an issue on the IPAM side of things when creating a new network. See if you can spot the bug as I write it out here.
Each API call in FastAPI will map to one function, with each class having their functions in their own file, for the sake of modularity/organization. I have a subnet.py file and ipRecords.py for those respective classes.
When a new subnet is created, I make the subnet in the database and then populate all of the IP addresses in the IpAddress table before returning to the FastAPI call. This means that one function call is chained to another one. Specifically subnet.createSubnet calls Iprecords.createIpRecord.
Both functions have a Session object coming in like this. Note that Depends comes from SQLModel and getDb() returns a database session, via yield.
myFunction( input1: int, input2, str, db: Session = Depends(getDb))
This means that when a new subnet is added, and then we call iprecords.createIpRecord, that doesn't get the proper result for getDb and we can't talk to the database.
My fix was to pass the db from one function to another so I can keep using it, and not pull it in via getDb on the inner function call.
Now that I'm through that mess, I can carry on with the rest of my refactor and get back to the main branch.
#pebkac #rackroot #programming #fastapi #python #ipam #homelab #opensource #sqlmodel
-
I learned something about using Python today, and this might influence how I write other parts of my code. I'm also open to ideas on the best way to go about this.
I'm now most of the way through a refactor where I'm switching to Postgres for my database and also using SQLModel over SQLAlchemy. I have all my classes written/rewritten and was running into an issue on the IPAM side of things when creating a new network. See if you can spot the bug as I write it out here.
Each API call in FastAPI will map to one function, with each class having their functions in their own file, for the sake of modularity/organization. I have a subnet.py file and ipRecords.py for those respective classes.
When a new subnet is created, I make the subnet in the database and then populate all of the IP addresses in the IpAddress table before returning to the FastAPI call. This means that one function call is chained to another one. Specifically subnet.createSubnet calls Iprecords.createIpRecord.
Both functions have a Session object coming in like this. Note that Depends comes from SQLModel and getDb() returns a database session, via yield.
myFunction( input1: int, input2, str, db: Session = Depends(getDb))
This means that when a new subnet is added, and then we call iprecords.createIpRecord, that doesn't get the proper result for getDb and we can't talk to the database.
My fix was to pass the db from one function to another so I can keep using it, and not pull it in via getDb on the inner function call.
Now that I'm through that mess, I can carry on with the rest of my refactor and get back to the main branch.
#pebkac #rackroot #programming #fastapi #python #ipam #homelab #opensource #sqlmodel
-
I learned something about using Python today, and this might influence how I write other parts of my code. I'm also open to ideas on the best way to go about this.
I'm now most of the way through a refactor where I'm switching to Postgres for my database and also using SQLModel over SQLAlchemy. I have all my classes written/rewritten and was running into an issue on the IPAM side of things when creating a new network. See if you can spot the bug as I write it out here.
Each API call in FastAPI will map to one function, with each class having their functions in their own file, for the sake of modularity/organization. I have a subnet.py file and ipRecords.py for those respective classes.
When a new subnet is created, I make the subnet in the database and then populate all of the IP addresses in the IpAddress table before returning to the FastAPI call. This means that one function call is chained to another one. Specifically subnet.createSubnet calls Iprecords.createIpRecord.
Both functions have a Session object coming in like this. Note that Depends comes from SQLModel and getDb() returns a database session, via yield.
myFunction( input1: int, input2, str, db: Session = Depends(getDb))
This means that when a new subnet is added, and then we call iprecords.createIpRecord, that doesn't get the proper result for getDb and we can't talk to the database.
My fix was to pass the db from one function to another so I can keep using it, and not pull it in via getDb on the inner function call.
Now that I'm through that mess, I can carry on with the rest of my refactor and get back to the main branch.
#pebkac #rackroot #programming #fastapi #python #ipam #homelab #opensource #sqlmodel
-
As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.
For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.
Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.
This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.
#rackroot #programming #applicationdesign #backend #ipam #fastapi #webdev #homelab #dhcp
-
As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.
For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.
Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.
This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.
#rackroot #programming #applicationdesign #backend #ipam #fastapi #webdev #homelab #dhcp
-
As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.
For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.
Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.
This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.
#rackroot #programming #applicationdesign #backend #ipam #fastapi #webdev #homelab #dhcp
-
As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.
For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.
Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.
This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.
#rackroot #programming #applicationdesign #backend #ipam #fastapi #webdev #homelab #dhcp
-
As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.
For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.
Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.
This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.
#rackroot #programming #applicationdesign #backend #ipam #fastapi #webdev #homelab #dhcp
-
I got the gateway update working tonight and decided to shift all the validation logic to the backend, which also had a side effect of simplifying my code.
Before I was on the front end writing javascript logic for whether the gateway was being set or cleared and then I would also need to write code for how to handle all the combinations. Now, I have one API endpoint at /networks/{id}/gateway where an HTTP POST can be submitted and that either passes or fails.
If someone puts in an invalid IP address, or the IP address is not a usable IP in the subnet, it won't be accepted and an error message is shown on the page. HTTP 500 is returned and Vuetify can pick that up to show an error message for me. Once valid input is submitted, the error will go away and the user will see the gateway updated to the proper value.
If someone adds a gateway when there wasn't one before, or updates the address to something else, then the IP will be processed and updated as long as it's valid.
#rackroot #programming #vuetify #python #ipam #fastapi #webdev #fullstack
-
I'm also having ideas for some kind of IP utilization metric where it will indicate how many IPs are available on a given network. Things like DHCP allocations and static IPs can all be summarized.
This database is gonna be interesting.
Also, I'm like halfway to a full IPAM tool. Why stop now lol
#programming #python #IPAM #rackroot #infrastructure #engineering
-
Oh hey, we've got the first of our blog posts about NetBox Enterprise out, now. I've been working on helping to put this product together since starting on at NetBox a few months ago and it's been a pretty great experience. Yes, even (mostly) the Kubernetes part! 😄
https://netboxlabs.com/blog/technology-showcase-an-inside-look-at-deploying-netbox-enterprise/
-
AITU Military CTF 2024:Digital Fortress: Как мы инфраструктуру для полигона поднимали. Часть 2
Перед прочтением данной статьи настоятельно рекомендую ознакомиться с 1 частью Введение Данная статья является продолжением статьи про поднятие киберполигона AITU Military CTF, в этой части мы рассмотрим глобальные изменения касающиеся инфраструктуры, такие как настройка сети ESXI, создание централизованного Firewall и мониторинг. Я решил написать эту статью так как очень мало подобных статей на тему постройки киберполигона, в последнее время в нашей стране начали часто проводится полигоны и в этой статье мы рассмотрим все тонкости настройки инфраструктуры в условиях ограниченности ресурсов.
https://habr.com/ru/articles/812445/
#CTF #киберполигон #ESXI #Mikrotik #OpenVPN #ipam #кибербезопасность #инфраструктура
-
I'm looking for a IP Address Management Tool #IPAM . If it's open source, than it's the best way, but not must. Target is to manage all IP addresses from a company.
Best process:
- LDAP
- approval workflow
- Manage IP ranges
- Manage IP addressesI found #NIPAP - but I dodn't try at the moment. Another one is #GestióIP - this looks fine but the last update is 2 years ago.
Anyone can help me please to find the right IP Address Management Tool? -
🔥⏲️ Fudge Sunday "There's a Lot of Opportunities" A look at recent funding, mergers, and acquisitions related to platform engineering
#mlops #machinelearning #developerexperience #devx #IDP #IDPaaS #dns #dnssecurity #networkautomation #networkmanagement #ipam #cmdb #vcfunding #mergers #acquisitions #funding #fundingnews #startups #startupfunding #newsletter #newsletters #opportunities #engineering #platformengineering #platformengineer
-
I wrote a blog post: "IP Address Management ( #IPAM ) using #PHPIPAM integrated with #Keycloak for #SAML2 #Authentication" https://jon.sprig.gs/blog/post/3015
-
@cmsirbu Many of our customers are very high skilled IT organisations and some of them are now actively migrating towards #netbox for as their main #ipam / #inventory tool. Some of them running their own DCs, some of them just some 10's of servers, one of them using netbox for documenting larger #wifi networks - quite different use cases.
-
#NetBox Labs will spin out from NS1 into its own company, with IBM as an investor!
https://netboxlabs.com/blog/netbox-labs-to-spin-out-of-ns1-ibm-to-invest
-
Caddy:
I've been having the worst time with Caddy it seems simple enough but I can't for the life of me get TLS working. I did a bunch of network magic to hop through a series of routers and NATs which is probably part of my problem but I'm seeing packets and the traffic looks ok as far as I can tell. I see that LetsEncrypt issues the certs but then it seems to struggle to serve it back. I was able to point Caddy at other services fine but TLS has been the issue. I need to give it another shot and I will change the approach to securely reach my lab net.PowerDNS Admin:
I also attempted to spin up PowerDNS Admin. The docker project seems like it has a nice UI but I couldn't get the docker-compose to run successfully. I tried updating a bunch of components and messing with updating the repo but it caused more and more problems rather than solving any. After a couple hours I gave up on it and I think I'll try running a vanilla PowerDNS instance later. I mainly chose it because I also see it in the Proxmox docs as the preferred way to hand over DNS entries from the SDN.Keycloak:
I got Keycloak running in the lab and the initial client user credential test to work. Then I tried configuring OpenID connect on my CodiMD instance. No go. I couldn't figure out how to align all the parameters on both the Keycloak side and CodiMD side. Then I read the docs and saw the SAML approach may be easier. I followed the example and attempted to map it to the parameters for both to get the IDP working. Still no luck. I've done SAML before and it didn't seem this difficult previously. I think the next attempt will be to try LDAP and sync up my users from GLauth over to Keycloak. If anyone has a good guide or tips on integrating things with Keycloak let me know.#homelab #selfhosted #proxmox #docker #netbox #ipam #dcim #rancher #vscode #powerdnsadmin #powerdns #codimd #caddy #ghost #tinyproxy #keycloak
