Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - franks

#1
Hi,

I did some more digging and found the following:

When I watch the bridge state while booting (bridge link) I can see that when the inferface gets resetted, the attributes change to "NO-CARRIER" and the state to "disabled. On start of the boot, state is forwarding and carrier is found - so this happens exactly, when the interface is resetted.

I tested OPNSense 22.1 - unable to install, because the same thing happens while first boot from Image :(
Installing an running PFSense works :(

Frank
#2
Hello,

I am running OPNSense 21.7.8 with XEN 4.14 (debian) today I installed debian updates and rebootet, now OPNSense is not working anymore:

On every boot, with every interface OPNSense is "reconfiguring the inferface due to feature change":


[...]
Configuring DMZ interface. . .xn2: performing interface reset due to feature change
xn2: backend features: feature-sg feature-gso-tcp4
xn2: performing interface reset due to feature change
done.
Configuring WAN interface. . .xn1: performing interface reset due to feature change
xn1: backend features: feature-sg feature-gso-tcp4
xn1: performing interface reset due to feature change
[...]


On every reset of an interface, in my Dom0 the vif-Interface belonging to the resetted interface is going down and never comes up again. So I end up with a running OPNSense and all vifs down with no connectivity.

On the next reboot - same thing.

Needless to say, that the interfaces have not changed in the xen config file at all, I do not understand, why OPNSense detects a change on every reboot.


vif = [ 'mac=00:16:3e:22:ac:fe,bridge=intern','mac=00:16:3e:3b:e8:aa,bridge=extern', 'mac=00:16:3e:4a:f8:ce,bridge=dmz' ]


I do not use openvswitch or the like, the vifs are directly added to existing bridges on VM creation.

Any help would be appreciated, my network is down :/

TIA

Frank