Project

General

Profile

Actions
Copy link

Bug #10800

closed

Multi WAN Load Balancing does not work on 2.5.0.a.20200729.0650

Added by Dmitry Fill over 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Multi-WAN
Target version:
-
Start date:
07/30/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.x
Affected Architecture:
amd64

Description

Version: 2.5.0.a.20200729.0650

Tried to follow documentation to setup multi WAN with Load Balancing

1. Two WAN Connections created with static IPv4 assigned by providers
2. Gateway Group is created with both WAN connections set to Tier1
3. In System / Routing / Gateways - added Monitor IP for each gateway
4. In System / General Setup - Added public DNS for each Gateway (1.1.1.1 for one & 9.9.9.9 for second)
5. In Firewall / Rules / LAN - Edited default rule for IPv4 protocol setting Gateway to Gateway Group created at step #2.
--
Both WAN connections are online

Tried to do
`curl http://icanhazip.com` - does not matter how many times run, still connection goes over WAN1 and I get a public IP of WAN1.
Tried to
- start multiple 4K/8K Youtube streams, on client machine on LAN, seems all still go through WAN1

Actions
Copy link
 #1

Updated by Jim Pingle over 3 years ago

  • Category set to Multi-WAN
  • Status changed from New to Rejected
  • Target version deleted (2.5.0)

There is not enough information here to rule out a configuration issue or a problem with your test methodology. This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions
Copy link
 #2

Updated by Dmitry Fill over 3 years ago

Thank you Jim. I got redirected here after clicking link "Give Feedback" on documentation section of "Multiple WAN Connections". Will use forum to describe the problem and see advice.

Actions
Copy link
 #3

Updated by Adam Goldberg over 3 years ago

Dmitry Fill wrote:

Version: 2.5.0.a.20200729.0650

Tried to follow documentation to setup multi WAN with Load Balancing

1. Two WAN Connections created with static IPv4 assigned by providers
2. Gateway Group is created with both WAN connections set to Tier1
3. In System / Routing / Gateways - added Monitor IP for each gateway
4. In System / General Setup - Added public DNS for each Gateway (1.1.1.1 for one & 9.9.9.9 for second)
5. In Firewall / Rules / LAN - Edited default rule for IPv4 protocol setting Gateway to Gateway Group created at step #2.
--
Both WAN connections are online

Tried to do
`curl http://icanhazip.com` - does not matter how many times run, still connection goes over WAN1 and I get a public IP of WAN1.
Tried to
- start multiple 4K/8K Youtube streams, on client machine on LAN, seems all still go through WAN1

I am experiencing the same issue. When I revert to 2.4.5p1 with the same configuration the issue resolves. Gateways with equal weights in a gateway group default to the first gateway added.

Actions
Copy link
 #4

Updated by Layla Mah almost 3 years ago

I am also experiencing the same issue. Failover works, but load balancing does not work -- all packets go through the first interface in the interface group unless the first interface is down.

It seems several other people have also reported this bug on the forums:
https://forum.netgate.com/topic/155694/multi-wan-load-balancing-does-not-work-on-2-5-0/2

I think it's very fair to assume Netgate introduced a regression in 2.5.0, and Adam Goldberg clearly gave context about his repro steps and test methodology.

NOTE: I have "Sticky Connections" disabled.

Actions
Copy link

Also available in: Atom PDF