Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    pfSense not enabling port

    Scheduled Pinned Locked Moved
    General pfSense Questions
    4
    145
    3.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      The status of the bridge device is not really important compared to that of the actual NIC. The bridge could appear up even if the NIC is not.

      I would check the NIC stats and see if you see any incoming packets on it. ip -s link show enp4s0f0

      georgelzaG G 2 Replies Last reply Reply Quote 0
      • G
        Gblenn @georgelza
        last edited by

        @georgelza said in pfSense not enabling port:

        @Gblenn I figured i'd give the host a ip on the network the card lives.
        i will then give the guest vm's their own ip's on that network also.

        can easily remove that 30.11

        G

        Leave all that to pfsense instead, that's where you want to control all those things, including all your static IP's. If you have set up the Unifi SFP+ port as VLAN 30 Untagged, then anything on the Proxmox side will of course get an IP from that range.

        georgelzaG 1 Reply Last reply Reply Quote 1
        • georgelzaG
          georgelza @stephenw10
          last edited by

          @stephenw10

          root@pmox1:~# ip -s link show enp4s0f0
6: enp4s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr30 state DOWN mode DEFAULT group default qlen 1000
    link/ether a8:b8:e0:05:f0:91 brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
        236040    3934    282       0       0    3934 
    TX:  bytes packets errors dropped carrier collsns           
      11447434   67461      0       0       0       0 
root@pmox1:~#
          1 Reply Last reply Reply Quote 0
          • G
            Gblenn @stephenw10
            last edited by

            @stephenw10 It's already in the info pasted above, showing NO-CARRIER and DOWN so it doesn't seem to be working unfortunately...

            1 Reply Last reply Reply Quote 1
            • georgelzaG
              georgelza @Gblenn
              last edited by

              @Gblenn

              I normally do dhcp reserve assignment on pfSense for all devices... aka control/manage i from that side.

              G

              G 1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ah, yes. try: ethtool enp4s0f0

                georgelzaG 1 Reply Last reply Reply Quote 0
                • georgelzaG
                  georgelza @stephenw10
                  last edited by

                  @stephenw10 said in pfSense not enabling port:

                  ethtool enp4s0f0

                  root@pmox1:~#  ethtool enp4s0f0
Settings for enp4s0f0:
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  10000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10000Mb/s
        Duplex: Full
        Auto-negotiation: off
        Port: FIBRE
        PHYAD: 0
        Transceiver: internal
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
root@pmox1:~#
                  1 Reply Last reply Reply Quote 0
                  • G
                    Gblenn @georgelza
                    last edited by

                    @georgelza Yes, so no need to set the IP, it's one of the things that made me think it was working when I saw it...

                    So when you ping from Proxmox, I guess in this case you were pinging inside the virtual switch of Proxmox and got that ICMP response. Meaning it never left Promxox...

                    And when you then ping from the PC, you can see that it times out. The response from 172.16.30.1 comes from pfsense obviously.

                    1 Reply Last reply Reply Quote 1
                    • georgelzaG
                      georgelza
                      last edited by

                      and from the logs

                      Oct 31 16:46:17 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered disabled state
Oct 31 16:46:17 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered blocking state
Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered forwarding state
Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
                      G 1 Reply Last reply Reply Quote 0
                      • G
                        Gblenn @georgelza
                        last edited by

                        @georgelza So it looks like there is something happening at least. But it states auto-negotiation : no.

                        So what if you set the Unifi side to 10G and not Autonegotiate?

                        georgelzaG 1 Reply Last reply Reply Quote 0
                        • georgelzaG
                          georgelza
                          last edited by

                          have to pop out for hour, daddy duties. bbl.

                          G

                          1 Reply Last reply Reply Quote 0
                          • georgelzaG
                            georgelza @Gblenn
                            last edited by

                            @Gblenn let me try.
                            it was set to 10 GBS FDX.

                            switched it to Auto, still same.

                            G

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              It has to be auto at both ends to use that. Otherwise it should link at 10G fixed on both ends.

                              Probably need to query the module to make sure it at least sees signal on the fiber. I don't have anything to test that with but maybe: ethtool --show-module enp4s0f0

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Just to confirm this is Proxmox installed on the same Topton hardware that pfSense couldn't get link on?

                                G 1 Reply Last reply Reply Quote 0
                                • G
                                  Gblenn @stephenw10
                                  last edited by Gblenn

                                  @stephenw10 said in pfSense not enabling port:

                                  Just to confirm this is Proxmox installed on the same Topton hardware that pfSense couldn't get link on?

                                  No it's a separate machine, thinking it should work in Proxmox at least...

                                  It has to be auto at both ends to use that. Otherwise it should link at 10G fixed on both ends.

                                  Probably need to query the module to make sure it at least sees signal on the fiber. I don't have anything to test that >with but maybe: ethtool --show-module enp4s0f0

                                  It did list this at the end as per the post further up:

                                      Link detected: yes

                                  And Proxmox log was showing interface going up and down...

                                  Oct 31 16:46:17 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
                                  Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered disabled state
                                  Oct 31 16:46:17 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
                                  Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered blocking state
                                  Oct 31 16:46:17 pmox1 kernel: vmbr30: port 1(enp4s0f0) entered forwarding state
                                  Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
                                  Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
                                  Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
                                  Oct 31 16:46:18 pmox1 kernel: ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX

                                  Perhaps time to try a different module, or set of modules / fiber...

                                  georgelzaG 1 Reply Last reply Reply Quote 0
                                  • georgelzaG
                                    georgelza @Gblenn
                                    last edited by

                                    @Gblenn

                                    I've already swopped the fiber out.

                                    And tried the pfSense which was 2 modules there... and that fiber. then ran into issues and thought if we think this is pfSense not liking it lets me jst confirm things work, in a more compatible environment, so installed transceivers into my 2nd Topton that runs pmox. patched that into my Unifi Pro Max port 26 which SFP+ (SFP1), port 25 is (SFP0).

                                    and ye. we not getting much further.

                                    My unifi switch is reporting the correct SFP+ transceivers so can't image there being a problem with them, and well, they brand brand new.

                                    G

                                    G 1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      Ok but it's the same model Topton device? Same NIC?

                                      Yeah, seeing the NIC logged as changing link state like that sure looks like it should be working....

                                      georgelzaG 1 Reply Last reply Reply Quote 1
                                      • G
                                        Gblenn @georgelza
                                        last edited by

                                        @georgelza Just realized one more thing that you might try in Proxmox...

                                        What do you see from this command?
                                        dmesg | grep ixgbe

                                        georgelzaG 1 Reply Last reply Reply Quote 0
                                        • georgelzaG
                                          georgelza @Gblenn
                                          last edited by

                                          @Gblenn said in pfSense not enabling port:

                                          dmesg | grep ixgbe

                                          [175483.486743] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175484.110776] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175484.214719] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175485.462768] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175485.670734] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175485.879762] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175485.982711] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175486.398837] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175486.502809] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175486.606757] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175486.710853] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175487.230749] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175487.438681] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175489.830832] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175489.934714] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175498.150577] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175498.255548] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
[175502.414503] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[175502.518579] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Down
                                          G 1 Reply Last reply Reply Quote 0
                                          • georgelzaG
                                            georgelza @stephenw10
                                            last edited by

                                            @stephenw10

                                            pretty much yes, cpu and memory and nvme size differs, thats all.

                                            G

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post