Thanks for the reply. We have actually decided to abandon this. Myself and the admin of the 10.92.133.0 network are able to stay in reliable contact, however the admin(s) for the network between are difficult to get in touch with and we never talk to the same person twice and won't allow us access to their devices.
Basically we are going to bypass this altogether simply because we have narrowed the issue down to an issue in the routing in the "middle" network, and it's too risky to rely on them.

Thanks.

If your ISP has you on a 50/6 profile then why would you need multiple PPPoE sessions to achieve that? Are you able to confirm that your modem is sync'ed at that speed?

http://doc.pfsense.org/index.php/Multi-WAN_2.0

http://doc.pfsense.org/index.php/VLAN_Trunking

For your pfsense box, use only isp gateway unles you have other network to reach with some gateway at lan.

Thanks for making it clear… Will try find it out which ruling suite best.  ;)

Then the computer that are using the other gateway should have access through unless you have created some strange firewall rule in pfSense that is blocking the IP from ISP1 and 2. It should treat those as external IPs. CAn you screen shot your rules and your NAT for this?

Thank you for your feedback.

Perhaps I can change the GUI so that we can chose a specific or all interfaces.
But I am no expert in changing the GUI, too. hehe ;)

–--edit----

Ok, I did some changes on these files:
freeradius.inc
freeradiussettings.xml

So we have the possibility to enter one IP address of the listening interface or we can chose a " * " if we like that freeRADIUS is listening to any interface. I tried this on my machine for a short time and it is working.

Version 1.0.5 should have the changes.

Yes, please post back if it works, fails or if you have further questions :-)

@bonnecomm:

There are precisely 2 subnets in use and a pile of PPPoE errors in the logs.

What are the errors?

The next version may fix it, depending on what the errors are of course.  8)

@jimp:

If your two interfaces ever have the same gateway, it will fail, and you can't override a gateway for pppoe in that way.

You'll likely need to let one modem do NAT in that situation.

That said, you might find this post-2.0 commit interesting :-)
https://github.com/bsdperimeter/pfsense-tools/commit/7d06581fa8dd923c94f8e8cfce05dfabbac39a25

I'm now running very nicely on 6 ADSL modems.

The basic idea is create a rule to permit traffic between interfaces without any gateway.

Test this first and then create rules that forces a gateway.

You have a few options.
I think the easiest one would be to set up two servers on pfsense1 (one per isp, both with the same port, psk, compression…).
Setup one client on pfsense2.
You can have the client try to connect to a dyndns address that is assigned to the active wan connection on pfsense1.
-E

Replying to the own threads sucks but I got it solved. And since I hate those threads were nobody says how here is my explanation:

As you can see in the picture above I took /dev/cuaU2 because there was no other device. Well - this is exactly the problem because the modem has to report as /dev/cuaU0.
I played around with some bios-settings regarding USB (legacy devices, etc) and also with the USB-Ports I used and somehow after a reboot I finally could see /dev/cuaU0 in the wizard. Guess what - since then it worked …