[OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

Joshua M. Clulow josh at sysmgr.org
Wed Apr 13 20:47:47 UTC 2022


On Wed, 13 Apr 2022 at 12:43, Toomas Soome via openindiana-discuss
<openindiana-discuss at openindiana.org> wrote:
> > On 13. Apr 2022, at 22:32, stes at PANDORA.BE <stes at telenet.be> wrote:
> > ----- Op 13 apr 2022 om 21:13 schreef Judah Richardson judahrichardson at gmail.com:
> >> Speaking as an experimental user (read: OI is not my daily driver) who
> >> acknowledges OI inherits a lot of internal functionality from a
> >> server/workstation distro (openSolaris): all of this strikes me as
> >> anachronistically(?) complicated for something that should by default
> >> expect to get an IP address lease from any DHCP server on a network to
> >> which it's connected.
> > It's not really anachronistic.  It's just that there is an enormous amount of history behind the networking stack and OpenIndiana is the kind of operating system distribution where users appreciate "old conventions" for configuring the network.
> This is just bad excuse to have mess about how you configure your network.

I agree.  I think we have a bug with the routeadm thing, but otherwise
I think people are trying too hard to consider the history when
thinking about it.  Broadly, I would say:

    - If you don't care beyond "plug in a cable", use NWAM.
      That's what it's for.  We can and should fix any
      defects that prevent it working as effectively
      automatic in simple environments, which would
      include desktops and laptops and even single-
      homed servers with simple DHCP addresses.

    - If you want to be in more control, or to have
      things be more static, disable NWAM.  Use ipadm.
      You will know when this is you, because your
      needs will not be met by NWAM.

I wouldn't make it more complex than that.


Cheers.

-- 
Joshua M. Clulow
http://blog.sysmgr.org



More information about the openindiana-discuss mailing list