I have other devices in MGMT vlan which I can ping, and I can ping nethserver so don’t believe it’s routing issue. In conf2-4 the installation is successful and with slight exception to conf3 (which I really struggled to figure out) I could also ping the AD form nethserver, but have never been able to ping the AD from any other machine. before installation of active directory, create br0, enable vlan filtering, install active directory, configure vb-nsdc with pvid and vlan 100.Ĭonf4: set the hosts PF connection to switch from trunk to vlan100, no libvirt vlan tag, install from fresh again (no vlan anything - so purely managed in physical switch) before installation of active directory, create eth.100, create br0 on eth.100.Ĭonf3: remove libvirt vlan tag. I have tried a multitude of configurations:Ĭonf1: using libvirt to set the vlan tag of the virtual ethernet device given to nethserver causes failure on installation of active directory components (nsdc i think), because I think there’s an unhandled error when enabling vlan filtering.Ĭonf2: remove libvirt vlan tag. However, I am using virtual ethernet devices as my host device has SR-IOV compliant network adaptors. My system is virtualised (QEMU/KVM) and I have read the remarks about virtualising bridge and promisc mode in manual. ping nethserver (expected ping / got ping).I’m experiencing this issue with the active directory support, which creates nsdc container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |