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

    Routing issue to internet on LAN

    Scheduled Pinned Locked Moved Routing and Multi WAN
    12 Posts 2 Posters 1.8k 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.
    • T Offline
      timthetortoise
      last edited by

      I'll assume the DHCP range is a typo and you meant 10.5.1.10 - 10.5.1.254.

      I'm a bit curious about the 169.254 route at the bottom of your PC's routing table. That's not really something that needs to be there, which leads me to believe you have something else touching your routing tables - but probably isn't the cause of your issues.
      Firstly, are you able to ping 10.5.1.1 from your PC? If not, you have A) a switching issue, B) an addressing issue, or C) a firewall rules issue. My money is on A or C, as people tend to try to get too complex with VLANs and firewall rules than is necessary.
      If you're able to ping your local gateway, are you then able to ping 70.168.57.35? If not, you have a firewall rules issue. Not really much else that it could be at this point if the routing tables you posted are accurate.
      If you're able to ping your WAN address, are you then able to ping 70.168.57.34? If not, you have A) a firewall rules issue, B) a routing issue. At this point if you're able to touch your WAN IP, you should be able to touch your WAN gateway. If you're not able to, the next step should be performing a traceroute to it and making sure it takes the path you expect (assuming you don't have much else in your topology, should be PC -> LAN IP -> Gateway). If it doesn't hit the LAN IP, you've got a default gateway issue. If it doesn't hit the gateway, you probably have a firewall issue.

      1 Reply Last reply Reply Quote 0
      • A Offline
        anogmus
        last edited by

        Correct I had type it is 10.5.1.10 - 10.5.1.254

        I connected my pc directly to LAN without switch at this point. no luck

        I'm not able to bing routing IP 70.168.57.35
        If I do traceroute it's not able to get out of lan.

        I restored to default settings still no luck…

        What can I do in firewall to make it work?
        Any other thoughts?

        1 Reply Last reply Reply Quote 0
        • T Offline
          timthetortoise
          last edited by

          Ah. If you're not using a switch, you have to use a crossover cable to connect the two machines directly (assuming that both are not gigabit NICs).

          1 Reply Last reply Reply Quote 0
          • A Offline
            anogmus
            last edited by

            @timthetortoise:

            Ah. If you're not using a switch, you have to use a crossover cable to connect the two machines directly (assuming that both are not gigabit NICs).

            It's soekris net6501 device.
            And I use switch too same bad results

            1 Reply Last reply Reply Quote 0
            • T Offline
              timthetortoise
              last edited by

              Okay, so are you able to ping 10.5.1.1?

              1 Reply Last reply Reply Quote 0
              • A Offline
                anogmus
                last edited by

                @timthetortoise:

                Okay, so are you able to ping 10.5.1.1?

                Yes I am able to ping 10.5.1.1

                1 Reply Last reply Reply Quote 0
                • T Offline
                  timthetortoise
                  last edited by

                  So make sure there's a rule in your LAN section to pass any protocol, any source, any destination. If there is already, then it's down to a routing issue.

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    anogmus
                    last edited by

                    @timthetortoise:

                    So make sure there's a rule in your LAN section to pass any protocol, any source, any destination. If there is already, then it's down to a routing issue.

                    I added such rule, no luck :(

                    What in routing can cause it?

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      anogmus
                      last edited by

                      So likely I am 27 years old who has been using linux ever since been 12.
                      So after log digging and routing tests I have fixed the problem and this happened to be a bug in pfsense that is runing on some hardware such as soekris net6501 in my case.

                      Here is the problem:
                      When you first install pfsense than configure WAN and Lan, assuming you don't do any changes to LAN it will allow you to go out and ping outside from LAN.

                      1. But soon as 2-3 minutes later LAN can't ping internet.
                      2. Lan stops accessign internet soon as you do change to LAN address.

                      Problem cause:
                      The internal gateway route have been removed from DCHP! Also firewall rule removed also! by pfsense software!! Ridicules!

                      FIX:
                      Create following rules:
                      In my case my LAN is 10.5.1.1
                      Firewall > Rules
                      Select tab LAN
                      Create Rule

                      Protocol: Any
                      Source: Any
                      Destination: Any
                      Port: Any
                      Gateway: Wan gateway here

                      Than once this done:
                      Services > DHCP server
                      in field Gateway enter your LAN's gateway, in my case it is 10.5.1.1

                      Volya! Now LAN got access to internet!

                      Let me know if you have any question!

                      1 Reply Last reply Reply Quote 0
                      • T Offline
                        timthetortoise
                        last edited by

                        There's no bug, you simply did something wrong. I am posting this from a fresh install in which I tested what you're claiming happened. My guess is that you didn't update your DHCP scope. When I change my interface address and adjust the DHCP scope for it, then release/renew my IP, it works as expected.

                        1 Reply Last reply Reply Quote 0
                        • T Offline
                          timthetortoise
                          last edited by

                          Gotta eat my words on this, it looks like you did indeed discover a bug in the DHCP code. I'm able to reproduce this on 2.1.2, and I'm assuming it applies to 2.1.1 as well.
                          In my case, my DHCP client was never assigned a gateway in general, and this is reflected by there not being an "option routers" directive in the dhcpd.conf file. I am investigating where this is happening.

                          Documented here with a temporary fix: https://forum.pfsense.org/index.php?topic=75766

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