Project

General

Profile

Actions

Bug #651

closed

Multiple gateways on WAN interface

Added by Rino Santilli over 14 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
-
Start date:
06/12/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

In system routing I created two gateways on the WAN interface, and for both I added a monitor IP.
If the second gateway is not reachable via ping (since it is unplugged) the "status - gateways" tells that everything is ok and the gateways are both green.
If I connect to the console I can see the routing table is right (route for the first monitor ip via the correct gateway, route for the second monitor ip via the correct gateway and default route via the first gateway) but if I try to traceroute to the second monitor ip, even with the second gateway unplugged and not reachable via ping, it reaches the endpoint. How is it possible?

Thank you

r3N0oV4

Actions #1

Updated by Rino Santilli over 14 years ago

Another small indication: when I delete a gateway in the routing page or if I modify the monitor IP, the route to the monitor IP is not removed and the only way to do this is a reboot.

Thank you
r3N0oV4

Actions #2

Updated by Ermal Luçi about 14 years ago

Please test new snapshots.
This should be fixed from that time.

Actions #3

Updated by Ermal Luçi almost 14 years ago

The problem with this is that apinger will bind to the same address and has no idea that the monitoring host is down since pf(4) rule for outgoing can override the selection!
This might work with some manual tinckering.

Actions #4

Updated by Francesco R over 13 years ago

Ermal Luçi wrote:

The problem with this is that apinger will bind to the same address and has no idea that the monitoring host is down since pf(4) rule for outgoing can override the selection!
This might work with some manual tinckering.

Ermal, can you please explain the manual solution for this problem?
I have the same exact problem, and also other people in the forum reported this issue:
http://forum.pfsense.org/index.php/topic,33554.0.html

In 1.2.3, a similar config worked well for me, but now that i have upgraded to 2.0 i found this bug. I think that is a regression.
Thank you.

Actions #5

Updated by Josep Pujadas-Jubany over 13 years ago

Hello!

At the Spanish Forum there is an user with similar problem.

He posted images of its topology. So, its easy to see what is he doing. He has one WAN and two gateways.

And it seems that it doesn't work!

Regards,

Josep Pujadas

Actions #7

Updated by Chris Buechler about 12 years ago

  • Status changed from New to Closed

one WAN with multiple gateways isn't really supported. It can be made to work with floating rules to override the policy routing logic. It's a config problem, not a bug. It's easier and better to have one NIC per gateway.

Actions

Also available in: Atom PDF