How do i enable IPV6 on Server an Clientside?

[Samuel Marischek]

Hello all,

We use here Bareos 17.2 with UCS. The most of the servers here are IPV6 only. So i find out that the ports on the server and client are not listen on ipv6. Where i can enable this?

And the same @the client. We use here Ubuntu 18.04.

Thanks a lot :)

[Jörg Steffens]

On 27.08.19 at 15:29 wrote Samuel Marischek:

Bareos daemons listen on IPv4 by default.
If you want it to listen on IPv6,
add following lines to your Bareos Director configuration
(/etc/bareos/bareos-dir.d/director/bareos-dir.conf):

Dir Addresses = {
ipv6 = {
addr = ::;
}
}

Do it accordingly in the Storage- and File-Daemon configurations.

Regards,
Jörg
--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

[Samuel Marischek]

Hello Jörg,

very thanks for your reply.

@the file /etc/bareos/bareos-dir.d/director/bareos-dir.conf this is working fine. But @the filedaemon on the client, the service will not start anymore after set the option . I edited the file "/etc/bareos/bareos-fd.d/director/bareos-dir.conf" on an Ubuntuclient. So it look like this.

Director {
  Name = bareos-dir
  Password = "XXXXXXXXXXXXX"
  Description = "Allow the configured Director to access this file daemon."

  Dir Addresses  = {
    ipv6 = {
        addr = ::;
    }
 }

}

But now the service did not start anymore.

Aug 27 18:25:53 ubuntudev bareos-fd[8437]: Config error: Keyword "DirAddresses" not permitted in this resource.
Aug 27 18:25:53 ubuntudev bareos-fd[8437]: Perhaps you left the trailing brace off of the previous resource.
Aug 27 18:25:53 ubuntudev bareos-fd[8437]:             : line 6, col 17 of file /etc/bareos/bareos-fd.d/directo
Aug 27 18:25:53 ubuntudev bareos-fd[8437]:   Dir Addresses  = {
Aug 27 18:25:53 ubuntudev systemd[1]: bareos-filedaemon.service: Control process exited, code=exited status=1
Aug 27 18:25:53 ubuntudev systemd[1]: bareos-filedaemon.service: Failed with result 'exit-code'.
Aug 27 18:25:53 ubuntudev systemd[1]: Failed to start Bareos File Daemon service.

So wrong place for it?

Am Dienstag, 27. August 2019 18:11:07 UTC+2 schrieb Jörg Steffens:

On 27.08.19 at 15:29 wrote Samuel Marischek:
> Hello all,
>
> We use here Bareos 17.2 with UCS. The most of the servers here are IPV6
> only. So i find out that the ports on the server and client are not
> listen on ipv6. Where i can enable this?
>
> And the same @the client. We use here Ubuntu 18.04.

Bareos daemons listen on IPv4 by default.
If you want it to listen on IPv6,
add following lines to your Bareos Director configuration
(/etc/bareos/bareos-dir.d/director/bareos-dir.conf):

  Dir Addresses  = {
    ipv6 = {
        addr = ::;
    }
  }

Do it accordingly in the Storage- and File-Daemon configurations.

Regards,
Jörg
--

 Jörg Steffens                   joerg....@bareos.com

[Samuel Marischek]

Ah, ok, i found the first one. Important is the identifier. Right for the Filedaemon on the clientside is:

FD Addresses  = {
    ipv6 = { addr = ::; }
  }

Next is the Storagedaemon. Hope i will find the right name of it.

[Samuel Marischek]

Ok, the storagedameon did not start:

Director {
  Name = bareos-dir
  Password = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXxx"
  Description = "Director, who is permitted to contact this storage daemon."

  SDAddresses  = {
    ipv6 = { addr = ::; }
  }
}

So i think SDAddresses ist no right.

[Jörg Steffens]

On 27.08.19 at 19:40 wrote Samuel Marischek:

> Ok, the storagedameon did not start:
>
> |
> Director{
>   Name=bareos-dir
>   Password="XXXXXXXXXXXXXXXXXXXXXXXXXXXXxx"

>   Description="Director, who is permitted to contact this storage daemon."

>
>   SDAddresses ={
>     ipv6 ={addr =::;}
>   }
> }
> |
>
> So i think SDAddresses ist no right.

You need to set it in the Storage Daemon own ressource at
/etc/bareos/bareos-sd.d/storage/bareos-sd.conf , see
https://docs.bareos.org/Configuration/StorageDaemon.html#storage-resource
--
Jörg Steffens joerg.s...@bareos.com

[Samuel Marischek]

Ah, so wrong file. So what have i done. Changed that files on the Serverside:

/etc/bareos/bareos-dir.d/director/bareos-dir.conf

/etc/bareos/bareos-sd.d/storage/bareos-sd.conf

/etc/bareos/bareos-fd.d/client/myself.conf




If check with lsof:




lsof -i :9101
COMMAND    PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bareos-di 1578 bareos    4u  IPv6  23628      0t0  TCP *:bacula-dir (LISTEN)


lsof -i :9102
bareos-fd 1438   root    3u  IPv6  11188      0t0  TCP *:bacula-fd (LISTEN)


lsof -i :9103
bareos-sd 9362 bareos    3u  IPv6  40641      0t0  TCP *:bacula-sd (LISTEN)





On the clientsite:

lsof -i :9103
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bareos-fd 891 root    5u  IPv6  26559      0t0  TCP ubuntudev.supertux.lan:41722->bareos.supertux.lan:bacula-sd (ESTABLISHED)

So should work right?

But if i start a backup, i got this errormessage:

bareos-sd JobId 43: Job Backup-ubuntudev.supertux.lan.2019-08-28_16.47.16_15 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
 Storage: "FileStorage" (/var/lib/bareos/storage)
 Pool: Incremental
 Media type: File

Am Mittwoch, 28. August 2019 16:19:17 UTC+2 schrieb Jörg Steffens:

On 27.08.19 at 19:40 wrote Samuel Marischek:
> Ok, the storagedameon did not start:
>
> |
> Director{
>   Name=bareos-dir
>   Password="XXXXXXXXXXXXXXXXXXXXXXXXXXXXxx"
>   Description="Director, who is permitted to contact this storage daemon."
>
>   SDAddresses ={
>     ipv6 ={addr =::;}
>   }
> }
> |
>
> So i think SDAddresses ist no right.

You need to set it in the Storage Daemon own ressource at
/etc/bareos/bareos-sd.d/storage/bareos-sd.conf , see
https://docs.bareos.org/Configuration/StorageDaemon.html#storage-resource
--

 Jörg Steffens                   joerg....@bareos.com