Hello can anyone help me with locating a bluetooth usb device that works with FreeBSD ?

SNAX_74: you may take a look into this bsd-hardware.info If you have access to the HW/bluetooth - it is also good starting point to live boot and check if your hardware is detected.

cybercrypto, I am using a Lenovo Thinkpad x260 and bluetooth device not detected on FreeBSD ?

So I am looking for a USB plugable device

lw

antranigv: heym there is another problem

xonotic works fine in jail, however, does not show up on the server list

hey mane

mane I'm not familiar with xonotic, I'll check how it works

mane I assume you have `sv_public 1` in the configuration?

yeaH

THE SAME CONFIG WORKED JUST FINE WITHOUT THE JAIL

oops caps

mane 1) can the jail access the internet 2) are all the proper ports forwarded?

you can run `sockstat -l` inside the jail to see which sockets are being listened on

maybe there are more ports? wait I'll also check your *old* pf.conf

I assume all of these needs to be forwarded to the jail? udp_services = "{ 1194, 51820, 26000 }"

i can join the server n xonotic by typing 'connect vlepy.com

na it only listens on 26000 udp

but it doesn't show on the master server, huh?

yeah

maybe the vm can't access the master server?

idk what the master server address is

antranigv: ok how would i add another web interface to another vm?

antranigv: btw where is the tun device on my server :x

i can't see /dev/tun0

mane is openvpn running?

yeah

if so, it should be on the host, I guess, inside of ifconfig

it can also be in /dev/tun/tun0.

it is in ifconfig

but there is no tun0 file in /dev

I haven't used OpenVPN in a while, but I think tun/tap devices should be in /dev/[tun|tap]/X

for adding another web interface, you might want to setup a vHost on Apache

I think they have docs for that, altho it's been a while since I did that

ok i got the tun nodes

what about passing tun0 to the vm, antranigv?

mane you mean to the jail? you want to have a jail just for openvpn? yeah that's doable using devfs.rules

antranigv: [devfsrules_jail=11]

add include $devfsrules_hide_all

add include $devfsrules_unhide_basic

add include $devfsrules_unhide_login

#add path tun* unhide

# not strictly needed

# add path bpf unhide

# add path bpf0 unhide

add /dev/tun* tun* unhide

antranigv: vlepy.com/~wsky/devfs.rules

oops

sorry for the spam

my client has troubles with copy/paste

okay well this is good mane

but I have to ask, do you want openvpn inside a jail basically?

if so, this config might be problematic for security, basically now *every* jail will have access to openvpn

dch you might know the answer to this. if a Jail is creating a tun/tap interface, say for OpenVPN, do we need to setup unhide in devfs.rules? or can we just use OpenVPN as is, in a VNET jail, and the tun/tap device will be reachable for that jail only?

Better than system-wide OpenVPN on root :f

Maybe they’ll finally fix this bug in FreeBSD

OpenVPN can’t drop privileges

?

openvpn runs under openvpn:openvpn

ya'll maybe aware already but if not, cybersecuritynews.com/confusion-attacks-in-apache-http-server apache http has a remote root exploit, my work just found out we're vulnerable and it's all hands on deck here.

I'm using Freebsd 14.0 p5 with KDE (xorg) and startx to bring up my desktop. I ran a pkg upgrade, rebooted and tried to bring up my desktop with startx. Xorg complained about not being able to locate a .serverauth file. I search a while for an answer on the forums but decided to roll back to a previous snapshot.

I want to upgrade my machine but I would like to know how I can prevent this from happening again. It appears most of everything related to KDE Frameworks is being upgraded from 5.115.0 to 5.116.0

these serverauth much likely has nothing to do with your issue. they are warnings

maybe look for real error in Xorg.0.log

I'll have to try to upgrade again and see if the problem persits and is logged. If I suppress these warnings in startx, will that allow startx to bring up my desktop even though a warning is present?

i have no idea

when i used X i never looked at these serverauth warnings

from what I understand, these files are created when the server process exist under abnormal conditions. Changing 'enable_xauth=1' to 'enable_xauth=0' in /usr/local/bin/startx only supressed the warning but KDE still failed to load.

I appreciate your help. I'll continue to look

you need to find out real issue.

maybe try startplasma-x11 directly or whatever binary it is

and look for errors

that's in tty

f451: on 14.0 it fails to drop privileges

if i have a working hba with the mps0 driver, a working jbod, the system should instantly see the disks once i turn on the jbod?

CCFL_Man: that is normally how it works, yes

Tried pkg upgrade again and same results, I'm unable to start KDE with startx. This is my only laptop so I rolled back to a previous snapshot. I looked at the logs for x and didn't see any errors. This is the first upgrade I've had problems with. I installed FreeBSD on this laptop with about a year ago wth 13 and KDE has worked thru every update and upgrade

SponiX: thank you!

never get your minisas cables from some questionable amazon seller

m

Is it important to upgade packages? If I stay up-to-date with freebsd-update, can I not upgrade packages?

i think freebsd-update updates them

Im a newb though

I will say that you should never use ports and pkg at the same time

rending of garments and gnashing of teeth will surely follow

i was under the impression freebsd-update was only security patches and base upgrades?

The reason I'm asking is, when i upgrade packages something is getting upgraded that is breaking xorg.

I have no clue how to troubleshoot this.

But, I'm good with not updating packages if it means my laptop stays functional

logs?

errors?

pancs?

panics?

short answer, yes. But, I have no way to save them or share them. I have only this laptop and once I upgrade my packages, startx fails to load KDE and I rollback to snapshot

But, there are no errors in Xorg log after the upgrade

It's confusing. I installed FreeBSD 13 on this laptop a little over a year ago. Followed the handbook for installing KDE, drivers etc. It's performed great and I've had no problems with updating or upgrading to present day 14.0-RELEASE-p9

mvee: does a more simple window manager work?

just to decouple X from kde

topcat001: no, I've got everything configured the way I need it. I intially installed with openbox but KDE, although heavy, does well for my workflow and habits

just for testing. Install a simple wm, even twm will do, switch out your startup line in xinitrc, see if X is working, Then you know for sure it's just kde (probably needs to clear config files)

how do I change xinitrc to start twm?

just delete xinitrc and twm should load right?

copy it to a .old file

just in case

ok

exec twm at the end instead of `exec startkde` (or whatever kde now uses). Of course, check if twm is installed/in path first. Use any other wm if you happen to have it

copy and edit it

mvee, timothias: no, pkg and freebsd-update manage diffrent stuff, to stay up-to-date with packages you have to use pkg, software that comes from packages can have security issues too, if you want to reduce updates use the quarterly repo (default), to reduce even more you can check if you really want some update before, but please if you update something, then update everything to reduce problems

of something assuming a newer version of something than you have installed

i do freebsd-update fetch install, and let it rip.

then a reboot

but thats not getting pkgs ive installed, ie: irssi

so I need to update them individually through my own dilligence of checking on them each

?

pkg upgrade

topcat001: ok, created another snapshot and upgrading packages. Will test twm once installed and reboot.

ima try it!

pray for me

cool

up to date!

thanks for the info