<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">+1 to this. A while back, the newer
versions of the venerable WRT54G series of routers started
shipping with much weaker hardware and a VxWorks operating system
instead of the classic Linux firmware. Not coincidentally, they
also started to suck at the same time! I recommend Tomato firmware
if your device can take 3rd party builds. I ran it on my current
router for years, only replacing it because my box doesn't have
enough memory to run a 2.6 kernel. <br>
<br>
As I understand it, a DHCP reservation for a particular device can
be added within the scope of the dynamically assigned ones. I
think that's even the official way, although all but the stupidest
firmware could hand one out from outside the range also. <br>
<br>
On 01/25/2014 01:11 AM, Dave Chiodo wrote:<br>
</div>
<blockquote
cite="mid:CAFP7keu1AukziB5F8fon-KLtFtpDWTVfcD0zj+DNOrBMYLY6-A@mail.gmail.com"
type="cite">
<div dir="ltr">Sounds screwy. But with the canned firmware those
things comes with, who knows. I tend to avoid the "stock"
firmware and prefer OpenWRT or Tomato.
<div><br>
</div>
<div style="">I can't imagine any reason having some fixed-IP
devices would be a problem. Technically even if they were in
the DHCP range it should be ok, as the DHCP service SHOULD do
a ping to make sure an address isn't claimed before assigning
it. (keyword "should" - so probably better to keep them
non-overlapping)</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Jan 24, 2014 at 9:55 PM, Eric
Beversluis <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ebever@researchintegration.org"
target="_blank">ebever@researchintegration.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Fri, 2014-01-24 at 21:28 -0500, Dave
Chiodo wrote:<br>
> The guy sounds like he has no idea what he's talking
about.<br>
><br>
><br>
> Are you trying to get the IP address that has been
assigned to the<br>
> router from upstream(the ISP)?<br>
><br>
><br>
> Or are you trying to see which IP's its DHCP server
to client<br>
> PCs/devices?<br>
><br>
</div>
Just wanting to see which leases the router has provided to
my various<br>
computers and printers. The attached devices list doesn't
give all the<br>
outstanding leases and, for some reason, doesn't show the
address<br>
assigned to the Mac, just shows its MAC and dashes in the IP
addr box.<br>
<br>
It's probably worth my while to reset the router to fac
default and<br>
reconfig it to see if that helps.<br>
<br>
Is there any reason that having some devices with fixed IP
addresses<br>
should cause problems for a lower end router like this?
There's no<br>
overlap with the assigned DHCP range.<br>
<div class="HOEnZb">
<div class="h5"><br>
><br>
><br>
><br>
><br>
><br>
> On Fri, Jan 24, 2014 at 7:36 PM, Eric Beversluis<br>
> <<a moz-do-not-send="true"
href="mailto:ebever@researchintegration.org">ebever@researchintegration.org</a>>
wrote:<br>
> I just spent a frustrating time (incl 20+
min waiting) on chat<br>
> with<br>
> Netgear to learn how to find the dhcp
leases on one of their<br>
> wireless<br>
> routers (WPN824N). After being hassled for
when and where I<br>
> bought it (I<br>
> thought Microcenter, but wasn't sure) the
guy finally said<br>
> that you<br>
> couldn't find the info there but had to
look at the modem.<br>
><br>
> "As I checked my resources about the
concern, there is no<br>
> settings in<br>
> the router which you can configure and view
the DHCP list.<br>
> Because it<br>
> can only be found on the modem's interface.<br>
> Eric Beversluis: ???? That's never been the
case with any<br>
> other wireless<br>
> router I've had. The moden wouldn't know
anything about it<br>
> since the<br>
> NAT'ing is done with the router.<br>
> Johnpaul Delatorre: You can check on the
modem's interface<br>
> where to<br>
> locate the list of DHCP leases and how to
configure it."<br>
><br>
> Am I totally wrong in thinking this was
nonsense? The router<br>
> is doing<br>
> the NAT'ing and assigning the DHCP leases,
so why would that<br>
> info be on<br>
> the modem and not on the router?<br>
><br>
> I'm thinking they just didn't bother to
make that info<br>
> available on this<br>
> particular model. But why would they do
that? Surely it's just<br>
> some<br>
> boilerplate coding to include in the
webconfig pages. I don't<br>
> think I've<br>
> ever had a wireless router that didn't show
this.<br>
><br>
> Or am I all wet?<br>
><br>
>
_______________________________________________<br>
> grlug mailing list<br>
> <a moz-do-not-send="true"
href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
> <a moz-do-not-send="true"
href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug"
target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
><br>
><br>
> _______________________________________________<br>
> grlug mailing list<br>
> <a moz-do-not-send="true"
href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
> <a moz-do-not-send="true"
href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug"
target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
<br>
<br>
_______________________________________________<br>
grlug mailing list<br>
<a moz-do-not-send="true" href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
<a moz-do-not-send="true"
href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug"
target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
grlug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grlug@grlug.org">grlug@grlug.org</a>
<a class="moz-txt-link-freetext" href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a></pre>
</blockquote>
<br>
</body>
</html>