On Thursday 18 June 2009 13:51:32 Tim Judd wrote:
> Replies inline
>
> On 6/18/09, Mel Flynn wrote:
> > On Thursday 18 June 2009 10:27:44 Tim Judd wrote:
> >> Long ago in 2007, I saw a M$ article that describes that Vista has an
> >> extremely short delay period to get an IP. If it doesn't get it
On Thursday 18 June 2009 14:30:21 Chuck Swiger wrote:
> On Jun 18, 2009, at 3:14 PM, Glen Barber wrote:
> >> A broadcast of 255.255.255.255 is misconfigured (not saying it's not
> >> gonna work, I'm saying for your network, it's not configured right).
> >> you need broadcast-address 192.168.2.255
>
On Jun 18, 2009, at 3:14 PM, Glen Barber wrote:
A broadcast of 255.255.255.255 is misconfigured (not saying it's not
gonna work, I'm saying for your network, it's not configured right).
you need broadcast-address 192.168.2.255
That is not 100% correct. By default, dhclient will send an initial
The broadcast definition in his snippet is in his subnet declaration.
It is used within the TCP/IP paramaters when it's offering the lease.
DHCP protocol is what you're talking about. And the client has
0.0.0.0 and broadcasts 255.255.255.255 to find any dhcp server that
might be out there. But m
On Thu, Jun 18, 2009 at 5:51 PM, Tim Judd wrote:
> Replies inline
>
> On 6/18/09, Mel Flynn wrote:
>> On Thursday 18 June 2009 10:27:44 Tim Judd wrote:
>>> Long ago in 2007, I saw a M$ article that describes that Vista has an
>>> extremely short delay period to get an IP. If it doesn't get it
>>>
Replies inline
On 6/18/09, Mel Flynn wrote:
> On Thursday 18 June 2009 10:27:44 Tim Judd wrote:
>> Long ago in 2007, I saw a M$ article that describes that Vista has an
>> extremely short delay period to get an IP. If it doesn't get it
>> within 1 second, it gives up (and maybe tries again). Co
On Thursday 18 June 2009 10:27:44 Tim Judd wrote:
> Long ago in 2007, I saw a M$ article that describes that Vista has an
> extremely short delay period to get an IP. If it doesn't get it
> within 1 second, it gives up (and maybe tries again). Common DHCP
> servers ping an IP address, wait 1 seco
On Thursday 18 June 2009 09:56:29 Chuck Swiger wrote:
> Hi--
>
> On Jun 18, 2009, at 10:41 AM, Mel Flynn wrote:
> > Does anyone have a how-to or pitfall summary on how to get a vista
> > computer
> > to:
> > - accept DHCP offers from isc-dhcp30-server-3.0.7_4
> > - connect to WPA-PSK using *any* sc
Long ago in 2007, I saw a M$ article that describes that Vista has an
extremely short delay period to get an IP. If it doesn't get it
within 1 second, it gives up (and maybe tries again). Common DHCP
servers ping an IP address, wait 1 second for a reply, and if no
reply, assumes the IP is availa
Long ago in 2007, I saw a M$ article that describes that Vista has an
extremely short delay period to get an IP. If it doesn't get it
within 1 second, it gives up (and maybe tries again). Common DHCP
servers ping an IP address, wait 1 second for a reply, and if no
reply, assumes the IP is availab
Hi--
On Jun 18, 2009, at 10:41 AM, Mel Flynn wrote:
Does anyone have a how-to or pitfall summary on how to get a vista
computer
to:
- accept DHCP offers from isc-dhcp30-server-3.0.7_4
- connect to WPA-PSK using *any* scheme supported by FreeBSD's hostapd
- give debugging information that makes
Does anyone have a how-to or pitfall summary on how to get a vista computer
to:
- accept DHCP offers from isc-dhcp30-server-3.0.7_4
- connect to WPA-PSK using *any* scheme supported by FreeBSD's hostapd
- give debugging information that makes sense to someone not speaking "if
!not_working throw g
12 matches
Mail list logo
