ERROR: Sending broadcast failed! when server is connected to a VPN

Hello,

I’m running Urbackupserver 2.4.13 on debian 10 on a machine called S
and Urbackupclient 2.4.11.3 is running on manjaro on a machine called C.

Both machines are on the same LAN and can ping each other.

  • When my server S isn’t connected to an exterior VPN, it can
    broadcast and C can connect to it. Backups are made with no problem.

  • When my server IS connected to an exterior VPN - which has nothing to with urbackup, I just have to use a VPN for a specific task - it can’t broadcast and C can’t connect to it.
    As you guessed, no backup is made in that situation.

In both situation S and C can ping each other.

Just to be clear, I want urbackup to use the same interface in both situation, I don’t want it to use the VPN.

Is there something I can do ?


Here is what I already tried:

  1. disable ipv6 completelly on the server. It changed nothing.
  2. specify the interface on the server (I tried both eno1 and tun0, just in case). It doesn’t work.

Here are some logs:

I restarted the server many times as you can see

2022-02-06 08:47:14: ERROR: Sending broadcast failed!
2022-02-06 08:47:57: WARNING: Shutting down (Signal 15)
2022-02-06 08:51:11: WARNING: Shutting down (Signal 15)
2022-02-06 08:51:15: ERROR: Sending broadcast failed!
2022-02-06 08:52:05: ERROR: Sending broadcast failed!
2022-02-06 08:52:55: ERROR: Sending broadcast failed!
2022-02-06 08:53:45: ERROR: Sending broadcast failed! 

# here I disconnected the VPN

2022-02-06 08:54:03: WARNING: Shutting down (Signal 15)

No more ERROR:... since the client can now connects itself.

When S isn’t connected to vpn and a backup is running:

2022-02-06 09:12:23: FileSrv: Mapped name: /home/quentin/gdrive/dev/hugo/theme-book/.git/objects/f7
2022-02-06 09:12:23: FileSrv: Received a Packet.
2022-02-06 09:12:23: FileSrv: Sending file (normal) ...AEM3ZyD|gdrive/dev/hugo/theme-book/.git/objects/f8/5e7dae91f128a987f... metadata_id=15...

On S:

S $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 1c:98:ec:0f:52:d8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.26/24 brd 192.168.1.255 scope global dynamic eno1
       valid_lft 83658sec preferred_lft 83658sec
    inet6 2a01:cb0c:9d3:1300:1e98:.../64 scope global dynamic mngtmpaddr
       valid_lft 259197sec preferred_lft 259197sec
    inet6 fe80::1e98:ecff:fe0f:52d8/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1c:98:ec:0f:... brd ff:ff:ff:ff:ff:ff

On C:

C $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d8:bb:c1:04:.... brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.17/24 brd 192.168.1.255 scope global dynamic noprefixroute enp6s0
       valid_lft 83566sec preferred_lft 83566sec
    inet6 2a01:cb0c:9d3:1300:.../64 scope global dynamic noprefixroute
       valid_lft 259172sec preferred_lft 259172sec
    inet6 fe80::a098:1eb8:.../64 scope link noprefixroute
       valid_lft forever preferred_lft forever

When S is connected to a VPN and no connection can be established

S $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 1c:98:ec:0f:52:d8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.26/24 brd 192.168.1.255 scope global dynamic eno1
       valid_lft 83302sec preferred_lft 83302sec
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1c:98:... brd ff:ff:ff:ff:ff:ff
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/none
    inet X.X.X.X/24 scope global tun0
       valid_lft forever preferred_lft forever

Logs from the client C

C $ tail -f /var/log/urbackupclient.log
2022-02-06 09:27:47: ClientService cmd: #IJxfOIXRADZ4p#2PING RUNNING pc_done=100&status_id=1&speed_bpms=0&total_bytes=21010916800&done_bytes=20980860776&paused_fb=1#token=eBeBvP...
2022-02-06 09:27:57: ClientService cmd: #IJxfOIXRADZ4pXI#2PING RUNNING pc_done=100&status_id=1&speed_bpms=0&total_bytes=21010916800&done_bytes=20980860776&paused_fb=1#token=eBeBvP...

Logs from the server S

S sudo tail -f /var/log/urbackup.log
2022-02-06 09:28:28: ERROR: Sending broadcast failed! (ipv6)
2022-02-06 09:29:18: ERROR: Sending broadcast failed!
2022-02-06 09:29:18: ERROR: Sending broadcast failed! (ipv6)
2022-02-06 09:29:18: ERROR: Sending broadcast failed! (ipv6)
2022-02-06 09:30:08: ERROR: Sending broadcast failed!

If the objective is just to get backups to run, then putting the client in internet mode would probably work.

I’ll try, thank you.