possible network bug

[nikkon]

my problem is that i can't force this thing to save anything. I increased it to 90 and 120. I save then reboot - back to step 1.

 

[Patrick M. Hausen]

test, reconnect, then save, then reboot?

 

[nikkon]

half the way is done. thank god.
last question: what should be the order of creation for bridge1?
If I create bridge1 before the vlan, then I cannot attach vlan to igb1. I need to remove it from the bridge then add only the vlan?
in cli is works, but in UI not so easy :)

 

[nikkon]

I just added VLAN10 as bridge member and kept igb1 outside.
let's see what happens after reboot.

@Patrick M. Hausen thanks a lot. I owe u some beer ;)

 

[Patrick M. Hausen]

The order is correct. A physical interface that is a bridge member cannot have VLANs in FreeBSD. Neither can a bridge interface have VLANs. Order is physical --> VLAN --> bridge.

Which means you have to create a bridge interface for each VLAN individually if you need anything like that. FreeBSD is not a switch.

 

[nikkon]

ifconfig bridge1
bridge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: vpn bridge
ether 58:9c:fc:10:ff:81
inet 172.16.20.2 netmask 0xfffffff8 broadcast 172.16.20.7
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: vnet0.9 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>. -> used by the specific Jail
ifmaxaddr 0 port 11 priority 128 path cost 2000
member: vlan10 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 55
groups: bridge
nd6 options=9<PERFORMNUD,IFDISABLED>

I guess that is the expected outcome.

 

[Patrick M. Hausen]

Yes - vnet0.9 is the interface of your jail.

 

[danp]

I can't contribute to fixing your problem directly -- but I am having the exact same issue with changes persisting after a Reboot.
I can put network changes in via the UI, get the connectivity I need. Then, reboot.... all reset.

Seeing you have the same reboot issue, is there some log that is written that may show the initial save then boot info?