[OmniOS-discuss] OmniOS stops acting as a DHCP client

[Michael Mounteney]

This is one of those instances where I'm going to leave out some
relevant fact but I'll try to put in all the factors.

TL;DR OmniOS permanently refuses to be a DHCP client.

My home server has two interfaces which show up as e1000g{0,1}.
e1000g0 is connected to the cable router provided by my ISP (Optus).

While I was away to-day, the server 'lost' the interface;  i.e.,
netstat -r did not show any ref. to e1000g0.  So I took it down and
brought it up again:

# ipadm delete-addr  e1000g0/v4
# ipadm delete-if e1000g0
# ipadm create-if e1000g0
# ipadm create-addr -T dhcp e1000g0/v4

Those last two commands were how I set up the interface on
post-installation configuration.  However, now that last command hangs
for a couple of minutes before dhcpagent reports a timeout.

The workaround is to assign an address statically:

# ipadm delete-addr  e1000g0/v4
# ipadm create-addr -T static -a 192.168.0.9 e1000g0/v4

This happened just the same with r151013 but I never got around to
investigating it.

A laptop, connected to the router, is able to obtain an address from
the router.

The paranoid in me wonders if Optus have loaded special firmware onto
their router which has decided that since I'm not running some version
of Mess Windows, for my own protection I won't be given an IP address.

I repeat:  r151014 has been getting its IP from the router's DHCP
server for about four weeks and has just stopped doing so
to-day, without intervention from me.

Any ideas?

______________
Michael Mounteney