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

    Not pinging Netgate Vlan's

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    72 Posts 3 Posters 10.6k 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.
    • A
      afcarvalho @stephenw10
      last edited by

      @stephenw10 the Netgate has a static IP 192.168.104.1
      Cisco Switch has a Static IP 192.168.104.2

      I connect my pc to the cisco switch and I cannot ping the Netgate 192.168.104.1...

      stephenw10S 1 Reply Last reply Reply Quote 0
      • J
        Jarhead @afcarvalho
        last edited by

        @afcarvalho First, 172.168? That's a public IP and shouldn't be used on your private lan.
        Second, where did that come from? On the topographic pic you posted they were all 192.168 networks.

        Can you access the LAN from your switch?
        It's the untagged network so you should be able to get to that on a vlan 1 switchport.

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

          @afcarvalho said in Not pinging Netgate Vlan's:

          I connect my pc to the cisco switch and I cannot ping the Netgate 192.168.104.1...

          But when you connect to the switch CLI can it ping 192.168.104.1?

          A 1 Reply Last reply Reply Quote 0
          • A
            afcarvalho @Jarhead
            last edited by

            @jarhead I can change the Vlan IP's
            If I connect my pc to the trunk port, I'm able to ping the Cisco Switch IP 192.168.104.2
            I'm gonna change the Vlan IP to 192.

            J 1 Reply Last reply Reply Quote 0
            • J
              Jarhead @afcarvalho
              last edited by Jarhead

              @afcarvalho Ping all pfSense interfaces from the switch.
              Any replies?

              Just saw Stephen already asked that. 😄

              A 1 Reply Last reply Reply Quote 0
              • A
                afcarvalho @stephenw10
                last edited by

                @stephenw10 I'm gonna try and I'll get to you

                1 Reply Last reply Reply Quote 0
                • A
                  afcarvalho @Jarhead
                  last edited by

                  @jarhead No response when pinging pfSense interfaces

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    afcarvalho @afcarvalho
                    last edited by

                    But now I've tried to ping from the Cisco Telnet Client and I get:
                    60e2c21f-5e1d-4be6-8d35-5b0a72cd2ede-image.png

                    My mind goes banana's...

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      afcarvalho @afcarvalho
                      last edited by

                      322747e3-23a7-4cca-b422-b46c1dd3e205-image.png

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

                        The switch may not have a gateway/default route to try to access the other subnets via pfSense. But at least it can ping the LAN IP proving the link.

                        A 1 Reply Last reply Reply Quote 0
                        • J
                          Jarhead @afcarvalho
                          last edited by

                          @afcarvalho The vlans aren't getting to the cisco switch.
                          Did you apply all settings in the 1100 switch?
                          Something has to be off in it.

                          A 1 Reply Last reply Reply Quote 0
                          • A
                            afcarvalho @stephenw10
                            last edited by

                            @stephenw10 Which Switch: pfSense or Cisco?

                            J 1 Reply Last reply Reply Quote 0
                            • J
                              Jarhead @afcarvalho
                              last edited by

                              @afcarvalho The 1100, pfSense.

                              1 Reply Last reply Reply Quote 0
                              • A
                                afcarvalho @Jarhead
                                last edited by

                                @jarhead Yes, I did.

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

                                  The Cisco switch has an IP in the LAN subnet so it can ping other devices in that subnet like the 1100. But if it doesn't have a gateway/default route set it won't be able to ping anything outside that subnet like the VLAN interfaces. It doesn't itself have an IP in the VLAN subnets.

                                  J 1 Reply Last reply Reply Quote 0
                                  • J
                                    Jarhead @stephenw10
                                    last edited by

                                    @stephenw10 said in Not pinging Netgate Vlan's:

                                    The Cisco switch has an IP in the LAN subnet so it can ping other devices in that subnet like the 1100. But if it doesn't have a gateway/default route set it won't be able to ping anything outside that subnet like the VLAN interfaces. It doesn't itself have an IP in the VLAN subnets.

                                    True, but when he plugged a pc directly into the 1100 he couldn't ping any of the vlans either.
                                    Something has to be wrong in the 1100 switch.

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      Jarhead @afcarvalho
                                      last edited by

                                      @afcarvalho Show a pic of the internallan interface page.

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        afcarvalho @Jarhead
                                        last edited by

                                        @jarhead 36a2c14b-48eb-4652-8460-ba019d8d2144-image.png

                                        ef315cc4-4fbc-4d67-964c-419c79068a83-image.png

                                        A J 2 Replies Last reply Reply Quote 0
                                        • A
                                          afcarvalho @afcarvalho
                                          last edited by

                                          Well guys, I do appreciate your effort in trying to help me but I need to rest for today.
                                          I'll continue tomorrow the chalenge...
                                          See you!
                                          A

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            Jarhead @afcarvalho
                                            last edited by

                                            @afcarvalho What type of nic do you have in the pc you're using?
                                            Can you add a vlan tag to it? Check in nic properties/configure/advanced.

                                            If you can tag a vlan, make it 30. Then plug directly into the router and see what you get for an IP.

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