I wasn't to happy to access that without a bit of preparation, but did.
The media converter of that fiber access was plugged into a port, I figured out which physical NIC that was, set up a vSwitch etc

Same setup as with the existing three interfaces in that pfSense, same models of physical NICs etc

I am not sure if it is well supported to add a vNIC while the VM is running? Seems not, as soon as I tried that, the whole site went offline because that specific pfSense is the main router.

That VM didn't even boot correctly after a reset. With that vNIC atttached, even when no cable was plugged into the pNIC, the VM failed to boot normally.

I have a crash report, that's four files: info.0 and info.1, very short. And 2 tarballs(?).

May I attach them here, does that make sense?

I browsed the report in the GUI and spotted this:

pci7: <ACPI PCI bus> on pcib4
vmx3: <VMware VMXNET3 Ethernet Adapter> at device 0.0 on pci7
vmx3: Using 512 TX descriptors and 512 RX descriptors
vmx3: Using 2 RX queues 2 TX queues
vmx3: Using MSI-X interrupts with 3 vectors


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address	= 0x2b8
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80af4a16
stack pointer	        = 0x28:0xfffffe00085e3910
frame pointer	        = 0x28:0xfffffe00085e3930
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (pci_hp taskq)
rdi: fffff8008137c800 rsi: ffffffff82d8db88 rdx: 000000000000001e
rcx: fffff800058df000  r8: 0000000000000000  r9: 0000000000000010
rax: 0000000000000000 rbx: fffff8011cc34800 rbp: fffffe00085e3930
r10: 0000000000000000 r11: fffff800054e8800 r12: fffffe00085e39e0
r13: fffff80012f51010 r14: fffffe00092a4000 r15: fffff8008137c800
trap number		= 12
panic: page fault
cpuid = 0
time = 1776856634
KDB: enter: panic

Aside from that crash (thinking of a cold boot): Is it possible that the 4th vNIC messes up the interface assignments?

My idea right now is to instruct the customer to add the 4th vNIC himself while the VM is properly shut down. Ah, the NICs are of the type vmx0 .. vmx1 .. etc

Thanks for any suggestions.

I have several HA/Carp Machine pairs. Some of the secondaries run on VirtualBox on an Ubuntu Host. When this works it is quite fine. But I periodically get updates from Oracle that break my systems. I am tired of fussing with the systems when this happens.

I thought I might try KVM. Ok I got one of my pfSense systems ported over to 2cows. That was easy.

What I am strugging with now is getting my ethernet connections setup on the KVM virtual system. As usual there are lots of offerings in the Internet. Since I have real NICs out there I am NOT interested in using VLANs.

After fusing with the KVM GUI I am thinking that it is only really setup to offer one interface and I need 5. Yes I programmed Virtualbox to do that and more. I had one box with 7 ports.

So I am asking advice on handling this problem. I would like to know if kvm virsh is capable of doing this alone or if I need to use Netplan or something like it in my Ubuntubox.

Here are a list of my NICs from the friendly vboxmange.

Thanks for any input and suggestions.

Roy Eberhardt

Oh my interface names on Virtualbox are vtnet0, vtnet1, vtnet2, vtnet3, and vtnet4, which is what you expect. Because I use statics to make my virtual WANs ips work, the mac numbers matter.

NIC 1: MAC: 080027B14459, Attachment: Bridged Interface 'enp1s0f0', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 2: MAC: 080027C40FA7, Attachment: Bridged Interface 'enp1s0f1', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 3: MAC: 08002730330B, Attachment: Bridged Interface 'enp1s0f2', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 4: MAC: 080027A008AF, Attachment: Bridged Interface 'enp1s0f3', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none
NIC 5: MAC: 0800275F894C, Attachment: Bridged Interface 'enp5s0f0', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled

I have already

• disabled ALTQ -> Feature #16166
• configured multiqueue for the network interfaces. (Proxmox)

Is there anything else I need to do?

How can I check, if it works?

Thx! :)

(The beginning has a lot of packet loss because I reset the machine with more power, thinking that might be the cause. However, real traffic begins at 11:40 a.m., and you can see that the latency and packet loss increase at that point).

CPU usage is around 10%, so that shouldn't be the problem. I have disabled ‘hardware checksum offload’. There is no difference, except that CPU usage is higher.

I don't know what else could be causing this. Many thanks in advance for your help.

i'm facing a really nasty bug with my pfSense (2.8.0) lately, after I switched to a fiber ISP provider here in germany.

Previously i had cable internet with a FritzBox as Modem / Router and a intermediate network between my virtualized pfSense and the Fritzbox (routed). This was fine for years.

What i did now (after Fiber internet became available) is the following:

I've set up a Netgear GC110P in front of my Server WAN NIC (Server is Microsoft Server 2022 with 3 NIC / where i use 2x Intel Pro 1000 as "external" network in my hyper-v config). Basically one is assigned to the WAN vSwitch and the other to the LAN vSwitch.

This worked great so far. The Switch is also taking care of other vlans but is fully configured. I just need it also as media converter between my WAN ethernet and the fiber counterpart.

I put a Bidi-GBIC with the correct wavelengths in the GC110P Switch, assigned one Copper RJ-45 port as untagged WAN vlan and did the same for the fiber SFP port with the Gbic. (basically creating a bridge between these two)

PfSense is using DHCP together with DHCP6 on the WAN interface.

Now the problem:
After some time IPv4 stops working completly (IPv4 from DHCP keeps getting assigned by the pfSense, but no traffic is possible outgoing and incoming). Also DHCPv4 request are left unanswered (from what i see in the logs).

I already tried disabling all the Hyper-V "optimizations" on the WAN port. But it doesn't help.

Interrestingly i see the following DHCP requests going out to the WRONG DHCP Server (not the ISP internal IP / Cisco Gateway). The real ISP gateway IP should be 10.216.0.1

Something is really off here. When I restart the firewall or just "Save & Apply Changes" on the WAN interface, everything is working again.

From the following condition the routing never recovers on it's own (ignore PPPOE in the naming of the gateway, it's just plain ethernet):

This is what i disabled for the WAN Nic in the Hyper-V hypervisor:

Any ideas? I'm planning to put a bare metal firewall in between for further troubleshooting / debugging, but personally - i think it's unlikely the virtualization, right?

[2.8.0-RELEASE][root@pfSense]/dev: gpart show
=>      40  10485680  da0  GPT  (5.0G)
        40      2008    1  freebsd-boot  (1.0M)
      2048   2097152    2  freebsd-swap  (1.0G)
   2099200   8386520    3  freebsd-zfs  (4.0G)

[2.8.0-RELEASE][root@pfSense]/dev: df -h /
Filesystem              Size    Used   Avail Capacity  Mounted on
pfSense/ROOT/default    2.0G    1.7G    297M    85%    /

[2.8.0-RELEASE][root@pfSense]/dev: zpool list pfSense
NAME      SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
pfSense  3.94G  3.24G   709M        -         -    65%    82%  1.00x    ONLINE  -

[2.8.0-RELEASE][root@pfSense]/dev: zpool get autoexpand
NAME     PROPERTY    VALUE   SOURCE
pfSense  autoexpand  on      local

Morning, above is my VM Lab-Network on my Lab Server. I want to create a real case scenario Network for testing before implementing it on my Production Server / VM Production-Network and the Main-pfSense Box.

I will be using pfSense baseline guide with VPN, Guest and VLAN support on all pfSense OS. As I learn new techniques, I want to test them first in the Lab to Production to Main.

Can anyone link me to an article(s) that will show me how to properly create the VLAN's on the Lab-Network?

Thanks!...