(config) Issue with outbound load balancing

Sabbasth

I just updated to the last build.

The Status > Gateways > Groups table now displays correct datas ("Online").

The traffic is still only on GW1. GW2 and/or GW3 are not used.

edit : clarify the post.

jimp

We'll need a screenshot of your LAN firewall rules tab then, and the contents of /tmp/rules.debug would also help.

Sabbasth

I just removed GW1 from the pool, for test purposes.

flushing states table -> Still GW1 used.

I noticed that now (probably after the upgrade) all GWs are marked as "Default" on System > Routing.
I tried to uncheck the box, but all GW are still "Default" after applying the changes.
I tried to reboot the server, but nothing changed.

Summary :

My pool is composed of GW2 & GW3
All the connections are made on GW1
All GW are marked as default, and I can't remove this mark
All GW are up and detected as such in all tables.
The GW Group table displays correctly "online" state.

P.S. : I've seen your post, doing it now.

Sabbasth

Here are the files

![fw rules.PNG](/public/imported_attachments/1/fw rules.PNG)
![fw rules.PNG_thumb](/public/imported_attachments/1/fw rules.PNG_thumb)
tmp_rules.debug.txt

Sabbasth

Jimp, did you see something wrong ?
I think the configuration is very basic.

I you want me to reset all the config, feel free to ask.

eri--

Try without sticky-address or from 2 different hosts on LAN.

jimp

It does look fairly basic, aside from the fact that all three gateways are on the same interface. I'm not sure if that is causing an issue or not, but as ermal said, try it without sticky checked under advanced options, see if that makes a difference.

Sabbasth

Ok, I tried deactivating sticky-connections and the problem remains the same.

Does pfSense shouldn't manage multiple GWs from the same interface ?

jimp

It should work, in theory, but I'm not sure if anyone has thoroughly tested that scenario using them for WAN-type gateways.

Sabbasth

Hi,

I received hardware pieces to have 1 if per GW ant it works now.
No more erroneous information (like every GW displayed as default).

I think there's a bug with this scenario. :)

I let you tag this thread as resolved or not (I'm not sure if it should be set as resolved).