Steve Glaus wrote:
Tim Pushor wrote:
Steve Glaus wrote:

Ok, I gotcha, trunk just looked like a ready mad solution for what I was trying to do... Could you tell me WHY it's not able to be used for that and what it is for? I've gone the pf route before to but it seems to add a lot of complexity to my ruleset

trunk(4) is mainly used to provide redundancy or performance enhancement on the same network. I was using it to provide switch redundancy by putting one cable in one switch, one in the other, and the switches connected together. If I lose a switch, it keeps chugging along.


Alright. Just so I understand.. COULD it be used to do what I'm trying to do? When you trunk two network interfaces together, are they adressless? Do the devices on the switch address the IP of the pseudo trunk interface?
I don't know. I suspect you'd have routing issues, at least. Yes, other devices address the IP of the trunk interface, and my real interfaces are address-less.

Reply via email to