Hi,
I have an Intel 1000CT NIC in an HP Microserver 40L running FreeNAS 8.3.0-RELEASE-p1-x64 (r12825). I have the server connected to a Netgear GS108Tv2 VLAN capable switch. I intend to use VMWare ESXi in future (NFS/iSCSI) so currently using a VLAN trunk between the switch and the FreeNAS server to pass vlan10 for my internal LAN (10.1.2.0/24). FreeNAS has been working fine until recently using VLAN10 on physical NIC em0, until I tried configuring plugins. I followed the instructions on the FreeNAS wiki for installing the Jail software and plugins. Each time I'd start the plugin I could ping the Jail IP from the FreeNAS shell and also could ping the FreeNAS IP and default gateway from within the Jail. DNS resolution was also working. The problem was the transmission plugin icon would not appear in the plugins tree menu. The console showed the following:
Dec 21 15:08:36 freenas kernel: bridge0: Ethernet address: 02:79:15:d1:df:00
Dec 21 15:08:36 freenas kernel: epair0a: Ethernet address: 02:33:00:00:0c:0a
Dec 21 15:08:36 freenas kernel: epair0b: Ethernet address: 02:33:00:00:0d:0b
Dec 21 15:08:36 freenas kernel: epair0a: link state changed to UP
Dec 21 15:08:36 freenas kernel: epair0b: link state changed to UP
Dec 21 15:08:36 freenas kernel: epair0a: promiscuous mode enabled
Dec 21 15:08:36 freenas kernel: bridge0: error setting interface capabilities on vlan10
Dec 21 15:08:36 freenas kernel: em0: promiscuous mode enabled
Dec 21 15:08:36 freenas kernel: vlan10: promiscuous mode enabled
Dec 21 15:10:13 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://10.1.2.2/plugins/transmission/_s/treemenu: timed out
I then reconfigured FreeNAS to enable DHCP on em0 (physical NIC). The port on the Netgear switch was reconfigured to untagged with a PVID of 10. I rebooted FreeNAS and em0 got the correct IP (10.1.2.2.) via DHCP in the same network range as the Jail IP. I was able to ping the Jail from FreeNAS and vice-versa as before. After stop/start of the plugins under control services, the transmission icon appeared ok in the tree menu. I have also been able to successfully install minidlna which also now appears in the tree menu.
I would like to know if there are any known issues with using plugins on a VLAN interface (not default em0)?
The interesting message when using a vlan interface seems to be "error setting interface capabilities on vlan10". I can't seem to find any more information on what capabilities are trying to be set.
Any help would be much appreciated!
Cheers,
Mark.
I have an Intel 1000CT NIC in an HP Microserver 40L running FreeNAS 8.3.0-RELEASE-p1-x64 (r12825). I have the server connected to a Netgear GS108Tv2 VLAN capable switch. I intend to use VMWare ESXi in future (NFS/iSCSI) so currently using a VLAN trunk between the switch and the FreeNAS server to pass vlan10 for my internal LAN (10.1.2.0/24). FreeNAS has been working fine until recently using VLAN10 on physical NIC em0, until I tried configuring plugins. I followed the instructions on the FreeNAS wiki for installing the Jail software and plugins. Each time I'd start the plugin I could ping the Jail IP from the FreeNAS shell and also could ping the FreeNAS IP and default gateway from within the Jail. DNS resolution was also working. The problem was the transmission plugin icon would not appear in the plugins tree menu. The console showed the following:
Dec 21 15:08:36 freenas kernel: bridge0: Ethernet address: 02:79:15:d1:df:00
Dec 21 15:08:36 freenas kernel: epair0a: Ethernet address: 02:33:00:00:0c:0a
Dec 21 15:08:36 freenas kernel: epair0b: Ethernet address: 02:33:00:00:0d:0b
Dec 21 15:08:36 freenas kernel: epair0a: link state changed to UP
Dec 21 15:08:36 freenas kernel: epair0b: link state changed to UP
Dec 21 15:08:36 freenas kernel: epair0a: promiscuous mode enabled
Dec 21 15:08:36 freenas kernel: bridge0: error setting interface capabilities on vlan10
Dec 21 15:08:36 freenas kernel: em0: promiscuous mode enabled
Dec 21 15:08:36 freenas kernel: vlan10: promiscuous mode enabled
Dec 21 15:10:13 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://10.1.2.2/plugins/transmission/_s/treemenu: timed out
I then reconfigured FreeNAS to enable DHCP on em0 (physical NIC). The port on the Netgear switch was reconfigured to untagged with a PVID of 10. I rebooted FreeNAS and em0 got the correct IP (10.1.2.2.) via DHCP in the same network range as the Jail IP. I was able to ping the Jail from FreeNAS and vice-versa as before. After stop/start of the plugins under control services, the transmission icon appeared ok in the tree menu. I have also been able to successfully install minidlna which also now appears in the tree menu.
I would like to know if there are any known issues with using plugins on a VLAN interface (not default em0)?
The interesting message when using a vlan interface seems to be "error setting interface capabilities on vlan10". I can't seem to find any more information on what capabilities are trying to be set.
Any help would be much appreciated!
Cheers,
Mark.