I did that once with a bunch or tranzeos. Works good. of course, having a
switch up on a tower isnt practical. I'm sure there must be a registry entry
for the dhcp timeout on windoze somewhere?

On Fri, Aug 20, 2010 at 5:37 PM, John Valenti <vale...@lir.msu.edu> wrote:

> Justin,
> I would think you would want to have it setup to just switch quickly to a
> static address via profile or script or something.
>
> But perhaps another solution would be to use a switch or hub? If your
> windows computer is plugged into that (rather than directly into a radio),
> it will keep ethernet carrier and not want to look for a new address every
> time you switched radios. So it would just keep using the autoassigned one.
> (I think)
>
> I don't use Mikrotik much, I vaguely remember it uses a program that
> manages radios without using IP addressing? Perhaps that is why your auto
> assigned 169. address is of any value. Almost all the radios I've used
> (Trango, Tranzeo, StarOS) you have to use a specific subnet (not auto
> assigned) to talk to it. So I started out with a system that let me rapidly
> switch between a few statics and dhcp.
>
> Hope that helps.
>
> On Aug 20, 2010, at 4:01 PM, Justin Wilson wrote:
>
> >    The whole thing is windows takes so long if there is no DHCP server
> available.  For example, plug into a fresh Mikrotik with no configuration.
>  How long does Windows take to time out if it is set to DHCP?  I have timed
> this at 1.5 minutes.  My mac only takes 17 seconds to say “hey there is no
> DHCP server I will auto assign a 169 IP”.  What I am looking for is a way to
> tell Windows don’t wait 1.5 minutes before you assign a 169 IP.  Only wait
> 20 seconds or whatever.
> >
> >     Sure you can assign a static IP and lessen this time, but assigning
> that IP takes time to do and undo.
> >
> >     The best solution I have seen so far is Barnes’s suggest for a
> program that lets you change networking profiles.  I was hoping someone knew
> of a registry key you could edit.  Something like DHCP_TIMEOUT=20s.  Instead
> of DHCP_TIMEOUT=120s.
>
>
>
>
> --------------------------------------------------------------------------------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
>
> --------------------------------------------------------------------------------
>
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>

--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to