PFsense Remote NUT server to UPS connected to a Synology



  • Hi, i have UPS connected to my Synology NAS and the NAS is UPS server.
    I have some Windows client connected to the NAS and that is working fine,
    but from Pfsense, i only get this error :

    Status Alert: The UPS requires attention
    Failed to retrieve status

    I use the same string in pfsense and windows
    MONITOR ups@192.168.85.10 1 monuser secret slave

    If i try this : tcpdump -n port 3493 -A on pfsense i get this:
    Looks like it is some connections between pfsense NAS.

    Anybody have some ideas ?

    17:09:13.223803 IP 192.168.85.1.10711 > 192.168.85.10.3493: Flags [P.], seq 4029307802:4029307825, ack 1702028924, win 513, options [nop,nop,TS val 369103 ecr 159656366], length 23
    E..K..@.@..Q..U...U
    )....*[.er.|....+......
    .... .).GET VAR ups ups.status

    17:09:13.223954 IP 192.168.85.10.3493 > 192.168.85.1.10711: Flags [P.], seq 1:25, ack 23, win 114, options [nop,nop,TS val 159661412 ecr 369103], length 24
    E..L.Z@.@.....U
    ..U...).er.|.*[....r=d.....
    .=d....VAR ups ups.status "OL"

    17:09:13.223963 IP 192.168.85.1.10711 > 192.168.85.10.3493: Flags [.], ack 25, win 513, options [nop,nop,TS val 369103 ecr 159661412], length 0
    E..4..@.@..h..U...U
    )....[.er......+......
    .... .=d
    17:09:18.231289 IP 192.168.85.1.10711 > 192.168.85.10.3493: Flags [P.], seq 23:46, ack 25, win 513, options [nop,nop,TS val 374111 ecr 159661412], length 23
    E..K..@.@..Q..U...U
    )....
    [.er......+......
    ..._ .=dGET VAR ups ups.status

    17:09:18.231429 IP 192.168.85.10.3493 > 192.168.85.1.10711: Flags [P.], seq 25:49, ack 46, win 114, options [nop,nop,TS val 159666419 ecr 374111], length 24
    E..L.[@.@.....U
    ..U...).er...*[....r.......
    .P...._VAR ups ups.status "OL"

    17:09:18.231436 IP 192.168.85.1.10711 > 192.168.85.10.3493: Flags [.], ack 49, win 513, options [nop,nop,TS val 374111 ecr 159666419], length 0
    E..4..@.@..h..U...U
    )....*[.er......+......
    ..._ .P.
    17:09:19.986735 IP 192.168.85.1.38229 > 192.168.85.10.3493: Flags [S], seq 3720198728, win 65228, options [mss 1460,nop,wscale 7,sackOK,TS val 375865 ecr 0], length 0
    E..<..@.@....U...U .U.....H........+.............. ...9.... 17:09:19.986834 IP 192.168.85.10.3493 > 192.168.85.1.38229: Flags [S.], seq 3922156754, ack 3720198729, win 14480, options [mss 1460,sackOK,TS val 159668175 ecr 375865,nop,wscale 7], length 0 E..<..@.@....U
    ..U....U......I..8.D..........
    .W....9....
    17:09:19.986844 IP 192.168.85.1.38229 > 192.168.85.10.3493: Flags [.], ack 1, win 513, options [nop,nop,TS val 375865 ecr 159668175], length 0
    E..4..@.@..h..U...U
    .U.....I.......+......
    ...9 .W.
    17:09:19.986864 IP 192.168.85.1.38229 > 192.168.85.10.3493: Flags [P.], seq 1:14, ack 1, win 513, options [nop,nop,TS val 375865 ecr 159668175], length 13
    E..A..@.@..[..U...U
    .U.....I.......+......
    ...9 .W.LIST VAR ups



  • UPDATE:
    Looks like an update from synology did the trick. :-)


Log in to reply