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

    Why does losing internet make me lose my LAN?

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 3 Posters 517 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.
    • N
      NickJH
      last edited by

      My internet is currently occasionally dropping. It then costs me LAN connectivity at the same time and I don't understand this. I can see the following in my system log:

      May 16 11:54:27 pfSense kernel: igc0: link state changed to DOWN
May 16 11:54:28 pfSense php-fpm[401]: /rc.linkup: Hotplug event detected for WAN(wan) static IP address (4: 62.30.63.90)
May 16 11:54:28 pfSense php-fpm[401]: /rc.linkup: DEVD Ethernet detached event for wan
May 16 11:54:32 pfSense rc.gateway_alarm[13641]: >>> Gateway alarm: WANGW (Addr:62.30.63.89 Alarm:1 RTT:1.352ms RTTsd:.478ms Loss:22%)
May 16 11:54:32 pfSense check_reload_status[440]: updating dyndns WANGW
May 16 11:54:32 pfSense check_reload_status[440]: Restarting IPsec tunnels
May 16 11:54:32 pfSense check_reload_status[440]: Restarting OpenVPN tunnels/interfaces
May 16 11:54:32 pfSense check_reload_status[440]: Reloading filter
May 16 11:54:33 pfSense php-fpm[400]: /rc.openvpn: Gateway, NONE AVAILABLE
May 16 11:54:34 pfSense sshd[3190]: Accepted publickey for root from 172.17.2.116 port 52141 ssh2: ECDSA SHA256:EffDx8wPJEJ/JGCONYEkT4NvLBbKLwhvoy/EJcB0vRc
May 16 11:54:34 pfSense check_reload_status[440]: Linkup starting igc0
May 16 11:54:34 pfSense kernel: igc0: link state changed to UP
May 16 11:54:36 pfSense check_reload_status[440]: Reloading filter
May 16 11:54:36 pfSense php-fpm[97227]: /rc.linkup: Hotplug event detected for WAN(wan) static IP address (4: 62.30.63.90)
May 16 11:54:36 pfSense php-fpm[97227]: /rc.linkup: DEVD Ethernet attached event for wan
May 16 11:54:36 pfSense php-fpm[97227]: /rc.linkup: HOTPLUG: Triggering address refresh on wan (igc0)
May 16 11:54:36 pfSense check_reload_status[440]: rc.newwanip starting igc0
May 16 11:54:36 pfSense check_reload_status[440]: Reloading filter
May 16 11:54:37 pfSense php-fpm[30134]: /rc.newwanip: rc.newwanip: Info: starting on igc0.
May 16 11:54:37 pfSense php-fpm[30134]: /rc.newwanip: rc.newwanip: on (IP address: 62.30.63.90) (interface: WAN[wan]) (real interface: igc0).
May 16 11:54:38 pfSense php-fpm[30134]: /rc.newwanip: Gateway, NONE AVAILABLE
May 16 11:54:41 pfSense php-fpm[30134]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
May 16 11:54:41 pfSense php-fpm[30134]: /rc.newwanip: Creating rrd update script
May 16 11:54:43 pfSense php-fpm[30134]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 62.30.63.90 ->  62.30.63.90 - Restarting packages.
May 16 11:54:43 pfSense check_reload_status[440]: Starting packages
May 16 11:54:43 pfSense check_reload_status[440]: Reloading filter
May 16 11:54:44 pfSense php-fpm[75615]: /rc.start_packages: Restarting/Starting all packages.
May 16 11:54:44 pfSense anmuscle[85684]: Starting anmuscle
May 16 11:54:44 pfSense anmuscle[4545]: Stopping anmuscle
May 16 11:54:46 pfSense anmuscle[11836]: Successfully stopped anmuscle
May 16 11:54:46 pfSense anmuscle[13056]: Finished configuring DTTS pf rules
May 16 11:54:47 pfSense anmuscle[14274]: Successfully started anmuscle on 13443

      But I lost my LAN for much more than 20s. Surely I should keep my LAN but I totally lost access to my file server.

      GertjanG 2 Replies Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Not seeing any references to the LAN interface there. I assume it's igc1?

        How exactly is it lost? No access to the gui? Can't ping pfSense? Can't ping anything on LAN?

        Does it still do it if you don't have that 3rd party service running?

        Steve

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

          @NickJH said in Why does losing internet make me lose my LAN?:

          Surely I should keep my LAN but I totally lost access to my file server

          Your file server and your PC are all connected to a switch, and this switch is also connected to pfSense ?
          Even if the LAN interface went 'down' your PC and your file server wouldn't notice something, they have their network settings not changing.
          How do you access your file server ?
          Does this server has static IP setup ?
          Does your PC or file server show a network event ?
          Pretty sure you could still ping the file server.
          Windows network stuff would still be up and running.

          A fact is that DNS would be out of business for the duration of a WAN event. As soon as it unbound is restarted, local DNS will be available, if you have any host overrides defined and/or static MAC leases created.
          Check in the Resolver log if unbound was also restart - when it stopped, when it was started again. Unbound being stopped (not running) is often confounded with 'no internet' but its actually only DNS that isn't working.

          What is "anmuscle" ?

          edit :
          example :
          I start to ping my "server", 192.168.1.4 from 192.168.1.6 :
          C:\Users\Gauche>ping poweredget310 -t -4
          All I saw was :

          ....
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
Réponse de 192.168.1.4 : octets=32 temps<1ms TTL=128
...

          During this time, I restarted pfSense, which causes network event on all interfaces, and that include LAN for sure 😊

          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
          • N
            NickJH
            last edited by

            I have seen it before when I also lose my WiFi. Everything is through a dumb switch. The server is on a static IP but everything else is on a dynamic IP with fixed leases. I access the server by FQDN so, if it is not cached in the PC, needs pfSense DNS.

            In terms of "lost", from my PC I could neither SSH into pfSense or my Server using PuTTy.

            anmuscle is the ADAMnetworks adam:ONE's product's DNS filtering service. It does DNS resolution for the LAN rather than unbound.

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

              Right so does that stop resolving for some reason? Disable it and test using Unbound instead. If you are using FQDN you must be able to resolve it.

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

                @NickJH said in Why does losing internet make me lose my LAN?:

                May 16 11:54:44 pfSense php-fpm[75615]: /rc.start_packages: Restarting/Starting all packages.
                May 16 11:54:44 pfSense anmuscle[85684]: Starting anmuscle
                May 16 11:54:44 pfSense anmuscle[4545]: Stopping anmuscle
                May 16 11:54:46 pfSense anmuscle[11836]: Successfully stopped anmuscle
                May 16 11:54:46 pfSense anmuscle[13056]: Finished configuring DTTS pf rules
                May 16 11:54:47 pfSense anmuscle[14274]: Successfully started anmuscle on 13443

                Something looks like it's out of sequence here.
                When packages are restarted they are all first "stopped".
                Then started.

                Here, for "anmuscle" : the stop starts with a start (now two instances are running ?), then a stop ....
                and then a start again.
                Strange.
                I also upvote unbound here.

                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
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.