#virtualized — Public Fediverse posts

@hrbrmstr @censys @honeylabs this is basically a saas product ready to be mobilized, pending license compliance #api wrapper #compliance #controls #artillery #tarpit #virtualized #logs

@hrbrmstr @censys @honeylabs this is basically a saas product ready to be mobilized, pending license compliance #api wrapper #compliance #controls #artillery #tarpit #virtualized #logs

@hrbrmstr @censys @honeylabs this is basically a saas product ready to be mobilized, pending license compliance #api wrapper #compliance #controls #artillery #tarpit #virtualized #logs

@hrbrmstr @censys @honeylabs this is basically a saas product ready to be mobilized, pending license compliance #api wrapper #compliance #controls #artillery #tarpit #virtualized #logs

#MissKittyPolitics #AI #research can make Kitty cry. #God is good! I rub sticks together. Answers pop out. The #hypothesis regarding the viability of running #decentralized #artificial #intelligence within #virtualized #Windows environments is not merely accurate; it anticipates the exact ...

RE: https://bsky.app/profile/did:plc:hc7tndm7gduompba65aps75k/post/3mjd6etuae22x

@darth ideally in a #virtualized #sandbox

Now that i'm switching up the networking from #virtualized #VyOS to #hardware based #openwrt, I'm starting to rethink this #bgp thing in the #homelab. Should I just use #netbird ( #WireGaurd Overlay )to route between #LXD networks that can't route to each other directly. But then.. is that my new #BGP.. Everything is just another shade of greay aint it. Shiiiet!

Now that i'm switching up the networking from #virtualized #VyOS to #hardware based #openwrt, I'm starting to rethink this #bgp thing in the #homelab. Should I just use #netbird ( #WireGaurd Overlay )to route between #LXD networks that can't route to each other directly. But then.. is that my new #BGP.. Everything is just another shade of greay aint it. Shiiiet!

Now that i'm switching up the networking from #virtualized #VyOS to #hardware based #openwrt, I'm starting to rethink this #bgp thing in the #homelab. Should I just use #netbird ( #WireGaurd Overlay )to route between #LXD networks that can't route to each other directly. But then.. is that my new #BGP.. Everything is just another shade of greay aint it. Shiiiet!

Now that i'm switching up the networking from #virtualized #VyOS to #hardware based #openwrt, I'm starting to rethink this #bgp thing in the #homelab. Should I just use #netbird ( #WireGaurd Overlay )to route between #LXD networks that can't route to each other directly. But then.. is that my new #BGP.. Everything is just another shade of greay aint it. Shiiiet!

Now that i'm switching up the networking from #virtualized #VyOS to #hardware based #openwrt, I'm starting to rethink this #bgp thing in the #homelab. Should I just use #netbird ( #WireGaurd Overlay )to route between #LXD networks that can't route to each other directly. But then.. is that my new #BGP.. Everything is just another shade of greay aint it. Shiiiet!

I hear that people think that a #firewall/#dhcp server like #pfSense / #OPNSense ought to be a discrete piece of #hardware, not just a #virtualized device because:

1. #network stability; no reboots on host #OS update
2. #firewall should get full control of NICs, probably for security sake?

Are these valid? Does the #ProxMox host have a lot of downtime? It seems to me that would be a deal breaker for a #homelab

What if I dedicate my NICs to the #router and use the wifi for management?

I hear that people think that a #firewall/#dhcp server like #pfSense / #OPNSense ought to be a discrete piece of #hardware, not just a #virtualized device because:

1. #network stability; no reboots on host #OS update
2. #firewall should get full control of NICs, probably for security sake?

Are these valid? Does the #ProxMox host have a lot of downtime? It seems to me that would be a deal breaker for a #homelab

What if I dedicate my NICs to the #router and use the wifi for management?

I hear that people think that a #firewall/#dhcp server like #pfSense / #OPNSense ought to be a discrete piece of #hardware, not just a #virtualized device because:

1. #network stability; no reboots on host #OS update
2. #firewall should get full control of NICs, probably for security sake?

Are these valid? Does the #ProxMox host have a lot of downtime? It seems to me that would be a deal breaker for a #homelab

What if I dedicate my NICs to the #router and use the wifi for management?

I hear that people think that a #firewall/#dhcp server like #pfSense / #OPNSense ought to be a discrete piece of #hardware, not just a #virtualized device because:

1. #network stability; no reboots on host #OS update
2. #firewall should get full control of NICs, probably for security sake?

Are these valid? Does the #ProxMox host have a lot of downtime? It seems to me that would be a deal breaker for a #homelab

What if I dedicate my NICs to the #router and use the wifi for management?

I hear that people think that a #firewall/#dhcp server like #pfSense / #OPNSense ought to be a discrete piece of #hardware, not just a #virtualized device because:

1. #network stability; no reboots on host #OS update
2. #firewall should get full control of NICs, probably for security sake?

Are these valid? Does the #ProxMox host have a lot of downtime? It seems to me that would be a deal breaker for a #homelab

What if I dedicate my NICs to the #router and use the wifi for management?

I did not know it was possible to just add #qemu command line parameters to a #virt-manager domain XML. Now that was really handy.

This enables networking for a #virtualized #Raspberry Pi Zero:

<qemu:commandline>
<qemu:arg value="-device"/>
<qemu:arg value="usb-net,netdev=net0"/>
<qemu:arg value="-netdev"/>
<qemu:arg value="user,id=net0,hostfwd=tcp::5555-:22"/>
</qemu:commandline>

(Yes, building the environment is a lot quicker on a powerful workstation doing #ARM emulation compared to on the Zero + SD card itself ... )

I did not know it was possible to just add #qemu command line parameters to a #virt-manager domain XML. Now that was really handy.

This enables networking for a #virtualized #Raspberry Pi Zero:

<qemu:commandline>
<qemu:arg value="-device"/>
<qemu:arg value="usb-net,netdev=net0"/>
<qemu:arg value="-netdev"/>
<qemu:arg value="user,id=net0,hostfwd=tcp::5555-:22"/>
</qemu:commandline>

(Yes, building the environment is a lot quicker on a powerful workstation doing #ARM emulation compared to on the Zero + SD card itself ... )

I did not know it was possible to just add #qemu command line parameters to a #virt-manager domain XML. Now that was really handy.

This enables networking for a #virtualized #Raspberry Pi Zero:

<qemu:commandline>
<qemu:arg value="-device"/>
<qemu:arg value="usb-net,netdev=net0"/>
<qemu:arg value="-netdev"/>
<qemu:arg value="user,id=net0,hostfwd=tcp::5555-:22"/>
</qemu:commandline>

(Yes, building the environment is a lot quicker on a powerful workstation doing #ARM emulation compared to on the Zero + SD card itself ... )

I did not know it was possible to just add #qemu command line parameters to a #virt-manager domain XML. Now that was really handy.

This enables networking for a #virtualized #Raspberry Pi Zero:

<qemu:commandline>
<qemu:arg value="-device"/>
<qemu:arg value="usb-net,netdev=net0"/>
<qemu:arg value="-netdev"/>
<qemu:arg value="user,id=net0,hostfwd=tcp::5555-:22"/>
</qemu:commandline>

(Yes, building the environment is a lot quicker on a powerful workstation doing #ARM emulation compared to on the Zero + SD card itself ... )

#linux #linuxtablet #linuxaudio

There are already several #immutable linux #distros available. Run any of the following on top: #flatpaks, #appimages #snaps, Compatibility layers like #WINE or #Anbox, #virtualized OSes, tools like #distrobox, #emulators, etc, & never worry about system stability again—pieces of the next generation linux puzzle!

I was already excited by the concept of #distroagnostic packaging uniting the linux realm, but the ideas of an #ImmutableOS completes the picture!

#linux #linuxtablet #linuxaudio

There are already several #immutable linux #distros available. Run any of the following on top: #flatpaks, #appimages #snaps, Compatibility layers like #WINE or #Anbox, #virtualized OSes, tools like #distrobox, #emulators, etc, & never worry about system stability again—pieces of the next generation linux puzzle!

I was already excited by the concept of #distroagnostic packaging uniting the linux realm, but the ideas of an #ImmutableOS completes the picture!

#linux #linuxtablet #linuxaudio

There are already several #immutable linux #distros available. Run any of the following on top: #flatpaks, #appimages #snaps, Compatibility layers like #WINE or #Anbox, #virtualized OSes, tools like #distrobox, #emulators, etc, & never worry about system stability again—pieces of the next generation linux puzzle!

I was already excited by the concept of #distroagnostic packaging uniting the linux realm, but the ideas of an #ImmutableOS completes the picture!

#linux #linuxtablet #linuxaudio

There are already several #immutable linux #distros available. Run any of the following on top: #flatpaks, #appimages #snaps, Compatibility layers like #WINE or #Anbox, #virtualized OSes, tools like #distrobox, #emulators, etc, & never worry about system stability again—pieces of the next generation linux puzzle!

I was already excited by the concept of #distroagnostic packaging uniting the linux realm, but the ideas of an #ImmutableOS completes the picture!

#linux #linuxtablet #linuxaudio

There are already several #immutable linux #distros available. Run any of the following on top: #flatpaks, #appimages #snaps, Compatibility layers like #WINE or #Anbox, #virtualized OSes, tools like #distrobox, #emulators, etc, & never worry about system stability again—pieces of the next generation linux puzzle!

I was already excited by the concept of #distroagnostic packaging uniting the linux realm, but the ideas of an #ImmutableOS completes the picture!