[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-users
Subject:    Re: [Bacula-users] Bacula 11.0.6 Windows Client IPv6 no starttls
From:       "Eyermann, Frank" <frank.eyermann () munich-business-school ! de>
Date:       2023-01-04 22:06:41
Message-ID: AM0PR03MB4065A63F71B72C10A02AEA2F8AF59 () AM0PR03MB4065 ! eurprd03 ! prod ! outlook ! com
[Download RAW message or body]

Hello all,

this would support my observation with

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

even 0.0.0.0 is not an IPv6 address.

Just installed newest binary from bacula org web site (Version 13.0.1). Absolutly same behaviour.

I will file a bug report.

Many thanks Radoslav and Martin.

Best regards,

Frank


-----Ursprüngliche Nachricht-----
Von: Martin Simmons <martin@lispworks.com> 
Gesendet: Dienstag, 3. Januar 2023 16:20
An: Radosław Korzeniewski <radoslaw@korzeniewski.net>
Cc: Eyermann, Frank <frank.eyermann@munich-business-school.de>; bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Bacula 11.0.6 Windows Client IPv6 no starttls

Error 10014 from accept is:

WSAEFAULT    The addrlen parameter is too small or addr is not a valid part of
             the user address space.

I think that can only be caused by a bug in the Bacula client (or it is not compiled correctly for IPv6).

__Martin


>>>>> On Mon, 2 Jan 2023 15:04:36 +0100, Radosław Korzeniewski said:
> 
> Thanks!
> 
> In this case as all components are on the same version it is not a 
> version inconsistency issue.
> To be honest, I have no clue why a Bacula windows client is unable to 
> receive any data on the socket, which is a main reason you can't 
> communicate with it.
> I had no issues like this in the past. You need to somehow (I don't 
> know
> how) debug why Bacula cannot read (receive) from a socket which should 
> work. Any firewall in the network path? Any antivirus software 
> disrupting communication? dunno.
> Maybe other users can help more. Good luck!
> 
> R.
> 
> pon., 2 sty 2023 o 14:13 Eyermann, Frank < 
> frank.eyermann@munich-business-school.de> napisał(a):
> 
> > Hello Radoslaw,
> >
> >
> >
> > 11.0.6 windows binary from bacula org web site.
> >
> >
> >
> > Best regards,
> >
> >
> >
> > Frank
> >
> >
> >
> >
> >
> > *Von:* Radosław Korzeniewski <radoslaw@korzeniewski.net>
> > *Gesendet:* Montag, 2. Januar 2023 11:34
> > *An:* Eyermann, Frank <frank.eyermann@munich-business-school.de>
> > *Cc:* bacula-users@lists.sourceforge.net
> > *Betreff:* Re: [Bacula-users] Bacula 11.0.6 Windows Client IPv6 no 
> > starttls
> >
> >
> >
> > Hi,
> >
> >
> >
> > sob., 31 gru 2022 o 01:30 Eyermann, Frank < 
> > frank.eyermann@munich-business-school.de> napisał(a):
> >
> > Hello Radoslaw,
> >
> >
> >
> > thank you for pointing me at the debug option.
> >
> >
> >
> > Running the director reveals not much interessing (I've tried stat 
> > client
> > command)
> >
> >
> >
> > backupsrv01-dir: ua_status.c:274-0 status:stat client:
> >
> > backupsrv01-dir: watchdog.c:196-0 Registered watchdog 7f12f001e138, 
> > interval 15 one shot
> >
> > backupsrv01-dir: btimers.c:145-0 Start thread timer 7f12f001e378 tid
> > 7f12fbfff640 for 15 secs.
> >
> > backupsrv01-dir: bsockcore.c:354-0 Current
> > [2001:hidden:hidden:101::2]:9102 All 
> > [2001:hidden:hidden:101::2]:9102
> >
> > backupsrv01-dir: bsockcore.c:285-0 who=Client: server05a-fd
> > host=2001:hidden:hidden:101::2 port=9102
> >
> > backupsrv01-dir: bsockcore.c:472-0 OK connected to server  Client:
> > server05a-fd 2001:hidden:hidden:101::2:9102.
> > socket=2001:hidden:hidden:101::10.60862:2001:hidden:hidden:101::2.91
> > 02
> > s=0x7f12f001e688
> >
> >
> >
> >
> >
> > But FileDaemon shows errors:
> >
> > 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: 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
> >
> > 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
> >
> > (And those both lines repeat thousands of times within a few 
> > seconds.)
> >
> >
> >
> >
> >
> > What version is your client?
> >
> >
> >
> > R.
> >
> >
> >
> > Best regarda,
> >
> >
> >
> > Frank
> >
> >
> >
> >
> >
> > *Von:* Radosław Korzeniewski <radoslaw@korzeniewski.net>
> > *Gesendet:* Donnerstag, 29. Dezember 2022 23:19
> > *An:* Eyermann, Frank <frank.eyermann@munich-business-school.de>
> > *Cc:* bacula-users@lists.sourceforge.net
> > *Betreff:* Re: [Bacula-users] Bacula 11.0.6 Windows Client IPv6 no 
> > starttls
> >
> >
> >
> > Hello,
> >
> >
> >
> > czw., 29 gru 2022 o 15:15 Eyermann, Frank < 
> > frank.eyermann@munich-business-school.de> napisał(a):
> >
> > Hello all,
> >
> >
> >
> > In our network I've enabled IPv6 in dual-stack configuration.
> >
> >
> >
> > Bacula-dir and Bacula-SD version 11.0.6, on Ubuntu 22.04
> >
> >
> >
> > With Linux Clients everything works fine.
> >
> >
> >
> > For Windows Clients (tested with 2016, 2019 and 2022 servers):
> >
> > If I state Address in Client resource of Director as an IPv4 
> > address, everything works fine.
> >
> > If I state Address in Client resource of Director as an IPv6 address 
> > (or DNS name), communication with Client is stuck:
> >
> >    - Director establishes TCP connection to client (3-way TCP Handshake)
> >    - Director sends a Hello packet
> >    - Client does _*not*_ respond with „starttls" but simply TCP
> >    acknowledges previous packet.
> >
> >
> >
> > At this point the communication is stuck. Director waits forever, 
> > Client waits forever.
> >
> >
> >
> > To debug what is going on, just execute both dir and client with '-d500'
> > (or higher) and examine output to find on what procedure it stuck on 
> > both programs.
> >
> >
> >
> > I hope this helps.
> >
> > --
> >
> > Radosław Korzeniewski
> > radoslaw@korzeniewski.net
> >
> > _______________________________________________
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> >
> >
> >
> >
> > --
> >
> > Radosław Korzeniewski
> > radoslaw@korzeniewski.net
> >
> 
> 
> --
> Radosław Korzeniewski
> radoslaw@korzeniewski.net
> 

_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[prev in list] [next in list] [prev in thread] [next in thread]