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

Packages not available issue

Scheduled Pinned Locked Moved General pfSense Questions
2 Posts 2 Posters 749 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
    peersu
    last edited by Mar 24, 2014, 3:47 PM

    Hi guys,

    I've been running pretty much trouble free for a few weeks now, but I think I ran into an issue or a bug.

    I had to restart my pfSense box (which is on ESX) and if you login to the web GUI and click on the packages link prior to all web services being running (DNS,etc.) then you will forever not be able to see 'packages available'… it will just return that no internet connectivity is detected.

    So, my question is, if you run into this scenerio, is there a process or something from the command-line that you can cycle the check for 'internet connectivity' for the 'available packages' to refresh and work, or should I just restart and wait an extra few minutes to be sure everything is up and running.

    ...actually after typing this out I thought of another troubleshooting step that I missed... I suppose I should double-check any IP used for packages isn't blocked by snort... I don't think that is the case though.  I'll update this later tonight when I'm certain this isn't the case.

    Thanks

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Mar 26, 2014, 5:15 PM

      Snort has blocked things a time or two for users.

      You can test DNS from Diagnostics > DNS Lookup or using "host" from the shell. You can check general connectivity by trying to ping a host on the Internet by name.

      Usually if your DNS and routing are OK, and packages still do not load, it turns out to be either something like snort blocking or maybe broken IPv6 routing that makes pfSense believe you have IPv6 connectivity when you do not. See https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference for a fix for that.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received