Solved Updates

[jeditoo]

Hallo everyone,
Could you please tell me how often should I update my FreeBSD? I think once a month would be good, but further, which commands are necessary by updating? Also 2nd question, how do I export firewall configfile?
Thanks in advance.

 

[SirDice]

Could you please tell me how often should I update my FreeBSD?

Keep an eye on the security issues. Use freebsd-update(8) to keep FreeBSD itself up to date. For ports, keep an eye on pkg-audit(8), again update when there are issues using pkg-upgrade(8).

Also 2nd question, how do I export firewall configfile?

What's there to export? All firewalls work with config files, you load the firewall with that configfile.

 

[jeditoo]

Thank you for your answer. Yeah, I need to export config file to keep it as back-up. Also, the firewall is blocking the updates, I have every time to disable the firewall. Which protocols, ports are responsible and necessary for update?

 

[jeditoo]

When there is a firewall between the Windows Update agent and the Internet, the firewall might need to be configured to allow communication for the HTTP and HTTPS ports used for Windows Update. Windows Update agent uses port 80 for HTTP and port 443 for HTTPS to obtain updates.
Is this same as in Windows?

 

[SirDice]

Yeah, I need to export config file to keep it as back-up.

Then backup the config file. No need to "export" anything.

Also, the firewall is blocking the updates, I have every time to disable the firewall. Which protocols, ports are responsible and necessary for update?

It's just HTTPS or HTTP, depending on what you configured. By default it's HTTPS. A pkg -vv will show you the URL that's used for pkg(8).

 

[drhowarddrfine]

Updating and Upgrading

 

[jeditoo]

Then backup the config file. No need to "export" anything.


It's just HTTPS or HTTP, depending on what you configured. By default it's HTTPS. A pkg -vv will show you the URL that's used for pkg(8).

Thank you a lot. A pkg -vv gave me the answer!

 

[SirDice]

Sign up for the freebsd-announce mailing list. It's very low volume, you only get important announcements, like security issues, EoL status and new versions that have been released.

freebsd-announce Info Page

Or check these: https://www.freebsd.org/security/advisories.html and https://www.freebsd.org/security/notices.html
Those two are also copied here on the forums, for example: https://forums.freebsd.org/threads/freebsd-sa-20-33-openssl.77994/

 

[jeditoo]

You're amazing. I'm really a beginner, but with everyday I'm getting more and more expierenced. If I go back to that config file of IPFW. How to correctly make a backup?



Groetjes!

 

[SirDice]

I'm really a beginner, but with everyday I'm getting more and more experienced.

I was a beginner once too. We all were.

If I go back to that config file of IPFW. How to correctly make a backup?

Just backup /etc/ipfw.rules. You probably also want to backup /etc/rc.conf. Changes to the firewall shouldn't be made "on-the-fly", that's just bad form. Modify the rules list and reload them. That way you can be sure it's always set correctly.

Chapter 33. Firewalls

FreeBSD has three firewalls built into the base system: PF, IPFW, and IPFILTER. This chapter covers how to define packet filtering rules, the differences between the firewalls built into FreeBSD and how to use them

www.freebsd.org

 

[jeditoo]

I was a beginner once too. We all were.


Just backup /etc/ipfw.rules. You probably also want to backup /etc/rc.conf. Changes to the firewall shouldn't be made "on-the-fly", that's just bad form. Modify the rules list and reload them. That way you can be sure it's always set correctly.

Chapter 33. Firewalls

FreeBSD has three firewalls built into the base system: PF, IPFW, and IPFILTER. This chapter covers how to define packet filtering rules, the differences between the firewalls built into FreeBSD and how to use them

www.freebsd.org

Well I don't really know how to do that properly.

 

[SirDice]

They're just files. Copy them to some place safe (a share on another machine, external drive, that sort of thing). That's the most basic and simple way of backing anything up. A backup, in its simplest form, is nothing more than a copy of a file stored somewhere else.

If you really want to get fancy you can use a version control system like git to store changes to the file (also nicely keeps track of who made the changes). Or you set up an automated backup solution like Bacula.