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

    pfSense + Catalyst 3750G

    Scheduled Pinned Locked Moved General pfSense Questions
    15 Posts 5 Posters 1.3k Views
    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.
    • provelsP
      provels
      last edited by

      Maybe a sketchy port or cable but you've probably checked that. Dunno.

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 1
      • M
        Manguu @Derelict
        last edited by

        @Derelict Oct 6 13:59:24 kernel bce1: link state changed to DOWN
        Oct 6 13:59:24 php-fpm 41751 /rc.newwanip: rc.newwanip: Info: starting on bce1.
        Oct 6 13:59:24 php-fpm 41751 /rc.newwanip: rc.newwanip: on (IP address: 10.0.0.1) (interface: LAN[lan]) (real interface: bce1).
        Oct 6 13:59:24 check_reload_status Reloading filter
        Oct 6 13:59:25 php-fpm 41751 /rc.linkup: Hotplug event detected for LAN(lan) static IP (10.0.0.1 )
        Oct 6 13:59:27 check_reload_status Linkup starting bce1
        Oct 6 13:59:27 kernel bce1: Gigabit link up!
        Oct 6 13:59:27 kernel bce1: link state changed to UP
        Oct 6 13:59:28 check_reload_status Linkup starting bce1
        Oct 6 13:59:28 kernel bce1: link state changed to DOWN
        Oct 6 13:59:28 php-fpm 372 /rc.linkup: Hotplug event detected for LAN(lan) static IP (10.0.0.1 )
        Oct 6 13:59:28 check_reload_status rc.newwanip starting bce1
        Oct 6 13:59:28 check_reload_status Reloading filter

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by Derelict

          OK it's out of the bce driver then.

          Is that LAN interface set as I mentioned before?

          What do the switch logs say?

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 1
          • M
            Manguu
            last edited by Manguu

            yeah I had left it at default after messing with it, and the switch port I changed it to auto also.

            The switch acts like nothing is happening at all, no lights up, no change in state of link nothing.
            And to try it out, I just plugged the R8000 back into the switch and it linked up

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by Derelict

              Welp. Really difficult to say. I'd suspect a cable. Problems with Cisco switches and bce NICs hasn't come across my radar before. If the switchport is not coming up at all I can see the NIC complaining though.

              My guess is if you connect that bce to anything else it will link up just fine. Not sure what you might need to change on that switch.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 1
              • M
                Manguu
                last edited by

                Yeah really weird, Im back on my R8000 as router connected to that same switch with the same cable and everything is working. It just won't play nice with the pfSense box

                1 Reply Last reply Reply Quote 0
                • provelsP
                  provels
                  last edited by provels

                  Sounds like "Port flapping"? Maybe Google that with "3750". Maybe it's a firmware deal. Was this port part of a bundle previously? Try moving the port config to another port?

                  Peder

                  MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                  BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

                    Try swapping the bce0 and bce1 port assignment. If it's a bad port it may follow that.

                    Steve

                    1 Reply Last reply Reply Quote 1
                    • M
                      Manguu
                      last edited by

                      So after using port 24 with my R8000
                      I decided to shutdown that port and set an IP on port 23
                      And pfSense now detected my switch and vice versa (sigh)
                      Port 24 on switch works with Pc, and R8000 but not with pfSense go figure

                      Now I need to figure out how to NAT on pfSense all my vlans behind the 3750G

                      Thanks a much for the input

                      I see this community is active and very helpful

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        @Manguu said in pfSense + Catalyst 3750G:

                        Now I need to figure out how to NAT on pfSense all my vlans behind the 3750G

                        If your using auto outbound nat, it will auto do it for you once you create the gateway and the routes to the downstream router (your 3750).. All you will have to do is make sure the rules on your transit interface (the interface that gets to the 3750) allows the downstream networks in its rules.

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.