On Wed, Jun 20, 2012 at 4:50 PM, Jerome Alet <[email protected]> wrote:
> Hi there, > > While playing with gateways and monitoring alternative IP addresses, > I've noticed a problem. > > When you add an alternative IP address to monitor, a static route is > added between the gateway address and the address to monitor. > > But when you delete this alternative IP address, click on "save" and > then on "apply changes", the static route is not removed as can be seen > with netstat -nr. > > Once you know this it's OK, but when you don't know and try to monitor > the external IP addresses of two links to two different ISP, each one > monitoring the other one, this creates some funny routing problems even > when you disable this monitoring, and this renders the problem difficult > to understand, and then fix. > > Is this a bug or normal behavior ? > > TIA > > -- > Jérôme Alet - <[email protected]> - Direction du Système > d'Information > Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX > Tél : +687 290081 Fax : +687 254829 > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list > Hello, I don't think I would call this a bug. There is no built-in mechanism (AFAIK) to connect these elements of the configuration together. It is similar to the behavior of version 1.x that created firewall rules for Port Forwarding but did not remove them when the forward was removed. In 2.0, a connection was added between the forwarded port and the associated firewall rule. If you know PHP, and have time, maybe you can write a patch to connect the gateway monitor and the static route, and submit it. I opened an issue in the pfSense Redmine to track this: http://redmine.pfsense.com/issues/2513 Moshe -- Moshe Katz -- [email protected] -- +1(301)867-3732
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
