> > > Hmm That'll need testing with several Sun unbundled products. > > > Solstice X.25 for example. > > > > Right. I've been following this thread passively, but my feeling is > > that there is nothing good that can possibly come of fixing this "bug". > > First, I don't view this as a bug, but a really poorly designed feature. > > Second, the impact of accidentally running into this poorly designed > > feature is minimal, while fixing it is highly risky. Do we know what > > other kinds of datalinks masquerade as DL_ETHER but depend the setting > > of the destination IP address to set IFF_POINTOPOINT? I certainly > > don't, and I don't see the value of discovering them through deliberate > > breakage. > > I think that's a pretty reasonable alternative. I still think fixing > the bug would be nice to do, but "not worth the bother and risk" is a > valid answer.
I'm unclear how what Seb's proposed is an "alternative" -- it seems like he's proposing doing nothing. Did I misunderstand? Regarding Seb's comment that "nothing good can possibly come from fixing this", as I understand the original issue, it was that a fairly simple user error can leave a twisted wreckage behind that has to be hauled away via unplumb. To that end, do we know if anyone actually depends on ifconfig working in this manner, or only the behavior of the ioctls that ifconfig uses working in this manner? If it's the latter, then we could tighten the ifconfig screws just to eliminate the usability issue. (Then again, there are so many usability issues with ifconfig -- hence the tentative plan for ipadm.) -- meem _______________________________________________ networking-discuss mailing list [email protected]
