• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: July 11th, 2023

help-circle

  • If you mainly want to “hide” your IP, you can’t. Look at the headers of any message. It’ll still show the original source IP, which will be yours.

    For the rest of the time I’d recommend getting a spam filtering service. Mimecast, ProofPoint, Barracuda, etc.

    Messages sent to you go to the filter, which then forwards the message over to your mail server. Outbound you configure your server to use the filter as a smart host. These filters will also buffer messages if your mail server is offline. So if the server is down, the filter holds on to messages and retries delivery later when your server is back up (within reason).


  • I don’t recall in virt-manager off the top of my head. But if you make changes in the XML of a domain, you do have to shutdown/restart the domain before they’re effective. And just to be safe, I would say to shutdown the domain, then check the XML, then start up again.

    You do say you’re just using qemu, so if that’s the case and you aren’t using libvirt in front of it, shutdown the VM, make sure your qemu command specifies an e1000 network device, and run again.

    I can check virt-manager when I get some free time this evening, if that’s what you want/need.









  • That’s right. So on the top backplane, you’ll connect the Oculink ports to the Oculink outfitted HBA. One port per drive.

    For the bottom 8 drives, it looks like you’ll have one miniSAS HD connector per four drives, plus another for the rear bays. I initially thought they were plain SATA and would go to the motherboard. But it looks like you’ll need a third connector - so you’ll want a 16 port HBA (Supermicro AOC-S3216L-L16iT).

    Reading through all the documentation I can, it looks like you’ll have the option to run all the bays as NVME or SAS disks. The controllers and layouts I’ve listed are for running four bays as NVME, and the other 10 as SAS.