New answers tagged

0

Sometimes you just need to go to sleep and you'll wake up with the answer. I fixed my own problem. I had checked the VLAN tagging on the individual physical NICs but not on the actual Team Interface in the Microsoft NIC Teaming configurator. I guess when it was created it was tagged as VLAN 99 and not set to Default. Setting is to Default has fixed my ...


0

For anyone following this thread... I also posted my question here, and got the answer. The syntax for moving a port between VLAN 100 and the default VLAN is: root@liux:~# ovs-vsctl get port dpdk1 tag [] root@liux:~# ovs-vsctl set port dpdk1 tag=100 root@liux:~# ovs-vsctl get port dpdk1 tag 100 root@liux:~# ovs-vsctl set port dpdk1 tag=[] root@liux:~# ovs-...


0

This network really needs to be sorted out and renumbered into different networks. There are no "nice" solutions to this problem as the entire design of IPV4 is broken. You can add individual IP addresses to directly connected routing tables with commands (assuming VLANA connects to eth0 and VLANB to eth1) like ip route add 192.168.0.10 dev eth0 ip ...


0

Give fwupd a try to make sure all your firmware is up to date. # install dnf install fwupd # check for compatible devices fwupdmgr get-devices # pull in newest update database fwupdmgr refresh # Gets the list of updates for connected hardware fwupdmgr get-updates # Run the updates fwupdmgr update Hope this helps you and others having similar problems.


0

I have solved it. I had the mistaken idea that vlan is added when moving from regular netdev to a vlan netdev, the opposite is the truth. vlan is added when the packet move from the vlan netdev to the regular one, it is removed when the packet is moving from the regular netdev to the vlan one. The point of the test was to varify the pc (1) did in-fact had ...


Top 50 recent answers are included