On 4/11/22 07:49, Bob Friesenhahn wrote:
The above only applies to how the client gets its name. At one time I used a
Solaris DHCP server (and it was great) but I think that server has been
deprecated in Solaris and likely removed since then.
Yes, Solaris 11.4 only ships the ISC DHCP
On Mon, 11 Apr 2022, Judah Richardson wrote:
Perhaps I misunderstood the documentation, so here's the verbatim quote:
"By default, the Solaris DHCP client does not supply its own host name,
because the client expects the DHCP server to supply the host name. The
Solaris DHCP server is
On Mon, Apr 11, 2022 at 8:14 AM Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Sun, 10 Apr 2022, Judah Richardson wrote:
>
> > OK. The Solaris documentation I linked to says that Solaris (and
> presumably
> > distros downstream of that codebase) expects the DHCP server to be
>
In message <642ef4d2-e6d0-aa16-dabb-084f67e3f...@duedinghausen.eu>, Stephan
Althaus writes:
>To clarify the symptoms on my machine: It is only the routing entry that
>disappears, the IP address remains active. The lease should not be the
>problem, as the duration is 30 days or the like..
>
>The
On 4/11/22 15:14, Bob Friesenhahn wrote:
On Sun, 10 Apr 2022, Judah Richardson wrote:
OK. The Solaris documentation I linked to says that Solaris (and
presumably
distros downstream of that codebase) expects the DHCP server to be
another
Solaris machine, and so DHCP servers that don't behave
On 4/11/2022 9:14 AM, Bob Friesenhahn wrote:
On Sun, 10 Apr 2022, Judah Richardson wrote:
OK. The Solaris documentation I linked to says that Solaris (and
presumably
distros downstream of that codebase) expects the DHCP server to be
another
Solaris machine, and so DHCP servers that don't
On Sun, 10 Apr 2022, Judah Richardson wrote:
OK. The Solaris documentation I linked to says that Solaris (and presumably
distros downstream of that codebase) expects the DHCP server to be another
Solaris machine, and so DHCP servers that don't behave like the latter can
result in unexpected
On Sun, 10 Apr 2022, Stephan Althaus wrote:
I have those messages, too.
$ dmesg |grep "0.0.0.0"
Apr 10 14:40:33 dell6510 in.routed[1035]: [ID 749644 daemon.notice] e1000g4
has a bad address 0.0.0.0
Did you intend to run a RIP routing daemon?
Bob
--
Bob Friesenhahn
Hi Andreas,
thanks a lot!
After a pkg refresh --full I was able to install my new zone without further
issues.
Best regards.
Maurilio.
> Il 10/04/2022 14:29 Andreas Wacknitz ha scritto:
>
>
> Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:
> > Am 10.04.22 um 11:23 schrieb Stephan Althaus:
