You can enable services (and thus autostart them at boot) withthis command: # systemctl enable service This means, you will need to type: # systemctl enable ufw Also, I recommend reading the wiki. https://wiki.archlinux.org/index.php/Systemd Best regards, Sebastian M. On Wed, Apr 15, 2015 at 09:39:50PM -0500, Francis Gerund wrote:

Hello!

How do I get ufw to start automatically upon Arch system startup?

The Arch wiki Uncomplicated Firewall pages says: "Start ufw as systemd service to have it running and enable it to make it available after boot. "

How do I do that?

Then it shows an example configuration (can't I just keep the default: deny all incoming, allow all outgoing)?

Then it says: "The next line is only needed *once* the first time you install the package:

# ufw enable"

That does not seem to be true - I have to do "sudo ufw enable" every time I restart the system.

Then, it says: "Then enable the ufw service with systemctl." How? Bottom line: ufw works okay, I just want it to start automatically when the system starts up.

Hello Francis, Both commands are equivalent. systemctl automatically adds the .service suffix is not specified. Just pick one. Yen Chi Hsuan On 16 April 2015 at 11:35, Francis Gerund wrote:

Okay, so do I do

1) sudo systemctl enable ufw

or,

2) sudo systemctl enable ufw.service

or, both?

On Wed, Apr 15, 2015 at 9:50 PM, Chi Hsuan Yen wrote:

...

Hello Francis,

Just simply run the following command as root or with sudo:

systemctl enable ufw.service

Yen Chi Hsuan

On 16 April 2015 at 10:39, Francis Gerund wrote:

...

Hello!

How do I get ufw to start automatically upon Arch system startup?

The Arch wiki Uncomplicated Firewall pages says: "Start ufw as systemd service to have it running and enable it to make it available after boot. "

How do I do that?

Then it shows an example configuration (can't I just keep the default: deny all incoming, allow all outgoing)?

Then it says: "The next line is only needed *once* the first time you install the package:

# ufw enable"

That does not seem to be true - I have to do "sudo ufw enable" every time I restart the system.

Then, it says: "Then enable the ufw service with systemctl."

How?

Bottom line: ufw works okay, I just want it to start automatically when the system starts up.

Okay, that seems to work. Thank you! Strange that the ufw install routine didn't do that automatically. And yes, I do read the wiki articles, whenever I have the time, patience and intelligence to do so. Which isn't easy after a very long, difficult day of learning to install and set up Arch. But I did want to get a firewall up and running, quicky. There are lots of bad guys out there these days. Thanks again. On Wed, Apr 15, 2015 at 10:49 PM, Sebastian M. wrote:

It does the same. Please read the wiki.

Regards, Sebastian M. On Wed, Apr 15, 2015 at 10:35:42PM -0500, Francis Gerund wrote:

...

Okay, so do I do

1) sudo systemctl enable ufw

or,

2) sudo systemctl enable ufw.service

or, both?

On Wed, Apr 15, 2015 at 9:50 PM, Chi Hsuan Yen wrote:

...

Hello Francis,

Just simply run the following command as root or with sudo:

systemctl enable ufw.service

Yen Chi Hsuan

On 16 April 2015 at 10:39, Francis Gerund wrote:

...

Hello!

How do I get ufw to start automatically upon Arch system startup?

The Arch wiki Uncomplicated Firewall pages says: "Start ufw as systemd service to have it running and enable it to make it available after boot. "

How do I do that?

Then it shows an example configuration (can't I just keep the default: deny all incoming, allow all outgoing)?

Then it says: "The next line is only needed *once* the first time you install the package:

# ufw enable"

That does not seem to be true - I have to do "sudo ufw enable" every time I restart the system.

Then, it says: "Then enable the ufw service with systemctl."

How?

Bottom line: ufw works okay, I just want it to start automatically when the system starts up.

On Wed, Apr 15, 2015 at 10:35:42PM -0500, Francis Gerund wrote:

Okay, so do I do

1) sudo systemctl enable ufw

or,

2) sudo systemctl enable ufw.service

or, both?

On Wed, Apr 15, 2015 at 10:49 PM, Sebastian M. wrote:

...

It does the same. Please read the wiki.

...

On Wed, 15 Apr 2015 23:25:54 -0500, Francis Gerund wrote:

...

And yes, I do read the wiki articles, whenever I have the time, patience and intelligence to do so. Which isn't easy after a very long, difficult day of learning to install and set up Arch.

But I did want to get a firewall up and running, quicky. There are lots of bad guys out there these days.

Hi, a few seconds of trail and error would have answered this question quick as lightning ;), but to mention this isn't the reason for my reply. My concern is off-topic. Anyway, it fits to this thread. It became a fashion to drop interleaved reply style and bottom posting. Please, if you don't want to use interleaved reply style or bottom posting, then _don't_ quote text below your reply. TIA, Ralf

On Thu, 16 Apr 2015 12:48:14 +0200, Ralf Mardorf wrote:

On Wed, Apr 15, 2015 at 10:35:42PM -0500, Francis Gerund wrote:

...

Okay, so do I do

1) sudo systemctl enable ufw

or,

2) sudo systemctl enable ufw.service

or, both?

...

On Wed, Apr 15, 2015 at 10:49 PM, Sebastian M. wrote:

...

It does the same. Please read the wiki.

...

...

On Wed, 15 Apr 2015 23:25:54 -0500, Francis Gerund wrote:

...

And yes, I do read the wiki articles, whenever I have the time, patience and intelligence to do so. Which isn't easy after a very long, difficult day of learning to install and set up Arch.

But I did want to get a firewall up and running, quicky. There are lots of bad guys out there these days.

Hi,

a few seconds of trail and error would have answered this question quick as lightning ;), but to mention this isn't the reason for my reply. My concern is off-topic. Anyway, it fits to this thread. It became a fashion to drop interleaved reply style and bottom posting. Please, if you don't want to use interleaved reply style or bottom posting, then _don't_ quote text below your reply.

TIA, Ralf

By accident I edited the top posting mail(s) with the quotation signs the wrong way up, but this easily happens when there is the need to edit wrong posting style replies :(.