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

    [SOLVED] LAN clients lost outside connection after upgrade to 2.4.4 [2.4.5-DEV]

    Scheduled Pinned Locked Moved DHCP and DNS
    16 Posts 2 Posters 2.0k Views 2 Watching
    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.
    • R Offline
      rosch
      last edited by

      Gateways:
      0_1538846232865_routing.jpg

      1 Reply Last reply Reply Quote 0
      • R Offline
        rosch
        last edited by

        The Routing log shows this:
        32990 attempting to reread config file
        radvd 32990 invalid all-zeros prefix in /var/etc/radvd.conf, line 9

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          PiBa @rosch
          last edited by

          @rosch
          Okay, that might indicate some issue with IPv6.. Does your ISP supply IPv6 ?

          Anyhow the ping 8.8.8.8 is using IPv4.. Can you check diagnoistics/routes, and to be sure also check the default-route on the workstation?

          1 Reply Last reply Reply Quote 0
          • R Offline
            rosch
            last edited by rosch

            Here my main routes, to me it looks good. I cut out some openvpn lines, it's not running anyway. LAN is 192.168.1.0.
            0_1538848655607_routes.jpg

            workstation route:
            192.168.1.0 * 255.255.255.0 U 0 0 0 br0

            ISP IPv6: I think IPv6 is supported, but the current WAN is IPv4.

            P 1 Reply Last reply Reply Quote 0
            • P Offline
              PiBa @rosch
              last edited by

              @rosch
              Does the workstation also have a default route ?

              R 1 Reply Last reply Reply Quote 0
              • R Offline
                rosch @PiBa
                last edited by

                @piba this is the full output:
                Destination Gateway Genmask Flags Metric Ref Use Iface
                10.0.3.0 * 255.255.255.0 U 0 0 0 lxcbr0
                10.0.5.0 * 255.255.255.0 U 0 0 0 docker0
                127.0.0.0 * 255.0.0.0 U 0 0 0 lo
                169.254.0.0 * 255.255.0.0 U 0 0 0 mgmt0
                192.168.1.0 * 255.255.255.0 U 0 0 0 br0

                It's a QNAP machine, the only one client I have access to to test.

                P 1 Reply Last reply Reply Quote 0
                • P Offline
                  PiBa @rosch
                  last edited by

                  @rosch
                  Seems to me like default route is missing then.. the ip on the qnap is statically configured? then you need to add a default route / default gateway on it somewhere..

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    rosch
                    last edited by rosch

                    It's not statically configured, but in pfsense there's a reservation for it.

                    In DHCP Server, I added 192.168.1.1 as the gateway, restarted QNAP's networking, but no luck.

                    P 1 Reply Last reply Reply Quote 0
                    • P Offline
                      PiBa @rosch
                      last edited by

                      @rosch
                      The 192.168.1.1 probably was already send 'by default'.. Would be easy to check if you had another client to put on that network, see if it picks up the proper default-route.. Now you might be able do a packet capture and analyze it with Wireshark.. That should show the dhcp packet indicating the default-route...

                      Or perhaps check qnap's logs see if it shows anything.?. ive never seen a qnap so cant really guide much there.

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        rosch
                        last edited by

                        Ok I'll check but it's not a QNAP issue because my solar inverter also has lost connection.

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          rosch
                          last edited by

                          Under LAN, Reserved Networks I had Block private networks and loopback addresses enabled..so I was shooting myself in the foot ๐Ÿค• . After unchecking, normal function resumed.

                          Sorry about that, and thanks for your help.

                          P 1 Reply Last reply Reply Quote 0
                          • P Offline
                            PiBa @rosch
                            last edited by

                            @rosch
                            Ay, that would cause issues indeed for a private-network.. Surely explains the solar-inverter was not having internet access. Not sure why the qnap wouldn't show its default-route though. Does it show it now? (Just interested for my own education..)

                            R 1 Reply Last reply Reply Quote 0
                            • R Offline
                              rosch @PiBa
                              last edited by

                              @piba said in [SOLVED] LAN clients lost outside connection after upgrade to 2.4.4 [2.4.5-DEV]:

                              @rosch
                              Does it show it now? (Just interested for my own education..)

                              It does:
                              default 192.168.1.1 0.0.0.0 UG 100 0 0 br0

                              P 1 Reply Last reply Reply Quote 1
                              • P Offline
                                PiBa @rosch
                                last edited by

                                @rosch
                                Okay, would have thought that would be there even if traffic was blocked. Perhaps is has some dynamic gateway monitoring or something that told it not to define that route when it wasn't available. The dhcp packet from pfSense side wouldn't be any different though afaik. But well its fixed :) i guess no further investigation is needed just to satisfy my curiosity ๐Ÿ˜‰ . Thanks for reporting back ๐Ÿ‘

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