Navigation

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

    [solved]package install - no route to host

    pfSense Packages
    2
    3
    273
    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.
    • O
      oldfart last edited by oldfart

      V.2.4.5 trying to install pfBlockerNG-devel

      Updating pfSense-core repository catalogue...
      pfSense-core repository is up to date.
      Updating pfSense repository catalogue...
      pfSense repository is up to date.
      All repositories are up to date.
      The following 10 package(s) will be affected (of 0 checked):
      
      New packages to be INSTALLED:
      	pfSense-pkg-pfBlockerNG-devel: 2.2.5_32 [pfSense]
      	lighttpd: 1.4.54 [pfSense]
      	lua52: 5.2.4 [pfSense]
      	jq: 1.6 [pfSense]
      	whois: 5.2.17 [pfSense]
      	py37-maxminddb: 1.4.1_1 [pfSense]
      	libmaxminddb: 1.4.2 [pfSense]
      	iprange: 1.0.4 [pfSense]
      	grepcidr: 2.0 [pfSense]
      	py37-sqlite3: 3.7.7_7 [pfSense]
      
      Number of packages to be installed: 10
      
      The process will require 9 MiB more space.
      903 KiB to be downloaded.
      [1/9] Fetching lighttpd-1.4.54.txz: .......... done
      pkg-static: https://pkg.pfsense.org/pfSense_v2_4_5_amd64-pfSense_v2_4_5/All/lua52-5.2.4.txz: No route to host
      Failed
      

      pfSense can ping external hosts and is correctly resolving domain names
      There is a default gateway configured
      from terminal - pkg update completes correctly

      1 Reply Last reply Reply Quote 0
      • kiokoman
        kiokoman LAYER 8 last edited by

        System / Advanced / Networking
        -> Prefer to use IPv4 even if IPv6 is available

        from terminal
        pkg-static -4 install pfSense-pkg-pfBlockerNG-devel

        1 Reply Last reply Reply Quote 0
        • O
          oldfart last edited by

          was a routing problem - traceroute files00.netgate.com failed.
          put NAT on automatic (was manual) and solved - now need to find out exactly where the problem is!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Products

          • Platform Overview
          • TNSR
          • pfSense Plus
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy