Hello James, Wednesday, January 2, 2008, 8:22:04 PM, you wrote:
JC> Robert Milkowski writes: >> If I have two different networks - A and B, with two default >> routers, Solaris by default will round-robin between them, which >> is bad... JC> It's not clear to me why that's "bad," as it's exactly what you've JC> asked the system to do and what a reader of RFC 791 would expect, but JC> I'll take it as a given. >> Is there a tunable (ndd?) to tell a global zone to use default >> router for a given packet from a network a packet came in? JC> No, because in general there's just no relationship at all between a JC> packet coming in and one going out. If there *is* a relationship, JC> it's something that may be known only to the application involved. JC> Even when the stack knows about it the relationship -- as with TCP, JC> but not with UDP or ICMP -- it's merely temporal; if the system can JC> get better bandwidth or reliability by using an equivalent or better JC> route, it can and should do so. JC> It's just not that simple. Yeah, I know. I'm just trying to quickly solve the problem. Looks like the workaround with putting interfaces in a global zone into down state does the trick. Good that ip-instances for ce is coming... (I know it's in snv_80). -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ networking-discuss mailing list [email protected]
