I am trying to disable Keyboard-Interactive login, as I only want key login, but it won't disable with the below sshd_config. I also have attached an edited ssh -v login to the server. I have been trying to follow here , here , and the documentation here sshd_config:

MaxAuthTries 3
PubkeyAuthentication yes

AuthorizedKeysFile      .ssh/authorized_keys
PasswordAuthentication no
PermitEmptyPasswords no

ChallengeResponseAuthentication no
KbdInteractiveAuthentication no
UsePAM no



Subsystem       sftp    /usr/libexec/sftp-server

Edited ssh -v output:

OpenSSH_7.9p1 Debian-10+deb10u2, OpenSSL 1.1.1d  10 Sep 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to *.*.*.* [*.*.*.*] port **.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: identity file /home/user/.ssh/id_xmss type -1
debug1: identity file /home/user/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9 FreeBSD-20200214
debug1: match: OpenSSH_7.9 FreeBSD-20200214 pat OpenSSH* compat 0x04000000
debug1: Authenticating to *.*.*.*:** as 'user'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC:  compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC:  compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:qDEr5lkrjAHt0jMrLosrpQEPP5s0BdC0+7CHyRl3+oY
debug1: Host '*.*.*.*' is known and matches the ECDSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:2
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: Will attempt key: /home/user/.ssh/id_rsa
debug1: Will attempt key: /home/user/.ssh/id_dsa
debug1: Will attempt key: /home/user/.ssh/id_ecdsa
debug1: Will attempt key: /home/user/.ssh/id_ed25519
debug1: Will attempt key: /home/user/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/user/.ssh/id_rsa
debug1: Trying private key: /home/user/.ssh/id_dsa
debug1: Trying private key: /home/user/.ssh/id_ecdsa
debug1: Trying private key: /home/user/.ssh/id_ed25519
debug1: Trying private key: /home/user/.ssh/id_xmss
debug1: Next authentication method: keyboard-interactive
Password for user@server:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password for user@server:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password for user@server:
Received disconnect from *.*.*.* port *:2: Too many authentication failures
Disconnected from *.*.*.* port **

Help me with pvpgn server run? I installed it on FreeBSD and, now I don't know how to start the service. I install in /build/src/bnetd ./bnetd and it didn't work. Can someone who understands FreeBSD give me a little help? to download and how to install it https://github.com/pvpgn/pvpgn-server i need start service now i how is possible??

This question pertains to Tuxedo laptops (and possibly Clevo, Uniwill, or Tongfang laptops, which Tuxedo systems appear to be based on). Tuxedo provides official support for Windows and Linux, but I'm particularly interested in BSD. For reference, my specific laptop model is the Tuxedo Gemini 15 Gen 2. The issue I'm experiencing is that the fans are controlled by the embedded controller (EC), which by default does not spin the fans adequately. Updating the EC firmware hasn't resolved the problem. As a result, the laptop runs hot, and I'm concerned that prolonged operation under these conditions may degrade the hardware. - The EC does not have pre-programmed fan profiles that the software selects. - The driver writes a desired fan speed directly as an 8-bit integer (255 being full speed and 0 being off). - On Linux, a daemon communicates with the driver via IOCTL, and the driver communicates with the EC through ACPI. What options are available to enable proper fan control on BSD operating systems (specifically OpenBSD or FreeBSD) without having to write my own driver?

I'm currently trying to update and install packages and other things on a FreeBSD server, but I’m blocked by my proxy. I'm in an university, and there are a few proxies before to go on the internet. To allow us ty bypass the proxy on our main PC (Debian 7) we need to enter the path of a config file in the networks settings (auto mode in proxy menu) But I can't manage to do this to my FreeBSD server. What can I get this to work?

I have one hard drive that I want to split into two separate FreeBSD OS installs and I'm running into a wall trying to figure out how to get it working. I followed Installing FreeBSD Root on ZFS using GPT in order to get a single OS up and running. There are no problems and everything works great. However, I do not know how to modify this in order to get a second OS up and running. I repeat from steps 2 onward to create the second partition and second zpool. Once I restart the FreeBSD boot menu does not show any boot options (i.e. no option for Boot Environment in option 8). If I do a zpool import it will show my second zpool that is a part of the other partition. I can even mount it using zpool import -R /mnt zroot2 and I can see the files. This is the point I'm quite lost. I can't figure out what I did to do. I looked into efibootmgr and bectl, but I'm not sure either is the right option. bectl seems to create Boot Environments from snapshots and not from other partitions. efibootmgr seems to need the file system mounted. Essentially my current progress is: - nda0p1 efi - nda0p2 freebsd-swap - nda0p3 freebsd-zfs (OS 1) - nda0p4 freebsd-zfs (OS 2) How do I get the FreeBSD boot manager to recognize the second OS? edit1: I tried installing twice through the UI and it did put another entry into the efibootmgr, but both options boot the newest install even though they point to separate files (\EFI\BOOT\BOOTX64.efi and \EFI\freebsd\loader.efi). The original install doesn't boot. edit2: I think the reason they both boot the same instance is they're both the same UI. You copy the efi into to the BOOTX64.efi location in the steps from above. From what I understand this efi automatically finds the FreeBSD instance. How does one create an EFI that points directly to an instance?

working I installed and setup Bind9 official package to test DNS forward zones based on source IP/subnets which unbound doesn't support I properly set NAT forwards, changed listening ports on Bind9 and configured it for DNS over TLS (see below) All works properly and DNS requests are properly forwarded and use TLS until I uncomment remote-hostname and/or ca-file options. Without them, as per Bind9 doc, encryption is granted but not TLS authentication If I enable those options to ensure strict TLS authentication, clients cannot resolve DNS entries and I get the below errors in logs:

Jul 29 00:50:29	named	92197	query-errors: debug 4: fetch completed for readaloud.googleapis.com.intranet/A in 0.056869: TLS peer certificate verification failed/success [domain:.,referral:0,restart:1,qrysent:0,timeout:0,lame:0,quota:0,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0]
Jul 29 00:50:29	named	92197	query-errors: info: client @0x1414c4b10800 10.0.31.62#9512 (readaloud.googleapis.com.intranet): query failed (TLS peer certificate verification failed) for readaloud.googleapis.com.intranet/IN/A at query.c:7836

I tried with different ca-file values, but no success **My working Bind9 config (with remote-hostname commented):**

tls cloudflare-tls {
//    ca-file "/usr/local/share/certs/ca-root-nss.crt";
//    ca-file "/usr/local/etc/ssl/cert.pem";
//    ca-file "/usr/share/certs/trusted/IdenTrust_Commercial_Root_CA_1.pem";
//    remote-hostname "one.one.one.one";
    prefer-server-ciphers yes;
};

options {
    forwarders {
        1.1.1.1 port 853 tls cloudflare-tls;
        1.0.0.1 port 853 tls cloudflare-tls;
        2606:4700:4700::1111 port 853 tls "cloudflare-tls";
        2606:4700:4700::1001 port 853 tls "cloudflare-tls";
    };
};

* **Bind9 Docs:** [https://bind9.readthedocs.io/en/v9.18.14/reference.html#namedconf-statement-prefer-server-ciphers](https://bind9.readthedocs.io/en/v9.18.14/reference.html#namedconf-statement-prefer-server-ciphers) > Strict TLS provides server authentication via a pre-configured > hostname for outgoing connections. This mechanism offers both channel > confidentiality and channel authentication (of the server). In order > to achieve Strict TLS, one needs to use remote-hostname and, > optionally, ca-file options in the tls statements used for > establishing outgoing connections (e.g. the ones used to download zone > from primaries via TLS). Providing any of the mentioned options will > enable server authentication. If remote-hostname is provided but > ca-file is missed, then the platform-specific certificate authority > certificates are used for authentication. The set roughly corresponds > to the one used by WEB-browsers to authenticate HTTPS hosts. On the > other hand, if ca-file is provided but remote-hostname is missing, > then the remote side’s IP address is used instead. Any help why enabling tls auth fails?

I’ve got a program that I wrote in Rust, to help me keep track of finances, as well as read/write the data that comes from an iOS app that I made to do the same thing, and I’m running into an issue. On FreeBSD, I can compile it just fine without any issues, but when I go to turn it into a port and test the port in poudriere, it complains that it cannot find libclang at all, even if I specify it in LIB_DEPEND, even though it is supposed to be present in the base of FreeBSD. The jail used by poudriere and the host are both running version 14.3. I did also see that there was indeed nothing in the location that typically holds libclang.so inside the jail, but in cases like those, I thought that it would have grabbed the port I specified according to the Porter’s handbook for LIB_DEPEND. Does anybody have an idea on how to solve this?

In Linux, an ARP entry's age gets reset/refreshed if a packet comes by. However, it seems that FreeBSD simply sets a timer, and unconditionally evicts the ARP entry even if packets with that MAC-address/IP came by. Is there a way to get Linux's behaviour of updating the age if traffic is seen? I am experiencing large bursts of ARP broadcast traffic every 20 minutes on my LAN because of this. I know that one can change the age in FreeBSD's cache, but that just changes the intervals between bursts. I want to stop the bursts in the first place.

I'm trying to boot mfsBSD ISO via PXE on a host with UEFI boot enabled. It was a pretty simple task with BIOS boot, the ipxe config for this task looked like this: kernel --name freebsd http://pxe.host/memdisk initrd http://pxe.host/mfsbsd.img imgargs freebsd harddisk raw boot Since memdisk way is not supported with UEFI boot method and it seems like there is no other way to boot mfsBSD directly, I switched to booting GRUB2 first: kernel --name grub2 http://pxe.host/grub2.efi boot So now I'm trying to boot an mfsBSD ISO from there, here's how my grub.cfg looks like: insmod efinet insmod tftp insmod loopback insmod iso9660 insmod ufs2 insmod part_msdos insmod gfxterm insmod vbe menuentry "mfs12.1.iso" { set isofile=(tftp)/mfs12.1.iso loopback loop $isofile echo "ISO mounted" set root=(loop) kfreebsd /boot/kernel/kernel.gz echo "kernel loaded" kfreebsd_loadenv /boot/device.hints kfreebsd_module /boot/kernel/ahci.ko echo "ahci.ko loaded" kfreebsd_module /mfsroot.gz type=mfs_root set kFreeBSD.vfs.root.mountfrom="ufs:/dev/md0" echo "set kFreeBSD.vfs.root.mountfrom" set kFreeBSD.mfs_type="mfs_root" echo "set kFreeBSD.mfs_type" set kFreeBSD.mfs_name="/mfsroot" echo "set kFreeBSD.mfs_name" set kFreeBSD.mfsbsd.autodhcp="YES" echo "set kFreeBSD.mfsbsd.autodhcp" } Unfortunately, the boot hangs every time with no information on screen: I've tried changing kFreeBSD.vfs.root.mountfrom to "cd9660:/dev/md0" with no result, tried different mfsBSD versions and also built an EFI-enabled ISO using this solution: https://github.com/mmatuska/mfsbsd/pull/100 Is there anything I am missing in this setup? I would greatly appreciate any help.

SSHFS changes modification date (not access date) of server files on download(!). Is there an option/setting to prevent that? The problems this causes include: - after the next download, you can't sort the files by date anymore. - when we backup to the server, every file will be transferred on every occasion (bc their dates are always different) - in the use-case of sharing updated files on the server: everything will be downloaded every occasion even if no-one uploaded anything UPDATE: After changing operating systems and taking 2 weeks to restore modification dates from backups (making sure that actually-modified files don't get their date restored...), there are two machines remaining with which we can reproduce the behavior: Server: Linux Mint 21.2, sshfs 3.7.1, fuse 3.10.5, fuse ki 7.31 fusermount3 3.10.5 Client: GhostBSD 14.2 (a modified FreeBSD 14.2-RELEASE-p1), sshfs 3.7.3, fuse 3.17.1, fuse ki 7.40, mount-fusefs 0.3.9-pre1 - Download Command: cp -pr mnt/content/ local/content/ - mount command: sshfs a@192.168.1.4:/home/a/server-dir mnt/ ----

`
df -T
Filesystem             Type     1K-blocks      Used Available Use% Mounted on
tmpfs                  tmpfs      1618628      2160   1616468   1% /run
/dev/sda5              ext3     435281408 433288172   1993236 100% /
tmpfs                  tmpfs      8093124         4   8093120   1% /dev/shm
tmpfs                  tmpfs         5120         4      5116   1% /run/lock
/dev/sda1              vfat         98304     31835     66469  33% /boot/efi
tmpfs                  tmpfs      1618624       104   1618520   1% /run/user/1000
/home/a/.Private       ecryptfs 435281408 433288172   1993236 100% /home/a
/dev/mapper/veracrypt1 ext3     391090108 368891012   2276168 100% /media/veracrypt1

` ----

`
sshfs a@192.168.1.4:/media/notcrypted/ mnt/

cp mnt/file .     that changes the server file's date

`

I'm making my first steps in FreeBSD, so please excuse any possible "linuxism". My goal is to run FreeBSD 10.2 inside virtual machine with QEMU/KVM and allow USB3 network card passthrough from the host to make it the only available WAN interface. To start QEMU/KVM I run the following: kvm -m 4096 \ -snapshot \ -hda /path/to/the/image \ -device nec-usb-xhci,id=xhci,addr=0x5 \ -device usb-host,bus=xhci.0,vendorid=0x0b95,productid=0x1790 \ -net none This is running fine, if I'm trying to start Ubuntu 16.04. The interface is up, shows up in lsusb and the address is assigned by DHCP. I'm also able to run the very same FreeBSD image with VirtualBox: the card is recognised (as it's supported by FreeBSD) and I see: pciconf -lv #skipped xhci0@pci0:0:12:0: class=0x0c0330 card=0x00000000 chip=0x1e318086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB When running QEMU monitor, info usb returns (no surprise) the same entry for the network card, both for Ubuntu and FreeBSD. The only way of adding XHCI controller in QEMU I found is to specify nec-usb-xhci, so far this is the only difference between VirtualBox and QEMU I see. Is there a way to make this USB3 passthrough to FreeBSD possible with QEMU?

I have a FreeBSD machine with an Atheros WiFi card and I want to use it as WPA Enterprise access point. I set up a RADIUS server on the FreeBSD machine and configure interface wlan0 and hostapd.conf, but I have no luck. My phone informs me that the MyWiFi network is password protected and refuses to accept my certificate. But I successfully use an access point (a white box with antennas and blue LEDs) as a WPA Enterprise access point from my phone. So I suppose I set up the RADIUS server correctly.

wlan0: flags=8843 metric 0 mtu 1500
        options=0
        ether 00:1a:cc:44:33:aa
        inet 192.168.12.1 netmask 0xffffff00 broadcast 192.168.12.255
        groups: wlan
        ssid "MyFiWi" channel 1 (2412 MHz 11g) bssid 00:1a:cc:44:33:aa
        regdomain NONE country DE ecm authmode 802.1x privacy MIXED
        deftxkey UNDEF txpower 30 scanvalid 60 protmode CTS wme burst
        dtimperiod 1 -dfs
        parent interface: ath0
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
        status: running
        nd6 options=29

My /etc/hostapd.conf:

# GLOBAL PARAMETERS
interface=wlan0
debug=0
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel

ssid=MyFiWi

# WPA/IEEE 802.11i PARAMETERS
wpa=WPA-RADIUS
wpa_key_mgmt=WPA-EAP
ieee8021x=1

# RADIUS CLIENT PARAMETERS
own_ip_addr=192.168.12.1
nas_identifier=FreeBSD
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=>

My /etc/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# home network; allow all valid ciphers
 network={
        ssid="MyFiWi"
        key_mgmt=WPA-EAP
        eap=TLS
        ca_cert="/home/MyFiWi.pem"
 }

What I do wrong?

I'm having problem of directory due to a typo in a command I wrote in my command I made a typo while writing this command chsh -s/usr/local/bin/bash/ instead of using this chsh -s/usr/local/bin/bash because of that, when I want to use the su command I receive not a directory error and I didn't know that to do. chsh -s/usr/local/bin/bash in order to solve it my self, but it gave me this error: pwd_mkdb: warning, unknown root shell, and displayed chsh: user information updated. But the issue persisted. **Additional info:** Os NAME=FreeBSD;VERSION="13.3-RELEASE-p4";VERSION_ID="13.3".

In a jail, I have installed python3.6 along python3.4. Both were installed using pkg install, no ports. I want to keep the 3.4 version for some time, but set the 3.6 as default. Answers found in internet, like [this one](https://stackoverflow.com/questions/9349831/how-to-set-python-version-by-default-in-freebsd) or [this one](https://unix.stackexchange.com/questions/254660/freebsd-using-python3-in-uwsgi-instead-of-python2) either involve to myself link /usr/local/bin/python to python3.6 (what must be done again after any upgrade of the default python, what I'd like to avoid; plus there's no such link anyway); or to set DEFAULT_VERSIONS in /etc/make.conf, what has no effects on binaries installation (I've tried, nevertheless). Moreover, the virtual environment is not an option, since I want to run uwsgi, what requires the *system wide* default python to match the one in the python virtual environment of the python application it "monitors" (in my case, Django), in order to start correctly. Even if I start from inside the Django's virtual environment (providing python3.6), uwsgi detects python3.4 as the default python version. Cannot find if there is any environment variable missing neither. For information, inside the jail (and virtual environment): # printenv USER=root LOGNAME=root HOME=/root SHELL=/bin/csh BLOCKSIZE=K MAIL=/var/mail/root PATH=/usr/local/venv/dj1/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin TERM=xterm-256color HOSTTYPE=FreeBSD VENDOR=amd OSTYPE=FreeBSD MACHTYPE=x86_64 SHLVL=1 PWD=/var/log GROUP=wheel HOST=dev_web0 EDITOR=vi LANG=fr_FR.UTF-8 MM_CHARSET=UTF-8 PAGER=more VIRTUAL_ENV=/usr/local/venv/dj1

I've come across the following DTrace one-liner on https://wiki.freebsd.org/DTrace/One-Liners :

# Summarize TCP life span in seconds:
dtrace -n 'fbt::tcp_close:entry { 
    @["TCP life span (seconds):"] = quantize((uint32_t)(ticks - args->t_starttime) / hz); 
}'

It does not work on latest FreeBSD 15.0-CURRENT anymore. It errors out with:

dtrace: invalid probe specifier fbt::tcp_close:entry {
 @["TCP life span (seconds):"] = 
    quantize((uint32_t)(ticks - args->t_starttime) / hz); 
}:
  in action list: no symbolic type information is available for kernel`ticks:
    No type information available for symbol

error text above manually wrapped/indented Any ideas why DTrace cannot find ` ticks `? It finds hz `` just fine. According to the wiki page, all the one liners were tested in the past so that is not a typo. Also, I tried including sys/kernel.h as it seems to be where ticks is declared, but that did not help (it ends up needing sys/queue.h as well and even then it does not work).

I would like to force make on FreeBSD to execute the target I specify no matter if it's up to date or not. I know that it could be done with a -B flag in GNU make but I cannot find anything similar in the FreeBSD make manual page.

We are two FreeBSD lovers and a stubborn system administrators. We are trying to project a phone based on FreeBSD for several months. Emanuel Vadot and Jesper Schmitz Mouridsen have enabled the panfrost driver already,but on the rockpro RK3399,but for my phone I've chosen the smaller Radxa board. These are their github with their kernel patches code : https://github.com/evadot/drm-subtree https://github.com/jsm222/drm-subtree We are trying to see if the panfrost driver worked on that board. Unfortunately,it seems that some code is missing,such as the vop2. Anyway,I want to show you the error that we get : We would have some clarification about what's missing,what should be fixed in the code. Eventually I could hire a FreeBSD kernel developer to produce the patch needed to enable it on the Radxa board. It makes no sense to run FreeBSD on a phone without being able to use its GPU / MALI / acceleration. We need a vop2 driver. Linux driver has 5000 lines of code and supports all of the vop2 variants .compatible = "rockchip,rk3566-vop", .compatible = "rockchip,rk3568-vop", .compatible = "rockchip,rk3576-vop", .compatible = "rockchip,rk3588-vop", this 5k lines do not include support for the rk3588 newer hdmi variants but lets ignore that for now and assume that current hdmi code will work for rk356x ; also from what i've seen the current linux vop2 code is for a newer release of drm than what evadot's code uses so the api is slightly different. Please enlighten us with some lucid considerations. Someone wants help us ? Thanks.

Let me preface I am not sure if this question has been asked before, I have been Googling for answers but came up short. I want to use standard Linux/Unix commands (running this on FreeBSD) to exclude lines from a log file that match a pattern. The log file also includes "last message repeated x times" to condense log entries. As an example, I want to take this:

May 27 2023 11:07 relevant information #1
May 27 2023 11:07 relevant information #2
May 27 2023 11:08 last message repeated 3 times
May 27 2023 11:08 useless information #1
May 27 2023 11:08 last message repeated 5 times
May 27 2023 11:09 last message repeated 8 times
May 27 2023 11:09 relevant information #3
May 27 2023 11:09 useless information #2
May 27 2023 11:10 useless information #3
May 27 2023 11:10 last message repeated 6 times

And get this output:

May 27 2023 11:07 relevant information #1
May 27 2023 11:07 relevant information #2
May 27 2023 11:08 last message repeated 3 times
May 27 2023 11:09 relevant information #3

I've gotten as far as using sed commands to do this, but I don't know enough about how it works to figure it out. I am especially lost when it comes to the log lines that have multiple "last message repeated" following it. Here's what I'm working with currently:

sed '/useless information/{d;N;/last message repeated/d;}' ./logfile.txt

The above first deletes matching lines containing "useless information", then adds the next line to the namespace with N, and then is supposed to delete the resulting line if it contains "last message repeated". But it is only deleting the lines with "useless information".

I have several **gif*** interfaces on my FreeBSD box. They are representing tunnels, encrypted using racoon+ipsec. If, at some moment, one of the tunnels hangs up, I am forced to reset racoon this way: /usr/local/etc/rc.d/racoon restart But in that case all tunnels are reset, which leads to a short absence of connectivity on all my tunnels (3-5 seconds, but nevertheless). Is there any method to reset one specific gif tunnel, while not touching any other tunnels?

I would like to connect the LYLYGO T-Keyboard to my FreeBSD system (14.2) using a BT dongle. To be honest I tried two different kind of dongle,these ones : a) ugen1.6: at usbus1 ubt0 on uhub0 ubt0: on usbus1 and this one : b) ugen1.6: at usbus1 ubt0 on uhub0 ubt0: on usbus1 but both failed to establish the connection between the BT dongles and the keyboard. This is how I have configured FreeBSD : /etc/rc.conf bluetooth_enable="YES" blued_enable="YES" hcsecd_enable="YES" /boot/loader.conf netgraph_load="YES" vkbd_load="YES" ng_ubt_load="YES" net.bluetooth.usb_isoc_enable="0" Then,I turn on the T-Keyboard and I see the message : Wait Bluetooth. On the FreeBSD terminal,I do : marietto# hccontrol -n ubt0hci create_connection E4:B1:63:01:52:0A but I get these errors : Status: Page timeout [0x4] ugen1.6: at usbus1 ubt0 on uhub0 ubt0: on usbus1 ng_l2cap_lp_receive: ubt0l2cap - unexpected ACL data packet. Connection does not exist, con_handle=12 Limiting closed port RST response from 239 to 205 packets/sec ubt0: ubt_bulk_read_callback:1131: bulk-in transfer failed: USB_ERR_IOERROR ubt0: ubt_intr_read_callback:1032: interrupt transfer failed: USB_ERR_IOERROR ugen1.6: at usbus1 (disconnected) I have no idea how to make it work.