Jim Klimov writes: > We had a problem with jumpstart/NFS setup; perhaps similar to yours? > > It was related to non-standard net masks (i.e. 192.168.0.0/255.255.252.0 is > not class-C). While DHCP provided the correct options and parts of the > installer loaded ok, then it reset the networking settings to "correct" ones > per network's class (snoop showed that broadcasts went to 192.168.1.255 > instead of 192.168.3.255, etc).
Those aren't "non-standard." They're very much standard netmasks following CIDR (RFC 4632) rules. Anything that requires the use of the old (and obsolete) classful netmasks is _broken_, and has been for a good 15 years or so. > While this problem was googled as valid for old releases, we were surprised > to trigger in Solaris 10u4 (8/07). > > A working solution was to separate the setup/mgmt network to a correctly > classed one (i.e. 192.168.16.0/24) on a separate interface (with individual > MAC address for DHCP/TFTP purposes). This shouldn't be necessary. Please do file a bug, and make sure you document your configuration clearly in the bug report. (My guess is that you're a victim of CR 4769904 -- "bootparamd thinks it's a routing protocol.") -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
