Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • B Bacula Community
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 95
    • Issues 95
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Bacula Community Edition
  • Bacula Community
  • Issues
  • #2667
Closed
Open
Issue created Jan 05, 2023 by Frank Eyermann@eyermannf

Windows Client IPv6 connection issue

Summary

Reproducibility Platform OS OS Version Product Version
always AMD64 Windows Server 2016/2019/2022 11.0.6, 13.0.1

Description

Windows Client does not correctly accept IPv6 connections.

Debug shows:

server05a-fd: lib/watchdog.c:82-0 Initialising NicB-hacked watchdog thread
server05a-fd: lib/watchdog.c:197-0 Registered watchdog 311c2c8, interval 30
server05a-fd: lib/mem_pool.c:617-0 max_size=512
server05a-fd: lib/events.c:48-0 Events: code=FD0001 daemon=server05a-fd ref=0x238e type=daemon source=*Daemon* text=Filed startup
server05a-fd: lib/message.c:1534-0 Enter Jmsg type=17
server05a-fd: lib/watchdog.c:254-0 NicB-reworked watchdog thread entered
server05a-fd: filed/filed.c:295-0 filed: listening on port 9102
server05a-fd: lib/bnet_server.c:90-0 Addresses 0.0.0.0:9102 [0.0.0.0]:9102 

(Startup successful, now I’m running stat client command on server)

server05a-fd: lib/bnet.c:490-0 Socket error: err=10014 Unknown error
server05a-fd: lib/bnet_server.c:191-0 Accept=-1 errno=603979776
server05a-fd: lib/bnet.c:490-0 Socket error: err=10014 Unknown error
server05a-fd: lib/bnet_server.c:191-0 Accept=-1 errno=603979776
server05a-fd: lib/bnet.c:490-0 Socket error: err=10014 Unknown error
server05a-fd: lib/bnet_server.c:191-0 Accept=-1 errno=603979776

(last two lines repeat until client is terminated)

Please note, debug shows server05a-fd: lib/bnet_server.c:90-0 Addresses 0.0.0.0:9102 [0.0.0.0]:9102 even client listens on IPv6 address. On Linux this line contains "Addresses [::]:9102", which seams correct.

I've tested Windows Server 2016, 2019, and 2022, using 11.0.6. and 13.0.1 binaries from bacula.org web site. Server is Ubuntu Jammy running Bacula-dir and -sd, version 11.0.6.

Steps to Reproduce

  1. Set up IPv6 on Client and Server
  2. Have Director connect to Client using IPv6
  3. Issue stat client on Director

Additional Information

config files:

# cat /opt/bacula/etc/bacula-fd.conf
FileDaemon {
  Name = server05a-fd
  FDAddresses = {
    ipv6 = { addr = ::; port = 9102; }
  }                # where we listen for the director
  WorkingDirectory = "C:\\Program Files\\Bacula\\working"
  Pid Directory = "C:\\Program Files\\Bacula\\working"
  Plugin Directory = "C:\\Program Files\\Bacula\\plugins"
  Maximum Concurrent Jobs = 10
  Heartbeat Interval = 300
}
Edited Jan 05, 2023 by Frank Eyermann
Assignee
Assign to
Time tracking