Gateways showing down after upgrade from 2.2 to 2.3 release

cmb

Can someone please outline the solution to this issue?

here:
https://forum.pfsense.org/index.php?topic=110043.0

sapelli

Hi,

I think I have the same bug here.
I have 2 gateways. One of those is ok. But the another, simply show "Disconnected"

If I ping throught the gateway "with problems" by de Status/Ping command, there are no problems.

Apr 18 18:02:48 dpinger UNFQ_DHCP 8.8.8.8: Alarm latency 0us stddev 0us loss 100%
Apr 18 18:02:40 dpinger send_interval 5000ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 8000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 192.168.2.100 identifier "UNFQ_DHCP "
Apr 18 18:02:40 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 5000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.1.2 identifier "BRT_DHCP "

what is wrog?

sapelli

same problem here.

One gateway is ok, the other one shows "disconnected":


Apr 18 18:02:48 	dpinger 		UNFQ_DHCP 8.8.8.8: Alarm latency 0us stddev 0us loss 100%
Apr 18 18:02:40 	dpinger 		send_interval 5000ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 8000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 192.168.2.100 identifier "UNFQ_DHCP "
Apr 18 18:02:40 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 5000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.1.2 identifier "BRT_DHCP "

if I ping, everything is ok:


PING 8.8.8.8 (8.8.8.8) from 192.168.2.100: 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=11.371 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=11.322 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=11.649 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.322/11.447/11.649/0.144 ms

what is wrong??

cmb

@sapelli:

I think I have the same bug here.

not a bug (in our code), read here:
https://forum.pfsense.org/index.php?topic=110043.0

@sapelli:

what is wrong??

read here:
https://forum.pfsense.org/index.php?topic=110043.0

Modesty

I have exacly same issue. Tried a lot but still no internet. Are there any solution for this?

dennypage

@Modesty:

I have exacly same issue. Tried a lot but still no internet. Are there any solution for this?

You probably want to start a new thread with a complete description of the problem you are experiencing. This thread referred to a (long resolved) issue with migrating monitoring parameters from apinger to dpinger which affected monitoring only.