13.0-p4 losing static IP during boot

covacat said:
is the kenv msg showing up during boot, before the login prompt is shown ?
you can hack /etc/rc like this
add
set -x at the top before the stty line
...
set -x
stty status '^T' 2> /dev/null
....
enable console.log in /etc/syslog.conf
....
# uncomment this to log all writes to /dev/console to /var/log/console.log
# touch /var/log/console.log and chmod it to mode 600 before it will work
console.info /var/log/console.log
.....

remove the rc_system line from loader.conf
reboot
grep the rc_system line in console.log
Click to expand...

Hello there...

I did exactly as you instructed, but again, there is no line refering to "rc_system" inside the dump of /var/log/console.log

:-/
 
vboxnet_enable="YES"
Click to expand...
Do you use VirtualBox?

Anyway, if you use real hardware for FreeBSD (and I think it's the case, reading your posts), these lines have nothing to do in your rc.conf.
vboxguest_enable="YES"
vboxservice_enable="YES"
Click to expand...
This is used when FreeBSD is running inside a host.
 
SirDice said:
One of the few services that are enabled by default. Don't need to set this.

Code: 
inetd_enable="YES"
inetd_flags="-Ww"
Who uses inetd(8) in this day and age?

Code: 
dsbmd_enable="YES"
I don't recognize that one. What does it do?

Code: 
vboxnet_enable="YES"
vboxguest_enable="YES"
vboxservice_enable="YES"
It's a guest and a host?
Click to expand...

I removed the other unnecessary lines. As for the
Code: 
dsbmd_enable="YES
it is a system for automatic mounting of external drives,
I took from here: Configuration – Automount Removable Media
 
i suspect one of the services has support for ghostbsd because the rc_system kenv thing is a ghostbsd setting and that service does some weird shit
 
Emrion said:
Do you use VirtualBox?

Anyway, if you use real hardware for FreeBSD (and I think it's the case, reading your posts), these lines are nothing to do in your rc.conf.

This is used when FreeBSD is running inside a host.
Click to expand...
Yes I use it occasionally.

Removed the other useless lines. Thank you for helping in the cleanup.
 
covacat said:
i suspect one of the services has support for ghostbsd because the rc_system kenv thing is a ghostbsd setting and that service does some weird shit
Click to expand...
Ah... the only thing related to GhostBSD here is this:

Code: 
# pkg info | grep GhostBSD
networkmgr-6.1                 FreeBSD/GhostBSD network connection manager

but I have been using this software for quite some time now, without any issue.
I don´t think it may be related...
 
cmoerz said:
If everything else fails, you could attempt a freebsd-update IDS to check for unexpected changes or even reinstall your rc scripts by doing a make installworld. If you want to avoid compiling world, you could also just download the txz files and extract them over your existing base files.

Obviously, the latter is the nuclear option and not necessarily the best choice since it won't help you find the root cause for your issue.
Click to expand...
Hello cmoerz.

I performed a make buildworld and make installworld after the update, just in case, but it didn´t work either.
 
covacat said:
well the problem is network related , ghostbsd related so it must be a duck
Click to expand...
Great news!

I deleted the networkmgr-6.1 package, rebooted and voilà... static IP assigned correctly after boot, again.

So, it seems that package and rc_system stuff is really the culprit.

Maybe a bug report on this should be filled?

Thank you very much covacat, and all the others, you guys are really something!

How not to love FreeBSD?!
 
You must log in or register to reply here.
Back
Top