Alex Johnson warns against starting in.routed which will forward packets
between the two ethernet cards in the Solaris box. This has the effect of
routing the secondary ethernet traffic onto the nodebus. I think you can
see why that's a bad thing. That's why Foxboro comments the in.routed
lines out of a normal Solaris boot sequence.
However, if you use the -q (quiet) option when you start in.routed the
routing tables are maintained for both ethernet cards, but no routing
occurs between the cards. This is part of setting up a firewall in
Solaris. I have successfully used this method for some time. I believe
Foxboro's concern is the difference between in.routed and in.routed -q is
quite extreme for one little argument. For safety's sake it is probably
better to maintain the routing tables by hand. Discretion being the better
part of valor and all that.
I would recommend anyone interested in learning more about this check out
http://docs.sun.com and see what they have to say about setting up your
TCP/IP network. The Solaris 2.6 System Administrator Collection Vol 1 does
a much better job of explaining the options available to you than the man
pages that get included with the systems.
Regards,
David Johnson
Premier System Integrators
(256) 355-1732
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
