John Brewer writes: > Dhcp client did work on and off there were several code changes and putbacks, > it had worked with Time Warners Cable modem, and DSL modem in between these > versions of snv_b55 to snv_b61 and one of the 10u4 beta's with a few other > caviate's > > http://www.opensolaris.org/jive/thread.jspa?messageID=66966\xF0\x90\x96\x96
That's a problem in the net-svc script (rather than the DHCP client itself). It refers to CR 6486630, which is a duplicate of 6355747, and which was fixed in snv_62 > and http://www.opensolaris.org/jive/thread.jspa?messageID=149926陲Ζ That's a general (and quite ancient) design problem with the system start-up scripts in OpenSolaris. The problem is that there's really no way to specify any policy rules for the actions taken by the networking start-up scripts. There's no way to say, as in the specific example in that thread, "I don't want the DNS server data from this DHCP server, but I do want the interface address and mask." The reason for this is that the original designer of those scripts (not me, and not now at Sun) believed that the DHCP server was always authoritative for all parameters it provides. In other words, if the DHCP server says "do X," then, by golly, you're going to do "X." As a mere client machine owner, you get no choice in the matter. That's somewhat understandable within a data center, where consistency is key. It's also fairly reasonable for desktops deployed within a single organization. It makes no sense at all in other contexts -- such as when talking to your ISP. In other words, it was all built for a very different design center from your situation, and it's not surprising that it doesn't meet your needs. It's not specifically "wrong," but merely horribly inflexible. The good news is that these sorts of policy rules for system configuration are *exactly* what the NWAM project is all about. I recommend that you check out what they're working on and make sure that they're addressing the scenarios that you have in mind. http://www.opensolaris.org/os/project/nwam/ (And, more to the point, I would argue strongly against a piecemeal approach to "fixing" this problem. There are known workarounds -- kludgy as they might be -- and any more substantive "fix" for the problem would almost certainly collide directly with the work that project is doing.) > Here are some bugid submitted: > > 6355747, 6460148 , 6486630 , 6508976 6295541 , 5105194 , 4867934 6355747 /lib/svc/method/net-svc makes a mess of hosts and ipnodes - Fixed in snv_62 6460148 dhcp client mangles /etc/hosts - Duplicate of 6355747 6486630 in dhcp client config, net-svc overwrites any manual changes in hosts/ipnodes - Duplicate of 6355747 6508976 Network Settings panel does not yield a working network configuration - Fixed in vermillion_59 (I think that's build 59 ... no clue about GNOME things) 6295541 IPv6 entry is overwritten by DHCP after reboot - Still open and owned by Sebastien Roy, but looks like a possible duplicate of 6355747 to me. 5105194 network/initial and network/service should be broken up - Open and owned by Zhenhui Xie. I believe this is part of NWAM. 4867934 request to implement RFC 3396; long options for DHCP - Open and available for any interested party to work on, but very likely to be unrelated to any problem you're having. > Plus loghost does not get inserted into the hosts. Ancient issue. That's: 4351417 DHCP client does not config loghost It's mostly just an annoyance, as it's easy enough to configure loghost to be 127.0.0.1 manually -- or just ignore the issue because it has no effect. > Also this goes back as far as 4773326 and even 2060734 in different attempts > to address the issue and it efects sparc systems as well see 6641824 with > dhcpconfig on bugid 6633481 4773326 PSARC 2003/325 Set hostname locally when not provided by dhcp server - Fixed in s10_53 (prior to Solaris 10 FCS!) 2060734 is not a valid CR number. It's actually an internal bugster subCR identifier for the S9u7 backport of the fix for CR 4773326. 6641824 DHCP netinstalls broken on SPARC - Fixed in snv_81. This wasn't really a DHCP problem. It was a part of the kernel's support for DHCP booting on SPARC that got broken by CR 6521412 ("new boot sparc") in snv_80, and subsequently fixed. I would be surprised if this is an issue here other than that it seems to have the same "DHCP" letters in it somewhere. 6633481 dhcpconfig(1M) crashes when configuring a DHCP server, no DNS configured and J2SE 1.4.2_12 is used - Looking through the evaluation of this CR, it seems to be a libresolv2 problem in Solaris 9 only. I don't know why it's not marked "no-s10+", but I think it should be, and I'll contact the RE. In any event, I very much doubt you've ever seen it. > I can only this can be reviewed and hope a solution can be found! You seem to say this as though we're sleeping. :-/ Of the "problems" you've cited, almost all are already fixed, some are not ones you could have seen, and the few that are open aren't implicated in any problems that the original poster cited. In other words, I don't think things really are as bad as you seem to be saying. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> 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
_______________________________________________ opensolaris-discuss mailing list [email protected]
