Wireshark - Capture VLAN TAGs. [TESTED]

Everyone knows there usually an issue with capturing VLAN TAGs using Wireshark (Windows) unless you fix it. I do have a huge Wiki page with the solution for every single type of NIC cards that I came across, but at this moment I use very simple and which is the most important UNIFIED SETUP that always works - whatever laptop I have in hands and External Gigabit adapter that is extremely easy to get - AmazonBasics USB 3.0 to 10/100/1000 Gigabit Ethernet Internet Adapter which is basically “ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter”.

Well, the cool thing is that Windows 7 and Windows 10 don’t need external drivers for that NIC and it just works after you plug it in. VLAN TAG capturing will NOT work, but we know how to fix it according to AX88179 FAQs:

• Q: How to capture the VLAN tagged packets on Windows WireShark tool?
• A: Please set the “Packet Priority & VLAN” parameter of ASIX USB to LAN Windows drivers to “Packet Priority & VLAN Disable” to capture the VLAN tagged packets on WireShark.

The solution is to go “Network Connections” > Right Click on the interface > “Properties” > “Configure…” > “Advanced” tab > “Packet Priority & VLAN” > select “Packet Priority & VLAN Disable” > OK.

Good luck!

Cisco “bgp redistribute-internal” command.

Quick note for myself regarding “bgp redistribute-internal” command that I ALWAYS forget to put in that costs me some time to troubleshoot the issue.

As you might know, by default, iBGP learned routes are not forwarded to an IGP routing protocol through the redistribute command. To change that behavior, we have to use “bgp redistribute-internal” command under the BGP process on the redistributing router:

router bgp X
 bgp redistribute-internal

Additional info:
Redistributing Internal BGP Routes Into OSPF
Configure Redistributing Internal BGP Routes into IGP

Good luck!

Windows RDP server 100% CPU utilization - Windows bug with WDDM. [TESTED]

After hitting the same issue with another instance of Windows 10 acting as an RDP server that got stuck with 100% CPU utilization and extremely slow overall performance I decided to create this note for myself and whoever would be interested in solution (workaround) for that nasty bug that was introduced in Windows 10 version 1903.

Common symptoms:
• No other changes were made. All what happened is regular Windows Update to Windows 10 version 1903.
• RDP server is not working, you can’t connect to it.
• CPU utilization for some of the cores is 100% and system is crawling.

Solution: Start > gpedit > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services->Remote Desktop Session Host->Remote Session Environment > Use WDDM graphics display driver for Remote Desktop Connections > change it from “No Configured” to “Disabled” > reboot the machine.

If you’d like to know more about it - read this Windows 10 V1903 black screen with Remote Desktop or any other article about this bug.

Good luck!

Admin area