Something is really strange.
For Windows it's recommended VBoxSVGA + 3D, for Linux it's VMSVGA + 3D but if I enable 3D for FreeBSD it forces a switch from VBoxSVGA to VMSVGA (while it works for Windows). And under FreeBSD this is what is started /usr/local/bin/VBoxClient --vmsvga. So I guess...
I think I found the problem. I had to switch to VBoxSVGA but then I get this warring:
So I guess the recommended one is a no go if we want the vboxvideo working.
Thanks for pointing me in the right direction !
I'm not sure. Everything is set to auto. I get this in the log:
[ 8.992] (II) Module int10: vendor="X.Org Foundation"
[ 8.992] compiled for 1.21.1.11, module version = 1.0.0
[ 8.992] ABI class: X.Org Video Driver, version 25.2
[ 8.992] (II) Loading sub module "int10"
[...
Hello,
with the current virtualbox-ose-additions (6.1.50) the Xorg is stuck with 2 resolution: 1024x768 and 800x600 and cannot be resize like before (or under Linux). Any idea if it's because the "additions" are old (6 vs 7) or I have to do something?
Only a reboot fixed it. And I removed the accept filters. There is something wrong with them or at least the "data" one. If I have more time I'll try to look into it.
Using this I was able to unload it. But I'm not sure it's a clean unload as the port is still open and the whole operation is not recommended. So I guess it's not cleaning up before it unloads itself.
If this is not the culprit then I'm at a total loss.
-f should force it even if it is in use.
Still I checked it just to be sure and it really does not support unload events:
accept_filt_generic_mod_event(module_t mod, int event, void *data)
{
struct accept_filter *p;
struct accept_filter *accfp = (struct accept_filter *) data...
Of course it shows sshd. There is not problem with lsof itself.
The configurations of exim and dovecot have not changed for years.
Inetdis local LAN ftpd only just double checked it - a leftover from the old days. I stopped it just in case but 993 is still open.
PS: Stopped exim too just in...
That's the whole point of this thread - it is strange. I'm using FreeBSD for 20 years and I have published kernel patches for it for the routing part so if it was something simple this thread would not exists 😁
I have nothing else that uses 993 and after you connect to the port it it unresponsive:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
tbyte 33896 146.9 39.8 4049316 2477368 2 I+ 14:54 130:16.54 /usr/local/openjdk18/bin/java -Xmx2048M -Xms2048M -jar...
I know what they are used for and that is the problem. Dovecot is not running and can not start because those ports are open ... by something. And I think '?' means the kernel itself.
Why would you even presume it's not as root ?
That semi-worked
Still not too much information on what is going on.
Any idea what has opened all those ports?
I've seen those question marks for few years now and they are not helpful at all.
It's FreeBSD 14.0-RELEASE-p3 #0: Mon Dec 11 04:56:01 UTC 2023
I can connect to the port
But it doesn't show in the netstat output.
Could it have something to do with 'accf_data' module ?
Well, literally the same happens with AVAGO MegaRAID SAS 9361-8i. Under Linux it's full speed of the HDD and under FreeBSD it's 23MB (dd bs=1M, bs=16M doesn't matter) and I'm talking about the read performance.
PS: Found a working solution https://forum.opnsense.org/index.php?topic=28381.0...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.