Discussion:
Monitor IP in gateway, strange behavior
Diego Barrios
2011-08-17 21:45:43 UTC
Permalink
Hi folks,

I`m not sure if this could be a bug, but i`ve just installed a new PFSense 2.0RC3 (latest snapshop) with 3 NICs, 1 LAN + 2 WAN



When i use the same "monitor IP" on both WANs, one of them stay "gathering statistic" forever in the gateway widget, on the dashboard.


If i use different IPs, everything works fine, with the latency time and packet loss for each one.


I`ve tried different IPs on each WAN (i don`t want to use the gateway`s IP of each one because for me it`s more important to compare the latency time to same destination trough different WANs) with always the same behavior


It`s not a serious problem for me, but maybe if it`s really a bug, you can fix in final release.


Have you guys already seen this issue before?


Thanks in advance.


Diego Barrios.
Chris Buechler
2011-08-17 21:42:12 UTC
Permalink
Post by Diego Barrios
Hi folks,
I`m not sure if this could be a bug, but i`ve just installed a new PFSense
2.0RC3 (latest snapshop) with 3 NICs, 1 LAN + 2 WAN
When i use the same "monitor IP" on both WANs
You can't do that. The GUI prevents configuring that and it works
correctly as far as I've seen, the GUI let you configure that?

---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscribe-***@public.gmane.org
For additional commands, e-mail: support-help-***@public.gmane.org

Commercial support available - https://portal.pfsense.org
Diego Barrios
2011-08-17 22:01:46 UTC
Permalink
I`m sorry, maybe i wasn`t clear... when i said "2 WAN" i mean "1 WAN and 1 OPT1"




LAN = Switch internal network WAN = ADSL


OPT1 = CABLE MODEM


Everything is working fine, with load balance between the links, redundancy etc... the issue is only with the IP to test if the gateway is up or not


(System/Routing/Gateway/Edit/Monitor IP)


[]`s


Diego

----- Original Message -----
From: "Chris Buechler" <cbuechler-***@public.gmane.org>
To: support-***@public.gmane.org
Sent: Wednesday, August 17, 2011 5:42:12 PM
Subject: Re: [pfSense Support] Monitor IP in gateway, strange behavior
Post by Diego Barrios
Hi folks,
I`m not sure if this could be a bug, but i`ve just installed a new PFSense
2.0RC3 (latest snapshop) with 3 NICs, 1 LAN + 2 WAN
When i use the same "monitor IP" on both WANs
You can't do that. The GUI prevents configuring that and it works
correctly as far as I've seen, the GUI let you configure that?

---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscribe-***@public.gmane.org
For additional commands, e-mail: support-help-***@public.gmane.org

Commercial support available - https://portal.pfsense.org
Tim Dickson
2011-08-17 23:10:01 UTC
Permalink
Post by Diego Barrios
Everything is working fine, with load balance between the links, redundancy etc... the issue is only with the IP to test if the gateway is up or not
You have to have a SEPARATE IP for each monitor address...
If you are going out through the same gateway, than traceroute out on the net somewhere and see if you can ping some local routers along the way.
Put their IP in as a monitor address.
Diego Barrios
2011-08-18 01:18:19 UTC
Permalink
Thanks Tim, that`s exactly what i did. Took different IPs to monitor in the same remote net (same latency time)





Diego

----- Original Message -----
From: "Tim Dickson" <TDickson-nqPVx6S/***@public.gmane.org>
To: support-***@public.gmane.org
Sent: Wednesday, August 17, 2011 7:10:01 PM
Subject: RE: [pfSense Support] Monitor IP in gateway, strange behavior
Post by Diego Barrios
Everything is working fine, with load balance between the links, redundancy etc... the issue is only with the IP to test if the gateway is up or not
You have to have a SEPARATE IP for each monitor address...
If you are going out through the same gateway, than traceroute out on the net somewhere and see if you can ping some local routers along the way.
Put their IP in as a monitor address. Pick one with as few hops as you can find.
Loading...