VLANs not coming up after reboot (Nas4Free)
jibbajabba
Member Posts: 4,317 ■■■■■■■■□□
in Off-Topic
Here is a copy / paste of my post from their forums, maybe someone here can help me with this :
I am new to NAS4Free, and FreeBSD in general, so maybe someone here can give me a pointer.
I got a little bit of an issue. In installed Nas4Free on two physical servers. Each server is pretty much identical. Only difference is that one box is a 2U with 8 drive bays and one is a 16 drive bay servers and 3U.
Anyway, both servers got a dual onboard card. Initially I thought I am using bonding, but it isn't really needed as both ports going to the same switch so for now I am using one interface (igb0) for the management access (which works fine) and the other interface, igb1, I used for VLANs
The management interface is not tagged and is using the default VLAN of the switch.
Now I created two VLAN interfaces, one I want to use for its internal management (different subnet to igb0) and one for the actual storage subnet.
The problem is now that each time the server reboots, I need to "up" the igb1 interface. I tried to put the ifconfig command to "up" the interface into the rc.conf, but it seems any changes in the rc.conf are being removed / overwritten no matter what I put in there.
So any help is highly appreciated. Just as an FYI - the physical switch config is fine as Windows based installs work just fine, including VLAN tagging.
Here are some more infos (screenshots etc.)
I am new to NAS4Free, and FreeBSD in general, so maybe someone here can give me a pointer.
I got a little bit of an issue. In installed Nas4Free on two physical servers. Each server is pretty much identical. Only difference is that one box is a 2U with 8 drive bays and one is a 16 drive bay servers and 3U.
Anyway, both servers got a dual onboard card. Initially I thought I am using bonding, but it isn't really needed as both ports going to the same switch so for now I am using one interface (igb0) for the management access (which works fine) and the other interface, igb1, I used for VLANs
The management interface is not tagged and is using the default VLAN of the switch.
Now I created two VLAN interfaces, one I want to use for its internal management (different subnet to igb0) and one for the actual storage subnet.
The problem is now that each time the server reboots, I need to "up" the igb1 interface. I tried to put the ifconfig command to "up" the interface into the rc.conf, but it seems any changes in the rc.conf are being removed / overwritten no matter what I put in there.
So any help is highly appreciated. Just as an FYI - the physical switch config is fine as Windows based installs work just fine, including VLAN tagging.
Here are some more infos (screenshots etc.)
san01: ~ # ifconfig igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:30:48:cb:52:bc inet xx.xx.xx.xx netmask 0xffffffe0 broadcast 81.19.58.63 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:30:48:cb:52:bd nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0xc inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=103<RXCSUM,TXCSUM,TSO4> ether 00:30:48:cb:52:bd inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan: 40 parent interface: igb1 vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=103<RXCSUM,TXCSUM,TSO4> ether 00:30:48:cb:52:bd inet 172.16.10.1 netmask 0xffffff00 broadcast 172.16.10.255 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan: 30 parent interface: igb1
My own knowledge base made public: http://open902.com
Comments
-
Trashman Member Posts: 140Bachelor of Science in Information Systems
2015 COLOR=#008000]X[/COLOR | 2016 COLOR=#ff8c00]In progress[/COLOR | 2017 | 2018 -
jibbajabba Member Posts: 4,317 ■■■■■■■■□□Saw that too but it is not directly related. I also believe Nas4Free is based on an older code base.
I found out that you can actually configure postinit scripts through the Nas4Free UI so added the ifconfig command there to "up" the interface after a reboot.
Works, but would still love to know why that doesn't work but at least I am getting somewhere now ..My own knowledge base made public: http://open902.com