On 8/20/07, James Carlson <[EMAIL PROTECTED]> wrote: > > I *wish* I could tell Solaris what its primary interface is. This is > > a common pain point when many physical and virtual interfaces exist > > and authorization (firewall, NFS, etc.) is performed > > by IP address. > > What would "primary" mean in this context? What would the system do > differently?
Primarily, I want the source address for NFS traffic to be predictable. To a lesser extent, I need this functionality for all traffic that doesn't specifically bind to a particular interface. For the NFS use case, the ideal situation would be the following to allow me to specify that different NFS mounts should originate from different source addresses. mount -F nfs -o srcaddr=192.168.23.45 server:/path /path However, since zones came about I have had much less need for this. > Perhaps the ifconfig "usesrc" option might get you closer to what you > want, but I don't think I understand what you're expecting from > designated primary interface or IP address. That is roughly what I would like to do, but all the examples that I see imply that you need to have a vni interface. My experimentation when using a vni interface suggests that those that wish to talk to the host have to have special routing table entries. Furthermore, usesrc is incompatible with IPMP. > I suspect that the NWAM project might be interested in your needs here. I haven't found (or looked too hard for) the details of the "enterprise" features of NWAM. I would love it to detect which VLANs are available on various physical links and provide a means for easily enabling the "best possible" service, presumably with a way to log+alert when "best possible" doesn't meet my definition of "good enough". Mike -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ networking-discuss mailing list [email protected]
