Criando seu proprio repositório de atualizações do Pfsense



  • Encontrei este topico no forum dos gringos esta noite e vou elaborar um tutorial em portugues para isso.

    Se você tem vários firewalls/servidores pfsense em sua rede local é uma boa pedida ter um repositório local para atualizações de firmware.

    topico de origem:http://forum.pfsense.org/index.php/topic,44511.msg231139.html#msg231139

    pfSense Updates Server
    
    Requirements
    1\. Web Server
    2\. Latest update image files & checksum hash files. Rename to latest.tgz & latest.tgz. <hash>3\. Text file named “version” containing version name
    
    “version” file example contents (between “---” sections):
    ---
    2.0.1-RELEASE
    
    ---
    
    Directory & file structure:
    
    .../_updaters
    |
    |- version
    |- latest.tgz
    |- latest.tgz.sha256
    
    .../_updaters/amd64
    |
    |- version
    |- latest.tgz
    |- latest.tgz.sha256
    
    Change update URL (System > Firmware > Updater Settings) on the target system to:
    
    http://<ip_address |="" dns_name="">/.../_updaters
    	or
    http://<ip_address |="" dns_name="">/.../_updaters/amd64
    
    Where “...” is the public path to the “_updaters” directory</ip_address></ip_address></hash>
    

    conteúdo da paste de updates

    pfsense update dir
    /usr/local/www/updates/_updaters$ find . | sort
    .
    ./amd64
    ./amd64/latest-nanobsd-1g.img.gz
    ./amd64/latest-nanobsd-1g.img.gz.md5
    ./amd64/latest-nanobsd-1g.img.gz.sha256
    ./amd64/latest-nanobsd-2g.img.gz
    ./amd64/latest-nanobsd-2g.img.gz.md5
    ./amd64/latest-nanobsd-2g.img.gz.sha256
    ./amd64/latest-nanobsd-4g.img.gz
    ./amd64/latest-nanobsd-4g.img.gz.md5
    ./amd64/latest-nanobsd-4g.img.gz.sha256
    ./amd64/latest-nanobsd-512mb.img.gz
    ./amd64/latest-nanobsd-512mb.img.gz.md5
    ./amd64/latest-nanobsd-512mb.img.gz.sha256
    ./amd64/latest-nanobsd-vga-1g.img.gz
    ./amd64/latest-nanobsd-vga-1g.img.gz.md5
    ./amd64/latest-nanobsd-vga-1g.img.gz.sha256
    ./amd64/latest-nanobsd-vga-2g.img.gz
    ./amd64/latest-nanobsd-vga-2g.img.gz.md5
    ./amd64/latest-nanobsd-vga-2g.img.gz.sha256
    ./amd64/latest-nanobsd-vga-4g.img.gz
    ./amd64/latest-nanobsd-vga-4g.img.gz.md5
    ./amd64/latest-nanobsd-vga-4g.img.gz.sha256
    ./amd64/latest-nanobsd-vga-512mb.img.gz
    ./amd64/latest-nanobsd-vga-512mb.img.gz.md5
    ./amd64/latest-nanobsd-vga-512mb.img.gz.sha256
    ./amd64/latest.tgz
    ./amd64/latest.tgz.md5
    ./amd64/latest.tgz.sha256
    ./amd64/version
    ./amd64/version-nanobsd-1g
    ./amd64/version-nanobsd-2g
    ./amd64/version-nanobsd-4g
    ./amd64/version-nanobsd-512mb
    ./amd64/version-nanobsd-vga-1g
    ./amd64/version-nanobsd-vga-2g
    ./amd64/version-nanobsd-vga-4g
    ./amd64/version-nanobsd-vga-512mb
    ./latest-nanobsd-1g.img.gz
    ./latest-nanobsd-1g.img.gz.md5
    ./latest-nanobsd-1g.img.gz.sha256
    ./latest-nanobsd-2g.img.gz
    ./latest-nanobsd-2g.img.gz.md5
    ./latest-nanobsd-2g.img.gz.sha256
    ./latest-nanobsd-4g.img.gz
    ./latest-nanobsd-4g.img.gz.md5
    ./latest-nanobsd-4g.img.gz.sha256
    ./latest-nanobsd-512mb.img.gz
    ./latest-nanobsd-512mb.img.gz.md5
    ./latest-nanobsd-512mb.img.gz.sha256
    ./latest-nanobsd-vga-1g.img.gz
    ./latest-nanobsd-vga-1g.img.gz.md5
    ./latest-nanobsd-vga-1g.img.gz.sha256
    ./latest-nanobsd-vga-2g.img.gz
    ./latest-nanobsd-vga-2g.img.gz.md5
    ./latest-nanobsd-vga-2g.img.gz.sha256
    ./latest-nanobsd-vga-4g.img.gz
    ./latest-nanobsd-vga-4g.img.gz.md5
    ./latest-nanobsd-vga-4g.img.gz.sha256
    ./latest-nanobsd-vga-512mb.img.gz
    ./latest-nanobsd-vga-512mb.img.gz.md5
    ./latest-nanobsd-vga-512mb.img.gz.sha256
    ./latest.tgz
    ./latest.tgz.md5
    ./latest.tgz.sha256
    ./version
    ./version-nanobsd-1g
    ./version-nanobsd-2g
    ./version-nanobsd-4g
    ./version-nanobsd-512mb
    ./version-nanobsd-vga-1g
    ./version-nanobsd-vga-2g
    ./version-nanobsd-vga-4g
    ./version-nanobsd-vga-512mb
    


  • Opa…

    Show of ball marcelloc!

    Só quem passa pelo processo de instalação/configuração de novos servidores, várias vezes por semana, sabe o quanto importante é manter MIRRORs locais de pacotes!

    Nem precisamos ir muito longe... há alguns dias o repositório oficial do projeto ficou indisponível!

    Sugestão: Você pode publicar o tutorial no nosso blog: http://www.pfsense-br.org/blog/- que tal?! ;)

    Abraços!
    Jack


Locked