-------- Original Message -------- On 4/3/25 08:52, otto.cooper <otto.coo...@proton.me> wrote:
> -------- Original Message -------- > On 4/3/25 08:18, Janne Johansson <icepic...@gmail.com> wrote: > > > The default route is given by an ip, then the kernel looks up which > interface contains the network for which the box can reach this ip in a > single hop. If it can, the route is now shown to be over this interface, and > that interface joins the egress interface group. If it can't find such an > interface, the default route is not set and no interface joins the egress > group. > > In a production network, you cannot change the LAN to accommodate obsd. It > is obsd that must accommodate itself to the existing LAN. > > In other words, if I set the LAN to a different subnetwork, egress goes to > the right interface but I fucked up a whole company. On the other side of the > wire, the ISP has a fixed IP I cannot change. > > So, obsd's automatic assignment of egress fails hard. As it turns out, it > fails hard because in the PCI bus ix0 (LAN) sits before em0 (gateway), so > obsd attaches egress to ix0, and it does so despite explicit group assignment > and change of priority in hostname.if. > > To solve obsd's royal fuckup, I have to use ix0 as egress and ix1 as > ingress, and disable emN. Which means purchasing hardware, wasting a 10Gbps interface for a sub 1Gbps uplink, and feed a single LAN switch instead of two.
