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 …

I'm not sure I understand you fully, but this is what I think you mean: You have a single layer 2 network, basically a bunch of servers (and possibly other hosts) connected to a switch or series of switches that are not split into vlans. On this L2 network you have configured multiple subnets, so for example you have a server whose address is 192.168.1.100/24 and another that is 172.16.0.200. Now you want to change things, such that each server actually sits on a separate vlan and can reach the other hosts only through pfsense. Am I close? Can you provide a diagram of how things are and how you want them to be? You can do this for free on gliffy.com.

Do you have firewall rules configured on the router?  pfSense creates a new section in the rules for the new VLAN interfaces, whatever you named them.  By default I think its opt1, opt2, etc.  You may need to create a rule to allow traffic from the VLAN's subnet outbound.  I'm pretty sure there are no rules and an implicit deny when you create a new interface.  This would result in you being able to ping the switch from pfSense, but not the other way around.

@abitdisgruntled: We would normally accomplish this via Policy-Based Routing and IP SLA How exactly would you do this? @abitdisgruntled: Sorry, I should have stressed more the reason why I need to route by hostname and not IP. As I mentioned 1 of the database providers uses Amazon Cloud services and as such the destination hostname's IP address changes frequently (often 4-5 times a week) and drastically (such that specifying a route based on destination range or network will also not work). It can be done with pfsense as jimp explained. Since the hostname you need to resolve changes IPs relatively infrequently ("4-5 times a week") then you can simply use an alias, as previously suggested. pfsense includes a daemon that periodically resolves any fqdn in aliases into IP(s). But it wouldn't work if the fqdn resolved to a different IP every time you did a DNS query (e.g. www.facebook.com). For those cases I've considered doing policy routing for the entire IP range and suggested a related feature to the devs here.

You may want to look at the HOWTO, as the way to set up load-balancing has changed somewhat since 1.x. http://doc.pfsense.org/index.php/Multi-WAN_2.0

That was fast! Thanks a Lot  ;D

Set your IPs as "IP alias" Type

You can do that with IP aliases, but it's going to be a big headache and a giant security problem. Reconsider the vlan switch idea, which is the proper way to do this and still sleep at night. You can get a decent 5-port vlan switch for $50. http://www.ncix.com/products/?sku=57524&vpn=GS105E-100NAS&manufacture=Netgear

I figured out what was wrong with my RV016, the MTU size was 1500 when it should have been 1492 for ADSL. http://www.cisco.com/en/US/products/ps9924/index.html This router allows you to load balance without putting a router in front of it.