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

Correct url for updates?

Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
2 Posts 2 Posters 1.8k 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.
  • C
    Clouseau
    last edited by Mar 1, 2010, 5:02 PM

    My Alix psSense 2.0 Beta1 gives this url by default for firmware upgrades:
    http://snapshots.pfsense.org/FreeBSD_RELENG_8_0/i386/pfSense_HEAD/.updaters/
    But there is only "legacy" ;D snapshots from january 22 2010.
    (I have version: 2.0-BETA1 built on Wed Feb 24 13:22:36 EST 2010 )

    I think that this should be correct firmware upgrade url: ?
    http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/

    The latest snapshots comes from (http://snapshots.pfsense.org/):
    http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/?C=M;O=D

    If this is correct update url for 2.0 BETA1 for nanobsd - this should be fixed as default in next possible snapshot  8)

    Now you have to use this as custom update url.

    Anyway - this looks great so far. Absolute the best firewall I've used!

    –--------------------------------------------------------------
    Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit
    Multible Vmware vSphere - pfSense 2.4.x 64bit

    pfSense - FreeNAS - OwnCloud

    1 Reply Last reply Reply Quote 0
    • C
      cmb
      last edited by Mar 2, 2010, 2:51 AM

      It's already been changed. You can't use that for nanobsd yet though.

      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