Thank you for the recommendations. I appreciate it. > Your LAN does *not* have to be in the same network segment as your ISP > gateway.
Agreed. The problem is the conflict that occurs naturally when connecting any two ISPs. > If your ISP changes the configuration of the gateway it provides, or > you change ISP or whatever, just use autoconf on em0, and let it be > configured to whatever your ISP sees fit. If I put em0 and em1 on DHCP, and connect each to their own gateway/router, they will get their respective configuration, but this does not solve the problem. Consider the case where both ISPs use 192.168.1.1/24: em0 and em1 will get two configurations for apparently the same network, causing a conflict. What's needed is an abstraction layer, a configuration where a group of interfaces is declared egress and adjusts itself accordingly. I have in mind something like a bridge: ``` > cat /etc/hostname.bridge0 add em0 add em1 add em2 add vether0 up ``` The "egress bridge" would mask whatever sits behind it, taking care of the routing tables, prioritizing on the fastest network, and serving it all to the LAN as the LAN's official gateway, using a single address that is independent from the specific gateways. It is evident that one such machinery does not exist, but it would be useful and it would save time.
