Messages

hello,

unfortunately it's not working....

any other idea ?

I dont remember...

hi

same setup for both. (and it worked before upgrade)
when I try to ping from the FW, it's ping without problem 8.8.8.8 (so it's ok for the interface)

one thing, when I put the local IP GW of the router (ISP Box) it's working ... but it's a stupid workaround because I ping the box ... not internet connectivity

a little diagram :
WAN1<>BOX1 (192.168.XX.1)<>FW(192.168.XX.254)
WAN2<>BOX2 (192.168.YY.1)<>FW(192.168.YY.254)

just 1 not working.
this is always the same one which is down.

hi

try to restart the 2 services (1 per WAN interface) in System: Diagnostics: Services

no effect :(

[-C{]

when I check in memory / process I can see, for the one which is not working :
/usr/local/bin/dpinger -f -S -r 0 -i COAXGW -B 192.168.xxx.254 -p /var/run/dpinger_COAXGW.pid -u /var/run/dpinger_COAXGW.sock -C{

and for the one which is ok :
/usr/local/bin/dpinger -f -S -r 0 -i FIBERGW -B 192.168.xxx.254 -p /var/run/dpinger_FIBERGW.pid -u /var/run/dpinger_FIBERGW.sock

perhaps a little workaround ?

Hi,

I move to the 19.1 version and I have a problem with the dpinger / multiwan

when I ping from my first WAN1 interface to 8.8.8.8 for example, no problem but when I put 8.8.8.8 in monitor IP for the WAN1 interface, dpinger say :
dpinger: COAXGW 8.8.8.8 : Alarm latency 0us stddev 0us loss 100%

somebody share the same problem ?
I tried to remove all gateway + group and recreate but it's not working

issue with dpinger ?

j'ai essayé, à priori pas vu de gros changement mais j'ai dpinger qui ne fonctionne pas :(