6/21/2023 0 Comments Intel e1000 nic linux vlan![]() Digging a bit more I did see some strange 6 extra bytes at the end of the frame called VSS-Monitoring trailer. Fired up wireshark and I was seeing that the SYN packets were sent and received on the other end, the SYN-ACK was sent back but the other end was simply ignoring it. I did restore the same working configuration (minus the interface remap) into the box and the first thing I observed was that inter VLAN routing was not working. The other slight config change was that WAN was now a new VLAN instead of a different NIC. The NIC had no VLAN selected as I wanted to pass them tagged to Pfsense. ![]() Then I created a single network adapter on the VM (I had a single nic) in VirtIO mode. I started by reading all the recommendations and created a linux bridge with VLAN aware enabled. The problem started when I tried to migrate Pfsense to Proxmox. I also decided to migrate away from ESXI into Proxmox. Since I wanted to upgrade the mac mini to build a NAS (needed those SATA connectors) and the mini was getting old, I decided to build a custom "pseudo low power" PC with a new AMD Ryzen 3, 32G ram and other goodies. The switch connects to a unifi AP that supports VLANs and has multiple SSIDs The other NIC goes to a managed switch in a trunk port that has 3 VLANS + untagged for LAN Dual NIC (one on board, one thunderbolt adapter) I have been using ESXI for 5 years now on a 2011 mac mini with no issues.
0 Comments
Leave a Reply. |