u/klabacita

The new pfSense Plus GUI is honestly impressive at first for those of us who have been using pfSense for more than 10 years. However, after using it for a while, the impact is not quite as strong.

One issue I find particularly frustrating is the “token is expired” message appearing every second. I understand that the token has expired, but having the notification appear so frequently feels excessive.

As for the traffic graphs module, I am not fully convinced yet.

This is only my personal opinion as someone who has been using pfSense since version 1.0.1, but I still find the little brother GUI to be better overall. Again, I am not trying to start a debate or create conflict; this is simply my own perspective. I do believe the new GUI will continue to improve over time, but so far, it has not been a “wow” experience for me.

I still need to test the API, and that is one area where I would give you a 10.

Thank you for your work, team.

Annoying

Hello team,

I installed Proxmox 9.1 and 9.2 on a Supermicro server with two NICs.

I have used this same server before with Windows 11 + Hyper-V, pfSense, Ubuntu, and other systems without any issues using both NICs.

During the Proxmox installation, I only configured NIC2 with a static IP on vmbr0:

192.168.2.8/24

I can manage Proxmox through the web interface and SSH without any problem. The system has also been fully updated.

However, for some strange reason, when I configure my second NIC as a bridge, vmbr1, using nic1, and connect the cable directly to either ISP1 or ISP2, both using DHCP, the VM connected to vmbr1 does not receive an IP address from either ISP.

If I check the NIC status, I get the following output:

root@proxmox-srv:~# ethtool nic1
Settings for nic1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no

I have tested this NIC by connecting it to both ISPs and also to my LAN switch.

Every time I power on the server, before Proxmox boots, I can see that both NICs are enabled and both LEDs are on. However, after Proxmox finishes booting, the LEDs on the second NIC turn off. It looks like Proxmox is disabling or shutting down the NIC.

This behavior happens with both Proxmox 9.1 and 9.2.

In dmesg, I only see this:

[    5.531579] e1000e 0000:02:00.1 nic1: renamed from enp2s0f1
[    8.332752] vmbr1: port 1(nic1) entered blocking state
[    8.332927] vmbr1: port 1(nic1) entered disabled state
[    8.333077] e1000e 0000:02:00.1 nic1: entered allmulticast mode
[    8.333258] e1000e 0000:02:00.1 nic1: entered promiscuous mode

The only NIC that works is the one I use to manage Proxmox.

Does anyone have any idea what could be causing this?