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

    Host is transmitting and unreachable

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 587 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.
    • I
      illeatthat
      last edited by

      I have had a NAS on my network with a DHCP static mapping for 2 years, a month ago it went offline and I mapped the other NIC to the static mapping and got it working again. Yesterday the NAS went offline and most of my attempts have failed after 30 minutes or so.

      I have set the NAS to be a static IP and removed the DHCP static mapping, this lasted for a few hours and then failed.
      Rebooting the NAS will result in 30 minutes or so of connectivity before I can no longer reach the web interface or any of the containers.

      But if I do a packet capture I can see that the NAS is communicating to other devices on the network.

      What seems to be happening is that if I put the NAS on a different VLAN, I can do a static mapping and have it work, but not on the network I currently have it on. I can see that in the ARP table it says incomplete (despite having a static DHCP mapping and creating an ARP entry). I can delete the incomplete entry, but nothing seems to work.

      How can I get this to work without rebuilding the VLAN and firewall rules?

      Thanks!

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @illeatthat
        last edited by

        @illeatthat Just a guess, when it drops off is there anything using that IP? Disconnect it and see if you can ping the IP.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        I 1 Reply Last reply Reply Quote 0
        • I
          illeatthat @SteveITS
          last edited by

          @steveits
          When it drops off I can no longer ping. I disconnect it and it continues to no longer ping.

          Last night I changed to regular old DHCP on VLAN 12 (the VLAN where the NAS is supposed to be), it dropped off after 30 minutes or so.

          This morning I changed it to regular old DHCP on VLAN 10, it has been going for 2 hours.

          1 Reply Last reply Reply Quote 0
          • I
            illeatthat
            last edited by

            Interesting update.

            I put a workstation onto VLAN 12 to watch what is happening.
            After 30 minutes it seems to "drop" off the network, but it actually looks like it is dropping the gateway. The workstation I put onto VLAN 12 can still reach the NAS and obviously ping it.

            Using pfsense's "ping" tool, I can try to ping the NAS from the source address of the VLAN and it results in 100% loss. So pfsense can't see it.

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