Hello backup'ers
I've setup and running one of my bareos systems on a pure ipv6 network
(you need correct resolution, firewall rules etc)
mostly restricting FD,DIR,SD with configuration like this
DIRAddresses = {
ipv6 = { addr = :: ; port = 9101 }
# ipv4 = { addr = 0.0.0.0; port = 9101 }
}
everything is working well under Linux
but now I've to integrate a windows 8.1 64bits client.
I've applied the same trick for the sd and the bareos-fd.exe seems to start
correctly
netstat -tan under windows show the daemon listening only on ipv6
Connexion actives
Proto Adresse locale Adresse distante État État de
déchargement
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING InHost
TCP [::]:135 [::]:0 LISTENING InHost
TCP [::]:445 [::]:0 LISTENING InHost
TCP [::]:3389 [::]:0 LISTENING InHost
TCP [::]:9102 [::]:0 LISTENING InHost
but if I try to connect with the director or bareos-tray-monitor then I got
only
TCP [2001:41d0:2:f1de::55:aa44]:9102 [2001:41d0:2:f1de::ff:3c90]:33452
ESTABLISHED InHost
and bareos-fd start to use 50% (2 full cpu)
And no connections are made ...
look like a crash with ipv6
If I filter to use only ipv4 the daemon work just prooving the setup is right.
How is it possible to debug this nasty crap?
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member & Board, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
