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

    Trunk port beetwen Cisco 3750g & PfSense 2.4.2-RELEASE

    L2/Switching/VLANs
    4
    11
    934
    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.
    • Rostyslav DidusR
      Rostyslav Didus
      last edited by Rostyslav Didus

      Hello friends.I tried to configure vlans to get separate networks like Teachers(vlan 5)10.10.108.1/22 and Drivers(vlan 10)10.10.112/22.
      First,I have configured vlan5(for test) on my cisco3750g and Cisco sf300-48pp..Made a trunk port beetwen both devices.Trunk works fine,I can communicate beetween PC's connected through access ports(vlan 5).

      The next I created vlan 5 on Pfsense.Made rules for passing traffic at vlan 5.
      Now, I have to make trunk port beetween 3750g and Pfsense to allow Teachers(vlan5) use internet.
      The trunk port from cisco 3750g to Pfsense exist(passing vlan 5).But,what about PfSense side.
      Is Pfsense already in trunking mode or it is access mode?
      Every instruction about Pfsense tuning shows me that I have to create vlans on Pfsense and make a trunk port on 3750g side and it should work.
      But I can't ping Pfsense iface(vlan5) from 3750g switch.

      I guess it's happening cause Pfsense side is'nt configured for trunking?

      Am I right?
      Help me please to get communication with Pfsense in trunking mode.

      My settings are:
      ShooterScreenshot-42-30-12-20.png
      ShooterScreenshot-40-30-12-20.png ShooterScreenshot-39-30-12-20.png ShooterScreenshot-38-30-12-20.png

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @Rostyslav Didus
        last edited by

        @rostyslav-didus Maybe you forgot that after 2.4.2 there were many updates. You missed them all. This means functionality issues and security issues.

        This means you have to read FIRST all the upgrade notices that came after 2.4.2 and check if you didn't miss a VLAN related update issues.
        Personally, I don't remember any more (why keep in mind what old software did / could / couldn't ?).

        When you decide to stick with an older version, you auto declared yourself at that moment expert on this version, as, when time passes, people just don't remember how things were done "using XP", when everybody uses "Win 10" now.
        Which means that someone that reads your question needs to remember who things were done with 2.4.2 ..... and his will greatly reduce the change of some one helping you == the chance some one answers you question.

        Except for me with my silly no-answer reply.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 1
        • bingo600B
          bingo600
          last edited by bingo600

          Can you ping it from of the Vlan5 connected pc's ?

          Btw: I do agree w. gertjan , you should upgrade your pfsense

          If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

          pfSense+ 23.05.1 (ZFS)

          QOTOM-Q355G4 Quad Lan.
          CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
          LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

          Rostyslav DidusR 1 Reply Last reply Reply Quote 0
          • Rostyslav DidusR
            Rostyslav Didus @bingo600
            last edited by

            @bingo600 I can not ping it.

            Today,I'll update to the latest PfSense version.
            Gonna make PfSense clone first.In case I am not sure if certificates and OpenVpn configuration gonna work on new Pfsense version(we've got 3 vpn working branches) ))

            Thank you !

            bingo600B 1 Reply Last reply Reply Quote 0
            • N
              NOCling
              last edited by

              Please post a Show Run Int Gi of the Cisco Port connected to the pfsense.

              Netgate 6100 & Netgate 2100

              Rostyslav DidusR 1 Reply Last reply Reply Quote 1
              • Rostyslav DidusR
                Rostyslav Didus @NOCling
                last edited by Rostyslav Didus

                @nocling
                Here it is.Part from "show run" command(cisco 3750g) about port port connected to the pfsense.

                interface GigabitEthernet1/0/1
                switchport trunk encapsulation dot1q
                switchport trunk allowed vlan 5
                switchport mode trunk

                cisco3750g_srv01#show interfaces trunk

                Port Mode Encapsulation Status Native vlan
                Gi1/0/1 on 802.1q trunking 1
                Gi1/0/47 on 802.1q trunking 1

                Port Vlans allowed on trunk
                Gi1/0/1 5
                Gi1/0/47 5

                Port Vlans allowed and active in management domain
                Gi1/0/1 5
                Gi1/0/47 5

                Port Vlans in spanning tree forwarding state and not pruned
                Gi1/0/1 5
                Gi1/0/47 5

                ***Gi1/0/47 is a trunk port(vlan 5 allowed) to cisco sf300-48pp.It works fine.

                1 Reply Last reply Reply Quote 0
                • N
                  NOCling
                  last edited by

                  Look good.
                  You can set switchport nonegotiate to.

                  Vlan 5 is created?

                  conf t
                  int vlan 5
                  ip add 10.10.108.9 255.255.255.0
                  exit
                  exit
                  ping 10.10.108.1

                  works?

                  Netgate 6100 & Netgate 2100

                  Rostyslav DidusR 1 Reply Last reply Reply Quote 1
                  • Rostyslav DidusR
                    Rostyslav Didus @NOCling
                    last edited by Rostyslav Didus

                    @nocling
                    I got it at my running config.
                    I tried #Switchport nonegotiate.Nothing changed.
                    I mean,I know you want me to create vlan 5 iface and assign IP/mask on it.
                    It is already done.

                    "Part of running config"
                    interface Vlan5
                    ip address 10.10.108.233 255.255.252.0

                    Thus,it should work(pinging vlan5 iface on PfSence). But,it doesn't.

                    My IT colleagues think that the problem is about old Pfsense version.
                    We thought,maybe we got LAN card,which doesn't support 802.1q.
                    After reading Pfsense manual I found out that it does,cause when I was chosing parent Iface for vlan 5,I could choose VMX0.It means card support 802.1q
                    I even tried another Cisco switch for trunking-nothing changed.)

                    1 Reply Last reply Reply Quote 0
                    • bingo600B
                      bingo600 @Rostyslav Didus
                      last edited by

                      @rostyslav-didus said in Trunk port beetwen Cisco 3750g & PfSense 2.4.2-RELEASE:

                      @bingo600 I can not ping it.

                      Today,I'll update to the latest PfSense version.
                      Gonna make PfSense clone

                      What net adapter type is the vmx ?

                      You say clone , is this a virtual pfSense ?

                      If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

                      pfSense+ 23.05.1 (ZFS)

                      QOTOM-Q355G4 Quad Lan.
                      CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                      LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

                      Rostyslav DidusR 1 Reply Last reply Reply Quote 1
                      • Rostyslav DidusR
                        Rostyslav Didus @bingo600
                        last edited by Rostyslav Didus

                        @bingo600
                        Yes sir!
                        My mistake-I didn't say that pfsense is on Esxi.
                        We updated pfsense. Now it got last stable version.
                        I am going to read how to make proper vlans on Esxi to allow vlan 5 flow.
                        I'll show esxi config in 2 hours.
                        Thanks.

                        bingo600B 1 Reply Last reply Reply Quote 0
                        • bingo600B
                          bingo600 @Rostyslav Didus
                          last edited by

                          @rostyslav-didus said in Trunk port beetwen Cisco 3750g & PfSense 2.4.2-RELEASE:

                          @bingo600
                          Yes sir!
                          My mistake-I didn't say that pfsense is on Esxi.
                          We updated pfsense. Now it got last stable version.
                          I am going to read how to make proper vlans on Esxi to allow vlan 5 flow.
                          I'll show esxi config in 2 hours.
                          Thanks.

                          I have not tried a pfSense on ESXi , but have a small home ESXi , where i used vSwitch to make the trunk (& Vlan definitions).

                          Someone else w. pfSense on a VM experience should chip in.
                          Have a look in this section.
                          https://forum.netgate.com/category/33/virtualization

                          If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

                          pfSense+ 23.05.1 (ZFS)

                          QOTOM-Q355G4 Quad Lan.
                          CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                          LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

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