Any reason you can't just use lagg(4) in one of the non-LACP modes? That's bascially designed to do exactly what you want.
On Tue, Feb 12, 2013 at 9:50 AM, Ivan Voras <ivo...@freebsd.org> wrote: > On 12/02/2013 18:38, Eggert, Lars wrote: > > > This sounds like your default route is going via igb2. > > Yes, it is. > > > You can make this work with ipfw rules (and I guess also setfib, > although I have not tried that.) > > The concept of FIBs looks clean and applicable but setfib works on newly > started process, and I would need to do something like apply it to > packets coming from an interface. > > I've found previous posts on "policy routing" with ipfw > ( > http://lists.freebsd.org/pipermail/freebsd-security/2004-April/001839.html > ) > but this is probably not what I need; I would need that packets > generated as a response to incoming packets go to the same interface as > the incoming packet. Or are you thinking of hard-coding client addresses > in ipfw rules so that packets going to specific IPs go to a specific > interface? > > > -- Freddie Cash fjwc...@gmail.com _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
