<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=429222003-28022009><FONT face=Arial color=#0000ff size=4>Great
suggestions! I hadn't thought that the VoIP router's DHCP might compete
with the one in the WRT54G, but that's a likely cause of my loss in DHCP
response time! Glad you and Robert reminded me to do the simple fault
isolation also. I had not done that either. Hadn't really dawned on
me that adding VoIP phone is about when the problems began, but now I realize
it's the only change in several years of flawless running.</FONT></SPAN></DIV>
<DIV><SPAN class=429222003-28022009><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=429222003-28022009><FONT face=Arial color=#0000ff
size=4>Chuck</FONT></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
tclug-list-bounces@mn-linux.org [mailto:tclug-list-bounces@mn-linux.org]<B>On
Behalf Of </B>Andrew S. Zbikowski<BR><B>Sent:</B> Friday, February 27, 2009
4:07 PM<BR><B>To:</B> TCLUG-List<BR><B>Subject:</B> Re: [tclug-list] DHCP
problems?<BR><BR></FONT></DIV><FONT face=Arial size=4>Take the VoIP device out
of the loop and see if that corrects your problem. If it does, you've found
the source of your problem. <BR><BR>Your VoIP device should have it's WAN port
connected to the cable/DSL modem, and your WRT54G's WAN port should be
connected to the VoIP device. If you've connected the VoIP device to one of
your WRT54G's LAN ports you've most likely added a second DHCP server to your
network, causing you issues. <BR><BR>Usually cable and DSL providers only give
you a single public IP address, so your VoIP woudl be configured by default to
connect directly to the cable/DSL modem and then act as a NAT router for the
rest of your network. <BR><BR>Check the documentation for your VoIP device.
You can reconfigure your network a couple ways... <BR><BR>If the VoIP device
is acting as a NAT router, you could put your WRT54G into bridge mode so that
it is just an Access Point. The VoIP device would be doing all the NAT, DHCP,
etc. for your network. <BR><BR>You could connect the WRT54G to your cable
modem, and connect the VoIP device to the WRT54G's LAN ports. Consult the
documentation for the VoIP device to determine what Quality of Service
settings your VoIP service requires, and consult the documenation for the
WRT54G to learn how to configure the WRT54G with those required QoS settings.
<BR><BR>What I'd do is:<BR>Connect the WAN port on the VoIP device to the
cable modem. Configure the VoIP device to give out DHCP addresses. Setup a
DHCP reservation for the WRT54G. If the VoIP device has a setting where you
can specify a DMZ destination, set your WRT54G as the DMZ. Any incoming
traffic that the VoIP device isn't going to deal with will now be forwared to
your WRT54G. <BR><BR>Put the WRT54G in router (not bridge) mode as and use as
normal. Because you configured the VoIP device to forward all traffic to the
WRT54G all port forwarding can be done on the WRT54G. <BR><BR>Optional: Get
another Wireless Router, connect it to the VoIP devices WAN port. Configure
this router to serve up guest access to visitors. This way visitors can get
access to the internet, but have no access to your own network. <BR><BR>I've
got an old Linksys router and two WRT54GL's running Tomato in this "Y"
configuration. The old Linksys router gets the public IP, and the WAN ports of
the WRT54GLs connect to the old Linksys router. I've limited the guest network
WRT54GL, turning off things like SMTP and giving the guest network bandwidth
limits, and even limiting what they can access via OpenDNS (</FONT><A
href="http://www.opendns.com/"><FONT face=Arial
size=4>http://www.opendns.com/</FONT></A><FONT face=Arial size=4>). Tomato has
a neat feature where it will rewrite all DNS packets so users on the guest
network can't specify their own DNS servers to get around the OpenDNS filters.
It was a fun little project and much apreciated by the parents of my wife's
panio students. <BR><BR>-- <BR>Andrew S. Zbikowski | </FONT><A
href="http://andy.zibnet.us" target=_blank><FONT face=Arial
size=4>http://andy.zibnet.us</FONT></A><BR><FONT face=Arial size=4>IT Outhouse
Blog Thing | </FONT><A href="http://www.itouthouse.com" target=_blank><FONT
face=Arial
size=4>http://www.itouthouse.com</FONT></A><BR></BLOCKQUOTE></BODY></HTML>