nomadbsd / NomadBSD

Livesystem based on FreeBSD
http://nomadbsd.org
BSD 2-Clause "Simplified" License
361 stars 42 forks source link

Bridge0 network interface is destroyed at some point of the NomadBSD booting process. #135

Closed Marietto2008 closed 1 year ago

Marietto2008 commented 1 year ago

Hello.

Some setting is wrong because bridge0 for some reason is destroyed at some point of the booting process and when NomadBSD is fully loaded it is not present on the network configuration,like you can see here :

https://pastebin.ubuntu.com/p/7xSQXnDfxG/

I can show you some important configuration files,with the hope that you understand why that happens and any bhyve VM can't connect to internet.

/boot/loader.conf : https://pastebin.ubuntu.com/p/GWBF7bFg6k/

/etc/rc.conf : https://pastebin.ubuntu.com/p/JsDYCkhh8B/

/etc/sysctl.conf : https://pastebin.ubuntu.com/p/DyWWrbFP4V/

dmesg : https://pastebin.ubuntu.com/p/FDRjh3YKgK/

very thanks.

mrclksr commented 1 year ago

Hi @Marietto2008,

it's just a guess. In /usr/local/etc/devd/networkmgr.conf comment out the line

        action "/usr/local/share/networkmgr/auto-switch.py $subsystem";

with a #.

Marietto2008 commented 1 year ago

NomadBSD is affected by a serious bug "FUSE protocol violation for server mounted at /usr/local : cache incoerent ! To prevent data corruption disable the data cache by mounting with -o direct_io". I tried to fix it by modifying the script located on /etc/rc.d/mount_uzip :

changing this :

-o allow_other,use_ino,suid,nonempty,kernel_cache \

with this :

-o allow_other,use_ino,suid,nonempty,direct_io \

I didn't see that error anymore,but unfortunately sometimes I see a similar error,that forces me to reboot because the system become not usable. I've attached some screens to show you that I have attached to this email.

Il giorno mer 14 dic 2022 alle ore 10:56 mrclksr @.***> ha scritto:

Hi @Marietto2008 https://github.com/Marietto2008,

it's just a guess. In /usr/local/etc/devd/networkmgr.conf comment out the line

    action "/usr/local/share/networkmgr/auto-switch.py $subsystem";

with a #.

— Reply to this email directly, view it on GitHub https://github.com/nomadbsd/NomadBSD/issues/135#issuecomment-1350764081, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFYNC5JTYZIHGJ6QB6SIOTWNGKWVANCNFSM6AAAAAAS4I4TXQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Mario.

Marietto2008 commented 1 year ago

Pic 6 is not related to that error,so,ignore it.

Il giorno mer 14 dic 2022 alle ore 14:31 Mario Marietto < @.***> ha scritto:

NomadBSD is affected by a serious bug "FUSE protocol violation for server mounted at /usr/local : cache incoerent ! To prevent data corruption disable the data cache by mounting with -o direct_io". I tried to fix it by modifying the script located on /etc/rc.d/mount_uzip :

changing this :

-o allow_other,use_ino,suid,nonempty,kernel_cache \

with this :

-o allow_other,use_ino,suid,nonempty,direct_io \

I didn't see that error anymore,but unfortunately sometimes I see a similar error,that forces me to reboot because the system become not usable. I've attached some screens to show you that I have attached to this email.

Il giorno mer 14 dic 2022 alle ore 10:56 mrclksr @.***> ha scritto:

Hi @Marietto2008 https://github.com/Marietto2008,

it's just a guess. In /usr/local/etc/devd/networkmgr.conf comment out the line

    action "/usr/local/share/networkmgr/auto-switch.py $subsystem";

with a #.

— Reply to this email directly, view it on GitHub https://github.com/nomadbsd/NomadBSD/issues/135#issuecomment-1350764081, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFYNC5JTYZIHGJ6QB6SIOTWNGKWVANCNFSM6AAAAAAS4I4TXQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Mario.

-- Mario.

mrclksr commented 1 year ago

How is this related to the bridge issue?

Marietto2008 commented 1 year ago

There is no relation between them. Your suggestion about putting the bridge0 up worked. The bridge problem is closed. The latter problem that I have reported is different and not related to the first one.

Il giorno mer 14 dic 2022 alle ore 14:39 mrclksr @.***> ha scritto:

How is this related to the bridge issue?

— Reply to this email directly, view it on GitHub https://github.com/nomadbsd/NomadBSD/issues/135#issuecomment-1351368761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFYNC5CVSTXBR2PIR3C2K3WNHEYZANCNFSM6AAAAAAS4I4TXQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Mario.

mrclksr commented 1 year ago

Ok. Do not post to unrelated issues, please.

Marietto2008 commented 1 year ago

When I said : "I didn't see that error anymore",I talked about this error : "FUSE protocol violation for server mounted at /usr/local : cache incoerent ! To prevent data corruption disable the data cache by mounting with -o direct_io",not to the bridge0 error. So I presume it is fixed. But actually I often see the error reported on the pictures that I have attached. I'm not sure if it is related to the error "Fuse protocol violation",but I suppose yes,in some way,because the effect is similar. The system became not usable,unstable,no application reply anymore.

Il giorno mer 14 dic 2022 alle ore 14:42 Mario Marietto < @.***> ha scritto:

There is no relation between them. Your suggestion about putting the bridge0 up worked. The bridge problem is closed. The latter problem that I have reported is different and not related to the first one.

Il giorno mer 14 dic 2022 alle ore 14:39 mrclksr @.***> ha scritto:

How is this related to the bridge issue?

— Reply to this email directly, view it on GitHub https://github.com/nomadbsd/NomadBSD/issues/135#issuecomment-1351368761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFYNC5CVSTXBR2PIR3C2K3WNHEYZANCNFSM6AAAAAAS4I4TXQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Mario.

-- Mario.