Search results

I’m running the linux binary of Splunk in Linuxulator (/compat/devuan01 chroot). Inside chroot it runs as splunkfwd, 1000:1000. Outside chroot, 1000:1000 is undefined, so I’ve created a FreeBSD user: splunklinux:*:1000:1000:Splunk Forwarder Linux:/opt/splunkforwarder:/bin/sh Because my...

Well, can you self-consume an NFS mount? It also means I need to run an NFS client in Linux userland, unless the FreeBSD host can be the client. I guess I could try (if fact I could also get rid of ACLs and change POSIX rights to indulge my needs). But more importantly I would love to...

Hello I’ve setup a Linux (Devuan) chroot environment on my FreeBSD 13.x server. I’m using nullfs to mount few ZFS filesystems inside the chroot. One of these FS has ACLs,that the linux part seems unable to see: # grep /var/log /etc/fstab /var/log /compat/devuan01/var/hostlog...

that’s actually step 1 of my scenario :) I prepare one SSD, and ship it with another blank SSD (step 2) ohhh I would probably have forgot this one, thanks. I’ll have to import my SAS pool after booting on the SSD, too. About data synchronization: I plan to restore most files from a backup...

Agreed, it makes me nervous too, but back in the days I used to upgrade FreeBSD by make/make install/etc, remotely over ssh and without IPMI ;) Good preparation is the key (and competent support inside the DC in case it derails). NVMe is not an option for me: - for the price of 2x8TB NVMe I...

Hello, I have a server with 4 SAS HDDs (no empty slot remaining), configured as a RAIDZ1 $ zpool list -v sas NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT sas 21.8T 4.36T 17.4T - - 38% 20% 1.00x ONLINE -...

Interesting, thank you, I’ll play with that later as I plan to provide IPv6 to my LAN :)

Hello! Thanks a lot, you nailed it. It was a problem with PF :( I’ve tested the paa out rule for inet6 and boom, it worked! I can’t ditch the freebox yet, it provides telephone and some TV services that someone in the household does not want to let go, yet :)

Hello, I’m running a FreeBSD (13.2-RELEASE-p2) gateway between my LAN and internet. On the WAN side (em1) it’s hooked to a freebox (the fiber "modem" of my provider) setup in bridge mode. Relevant rc configuration: ifconfig_em1="DHCP" gateway_enable="YES" ifconfig_em0="inet 192.168.0.1...

edit first post IIRC

I did, of course. Everything is properly setup, I just want to log hits for blacklistd-managed rules that are "inside" the anchor. And apparently the only way to do so is to implement the solution from shurik

Thank you both. I do understand that an anchor is not a rule, but you can add some context related element to an anchor (like "in", "on $ext_if", etc.) so I was hopping there was a way to add "log" too. Changing the helper is a "high maintenance" solution if I want to ensure my own helper stay...

Hello, I'm using blacklistd on my FreeBSD 13.x servers (ssh, submission) and I would like pf to log when a connection attempt hit the rule. Currently I use: anchor "blacklistd/*" in on $ext_if I've tried to add "log" at different places in this statement, but got only "syntax error" from...

Well. My question is about the behavior of bash, the default shell on FreeBSD is irrelevant :)

both seem to work, actually

Thanks, it's working. Do you have any idea if it comes from the bash version it self, or from a FreeBSD only bash patch?

Hello, I'm currently trying to test borgwarehouse.com to make sure it can get installed and ran properly on FreeBSD. It's very early stage software but sounds promising. Anyway, the software relies on a handful of bash shell scripts that could be ported to FreeBSD in no time. One of those shell...

Thanks, I'll take a look at ports. NFS is not an option here, unfortunately.

I've tried an infinite variation of commands but none worked, this one is no exception and returns the same error :(

Hello, I'm trying to share files between my Mac and my FreeBSD PC using SMB (macOS file sharing). The share works great between the Mac and a Windows PC, so everything is correct server-side. Trying to mount the share on FreeBSD 13.1 yields to this error: $ sudo mount_smbfs -I 192.168.0.2 -U...