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

    stuck on the simplest thing - route not found

    Scheduled Pinned Locked Moved Routing and Multi WAN
    16 Posts 3 Posters 771 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.
    • P
      planetinse @Gertjan
      last edited by

      @Gertjan

      yes still all from pfsense diagnostics

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

        @planetinse

        I don't understand your answer.

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

        P 1 Reply Last reply Reply Quote 0
        • P
          planetinse @Gertjan
          last edited by planetinse

          @Gertjan
          c247b732-6d48-4b77-a9e6-a3b107c9a3b6-image.png

          and

          676f157d-8954-4725-b251-02d2ba42b4ea-image.png

          vs.

          22e36192-0574-4a0a-8191-5c5bc9e6e5a5-image.png

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

            @planetinse

            Ping from LAN works ?

            30d011f6-9386-41f5-b9ca-b0d5540dfceb-image.png

            You have more then one WAN ?

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

            P 1 Reply Last reply Reply Quote 0
            • P
              planetinse @Gertjan
              last edited by planetinse

              @Gertjan

              No its just the naming, ping from a LAN connected device does not work (just as diagnostic)

              74000771-8da6-400c-b8d7-1ad0690b613b-image.png

              Rule LAN

              65b206c0-595d-445f-9d18-81a143ed1683-image.png

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

                Keep them coming :

                @Gertjan said in stuck on the simplest thing - route not found:

                Detail your pfSense LAN settings.
                And ... the DHCP server settings.
                Did you LAN device get a lease ?

                On the LAN device : what is the IP it got ? DNS ? and ... the gateway ?
                ( a Windows PC : launch "ipconfig /all" and you can see them all )

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

                P 1 Reply Last reply Reply Quote 0
                • P
                  planetinse @Gertjan
                  last edited by planetinse

                  @Gertjan

                  Lan device gets a Lease, (static mapping in this case below) but since this not work on the firewall itself (localhost) I don't think this is a LAN issue?

                  979e2d4d-b1ac-4e96-8344-1d81485c7fd5-image.png

                  DHCP
                  7e05c363-1e1c-46c9-8f83-6edcee28927c-image.png

                  LAN
                  df4c4e02-49bb-49cd-8908-1eb3c542f14b-image.png

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

                    @planetinse said in stuck on the simplest thing - route not found:

                    Lan device gets a Lease

                    Ok, good.
                    The gateway is ? ( 172.16.10.1 !. )
                    DNS is ( should be the same ) ?

                    @planetinse said in stuck on the simplest thing - route not found:

                    static mapping in this case below

                    Doesn't work with kea .... You need static MAC DHCP leases, go back to ISC.

                    @planetinse said in stuck on the simplest thing - route not found:

                    I don't think this is a LAN issue?

                    From your LAN device, (ens160) you should be able to ping the pfSense LAN IP 172.16.10.1

                    If you wan t to use his, afaik, use ISC :

                    4fdbc65c-126b-41e8-91be-0391394135d3-image.png

                    Or set it to :

                    9c2f484e-f8a6-4860-a0d9-747c05d8b7a2-image.png

                    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 0
                    • P
                      planetinse
                      last edited by

                      Thanks i have done all those things, it had no effect on the diagnosis tools (ping, traceroute) in pfsense,

                      and same on LAN-client

                      nslookup works fine everwhere, thats why i illustrated using IP address.

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

                        @planetinse

                        Show your IPv4 routes ( Diagnostics > Routes )

                        and

                        System > Routing > Gateways

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

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          planetinse @Gertjan
                          last edited by planetinse

                          @Gertjan

                          I changed monitor to 8.8.4.4, just to check if it made any difference,
                          and also tried ping the same, it made no difference

                          85fc3f12-016d-44a4-88e2-5bad3eab4c22-image.png

                          9e517ada-8d38-466f-b85b-d7038895c401-image.png

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

                            @planetinse

                            Can't see anything out of the ordinary.

                            Your interfaces are named 'vmx', it this a VM ? If so, re check with your hypervisor, as this makes stuff more complex.

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

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              planetinse @Gertjan
                              last edited by planetinse

                              @Gertjan

                              I did backup, factory reset, setup same things, load package's from backup - all good !

                              EDIT: except HAPROXY using the wrong certificate whatever certificate i select :)

                              NogBadTheBadN 1 Reply Last reply Reply Quote 0
                              • NogBadTheBadN
                                NogBadTheBad @planetinse
                                last edited by NogBadTheBad

                                @planetinse I'm not a vmware expert, but the default route is pointing to vmx0 and 5.45.176.224 pointing to vmx1

                                Andy

                                1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

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