pfSense

I have a working setup on 2.3 with this configuration (but with second WAN on OPT1): 2 PPPoE connections, same provider and gateway. Maybe a broken config or a problem with a specific nic/specific interface?

I also updated from 2.2.

PS: However I noticed that the second WAN connection is not that powerful than WAN1: both connections are 100MBit links, WAN1 is able to saturate 95MBit, WAN2 between 60-70. But I'm not sure why that is and if this is related.

that does work in general but sounds like there is some edge case there.

Alexander: could you get me into the system or a backup of your config? Email cmb at pfsense dot org

Because you said it should work I reinstalled the firewall with 2.3 and tested it again. The same Problem here. Because I couldn't restore my Backup File (I got an error in webgui), I installed 2.2.6 and restored my backup. The problem still exists. So i deleted the second pppoe connection and added it again. And now it works. I think adding pppoe lines in 2.3 is broken.

I tried this:

2.3 new install = second pppoe don't work
2.2.6 new install = second pppoe works
2.3 -> 2.2.6 = second pppoe don't work, it must be removed and added again
2.2.6 -> 2.3 second pppoe don't work

That is not a valid test. You cannot restore a 2.3 configuration to 2.2.x or any earlier version.

I have a test system here with two PPPoE lines, both added on 2.3, and both work, so it definitely can work. The question is why some work and why yours does not.

Check the differences in config.xml from a working case and non-working case for the interface itself and in the ppps section.

We have 3 setups with multi-wan and the terminating on the same AC. One we are even using ourselves with dual t-business DSL16000 lines (v4, same DEFGW).

All are set up for load-balacing and failover (via firewall rules). Works for me.

@Alexander Rehbein: Do you still need help with the setup? Open a forum thread in the english or german forums so we can help.

Sorry for my late answer.

I could solve the problem. It was an problem with the nanobsd version. I've got an lot of other errors. I could solve all problems with permament write modus of the cf card. With the new update this fix was also implemented as i could see.