Klensin
Cc: Iljitsch van Beijnum; ietf@ietf.org; [EMAIL PROTECTED]
Subject: Re: DHCP failures (was RE: Do you want to have more
meetingsoutside US ?)
On Jul 31, 2007, at 6:30 PM, John C Klensin wrote:
And, while I'm picking on DHCP because I personally had more
problems with it, I see IPv6
Bob Hinden wrote:
It was also interesting to open the Mac network control pannel, enable
my Airport (WLAN) interface, and see the IPv6 global address appear
almost instantaneously and in many case having to wait many seconds to
minutes for DHCP provided IPv4 address to appear.
Any chance
On 2-aug-2007, at 21:17, Dave Crocker wrote:
It was also interesting to open the Mac network control pannel,
enable my Airport (WLAN) interface, and see the IPv6 global
address appear almost instantaneously and in many case having to
wait many seconds to minutes for DHCP provided IPv4
Iljitsch == Iljitsch van Beijnum [EMAIL PROTECTED] writes:
Iljitsch On 2-aug-2007, at 21:17, Dave Crocker wrote:
It was also interesting to open the Mac network control
pannel, enable my Airport (WLAN) interface, and see the IPv6
global address appear almost instantaneously
On Jul 31, 2007, at 6:30 PM, John C Klensin wrote:
And, while I'm picking on DHCP because I personally had more
problems with it, I see IPv6 authconfig as being exactly the same
issue: we are telling the world that these things work and they
should be using them; if we can't make them
A good start would be explaining what exactly went wrong with the
DHCP server(s) this time. We have a problem and we're working on it
is not all that helpful.
I wasn't directly involved in debugging this, but this is what I gathered
from later discussions: The bottom line seemed to be a
JORDI PALET MARTINEZ wrote:
...
The poor network infrastructure is not only a question of the links. It
is a
question of having a good or bad network, like the problem that we had
all
this week with the DHCP. Having a good link the network was still
unusable
60% of the time.
I had no
On Aug 1, 2007, at 12:40 AM, Tony Hain wrote:
JORDI PALET MARTINEZ wrote:
...
The poor network infrastructure is not only a question of the
links. It
is a
question of having a good or bad network, like the problem that we
had
all
this week with the DHCP. Having a good link the network
--On Tuesday, 31 July, 2007 15:40 -0700 Tony Hain
[EMAIL PROTECTED] wrote:
JORDI PALET MARTINEZ wrote:
...
The poor network infrastructure is not only a question of the
links. It is a
question of having a good or bad network, like the problem
that we had all
this week with the DHCP.
On 1-aug-2007, at 0:59, John C Klensin wrote:
Almost independent of the IPv6 autoconfig issues, I find it
deeply troubling that we seem to be unable to both
* get the ducks lined up to run IPv6 fully and smoothly,
with and without local/auto config.
IPv6 worked pretty well
John,
Almost independent of the IPv6 autoconfig issues, I find it
deeply troubling that we seem to be unable to both
* get the ducks lined up to run IPv6 fully and smoothly,
with and without local/auto config.
* get a DHCP arrangement (IPv4 and, for those who
--On Wednesday, 01 August, 2007 01:14 +0200 Iljitsch van Beijnum
[EMAIL PROTECTED] wrote:
* get a DHCP arrangement (IPv4 and, for those who want
to use it, IPv6) that performs reliably, consistently,
and largely invisibly (if I have to worry about what a
DHCP server is
12 matches
Mail list logo
