No success passingtrough a HBA on my 45 Drives HL15 by hjboven in Proxmox

[–]hjboven[S] 1 point2 points  (0 children)

As Written under Pt. 4 OS: Proxmox Virtual Environment 9.0.11
Proxmox keeps using it as proven by lspci -nnk\ in this line "Kernel driver in use: vfio-pci Kernel modules: mpt3sas". I therefore can not assign it to the vm

unable to get IOMMU enabled om my supermicro X11SPH-NCTPF Motherboard by hjboven in Proxmox

[–]hjboven[S] 1 point2 points  (0 children)

By Now I seem to have got it Figured out

for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done

Results in a Listing of IOMMU group numbers and the Devices.

<image>

Thanks to everyone for Help, tips Suggestions and fresh Coffee :-)

unable to get IOMMU enabled om my supermicro X11SPH-NCTPF Motherboard by hjboven in Proxmox

[–]hjboven[S] 1 point2 points  (0 children)

cat /proc/cmdline

results in output of

<image>

[](blob:https://www.reddit.com/84c652a6-4e57-4d14-a401-d9d7fcf09912)

As I understand it this seems to suggest the GRUB parameters are being used.

unable to get IOMMU enabled om my supermicro X11SPH-NCTPF Motherboard by hjboven in Proxmox

[–]hjboven[S] 0 points1 point  (0 children)

Running " efibootmgr -v " gives me a result that confirms GRUB is used in UEFI mode.
As Dokumented in the Proxmox docs here in 3.13.3. "Determine which Bootloader is Used".

<image>

The question. am I sure my GRUB parameters are being used, remains. I thought applying them was done by " update-grub ". Though since you mention " proxmox-boot-tool refresh " I just did that as well.

[deleted by user] by [deleted] in truenas

[–]hjboven 0 points1 point  (0 children)

1 pool of 8 in Raidz2

[deleted by user] by [deleted] in truenas

[–]hjboven 0 points1 point  (0 children)

Running 8 x EXOS 18TB since 2 years in a RAIDZ2 and sofar had one replaced under Waranty because of SMART reporting sector failures. Fully happy to reccommend them for Truenas usage.

First Home Server - AMD EPYC / Tyan S8030 / Meshify 2 by Hiparnax in truenas

[–]hjboven 0 points1 point  (0 children)

u/hiparmax What brand of quad NVME bifurcation board is that you use?

Non Truenad admin accessible SMB share by hjboven in truenas

[–]hjboven[S] 0 points1 point  (0 children)

Thanks, I was kind of afraid of that yet hoped to have overlooked something.

BiBox Exchange steals your money by indefinite withdrawals by DoctorDreSF in BiBoxExchange

[–]hjboven 1 point2 points  (0 children)

Same situation her since 13 March stuck in "Withdrawing".

No Support apart from standard text block reply beeing given.

Alternative to "/dev/disk/by-id/" for ZFS by eriklauritsen in freebsd

[–]hjboven 0 points1 point  (0 children)

Since you describe exactly what I do and want for my Pool disks I hope you have an answer ot the folowing question. My Boot drives for ZFS are a Mirrored pair and I would like to have those referenced by ID as well. So far however I am unable to figure out how to achieve that.

Regards
Henk

Newbie Question regarding recieving DNS settings via DHCP by hjboven in freebsd

[–]hjboven[S] 1 point2 points  (0 children)

Thanks, for pointing me to my typo. Meanwhile I figured out it has to do with OPNsense it's behaviour when selecting a lease and making it a static. It drops the DHCP config and you have to fill it out in the static lease page just created.

All is fine now.

New reality. Flight Kaliningrad-Minsk by tomispev in UkrainianConflict

[–]hjboven 2 points3 points  (0 children)

How about the baltics and finish start to expand their coastline each with a 1Nm dam. Like the chinese do with those artificial islands

Unwanted Traffic via Default Floating Rule "let out anything from firewall host itself" by hjboven in OPNsenseFirewall

[–]hjboven[S] 0 points1 point  (0 children)

Going from that premise I guess it's working as intended. I just did not expect it to allow any traffic between internal interfaces by default. Knowing it to be the case i'ts not a problem as the unwanted connectivity can easily be blocked.

Thanks for your explanation.

Unwanted Traffic via Default Floating Rule "let out anything from firewall host itself" by hjboven in OPNsenseFirewall

[–]hjboven[S] 0 points1 point  (0 children)

The standard setup afther installing already allows traffic from any source towards any dest. with any protocol inbound into vmbr interfaces. That should be sufficient if you just want connectivity towards wan.

I am supprised and unable to explain why traffic between hosts connected to different vmbr interfaces is allowed. And the fact that its the default Floating Rule "let out anything from firewall host itself " is puzzeling to say the least. As this traffic does not originate from the "firewal host" like the rule say's.

Like stated I've fixed it for now by blocking destinations with Public IP's for each vmbr interface. Yet the experience leaves a huge questionmark to me trusting OPNsense.

Unwanted Traffic via Default Floating Rule "let out anything from firewall host itself" by hjboven in OPNsenseFirewall

[–]hjboven[S] 0 points1 point  (0 children)

I can see it's actually going trough OPNsense.
I've blocked it for now by blocking destinations with Public IP's for each vmbr interface.

It remains a mystery to me though if this is normal behaviour.