Hi Craig I'll ask him to test these and see if it helps.
Here's a short example of the dhcp log: Unusual System Events =-=-=-=-=-=-=-=-=-=-= Sep 10 13:00:31 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:00:32 logan2 dhcpd: DHCPOFFER on 204.96.181.161 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:01:02 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:01:03 logan2 dhcpd: DHCPOFFER on 204.96.181.190 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:01:33 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:01:33 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:01:34 logan2 dhcpd: DHCPOFFER on 204.96.181.217 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:01:34 logan2 dhcpd: DHCPOFFER on 204.96.181.171 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:02:04 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:02:05 logan2 dhcpd: DHCPOFFER on 204.96.181.209 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:02:35 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:02:36 logan2 dhcpd: DHCPOFFER on 204.96.181.215 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:03:06 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:03:07 logan2 dhcpd: DHCPOFFER on 204.96.181.160 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:03:37 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:03:37 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:03:38 logan2 dhcpd: DHCPOFFER on 204.96.181.243 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:03:38 logan2 dhcpd: DHCPOFFER on 204.96.181.213 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:04:08 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:04:09 logan2 dhcpd: DHCPOFFER on 204.96.181.238 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:04:39 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:04:40 logan2 dhcpd: DHCPOFFER on 204.96.181.223 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:05:10 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 Sep 10 13:05:11 logan2 dhcpd: DHCPOFFER on 204.96.181.204 to 00:10:4b:f2:21:a1 (Gate2000) via 204.96.181.131 Sep 10 13:05:41 logan2 dhcpd: DHCPDISCOVER from 00:10:4b:f2:21:a1 via 204.96.181.131 (This goes on all day and all night....) I'll have him check those items you mentioned and see if it helps. Thanks! Sam On Wed, 10 Sep 2003 [EMAIL PROTECTED] wrote: > Sounds to me like a possible problem with the ethernet connection between the > PC and the airbridge. That means one of the following: > > - Problem with the PC's NIC > - Problem with the Airbridge's NIC > - Problem with the cable > > If the customer is using WinXP, it detects when the ethernet connection goes > down. If the connection is bouncing, the PC will ask for a new IP address > every time the ethernet comes back up. They'll also (obviously) lose their > connection when it goes down. Remember to try setting the NIC to 10 meg half > duplex. Some NICs have trouble with auto negotiating. > > Craig > > > Quoting Sam <[EMAIL PROTECTED]>: > > > Hi Craig > > > > The customer claims that it causes his PC to "drop off the network" for a > > few seconds each time it happens. The frquency of requests vary from three > > or four times in a one to two second period, to once each three to four > > minutes. > > > > The TTL is set to an hour. > > > > As soon as I grab the logs again (once an hour) and these entries are in > > there I'll post it. > > > > Thanks Everyone > > Sam > > > > On Wed, 10 Sep 2003 [EMAIL PROTECTED] wrote: > > > > > Back to answering Sam's question, since this thread seems to have > > diverged... > > > > > > When DHCP hands out an IP, it also hands out a lease time. After that > > lease > > > time expires, the client is supposed to ask for an IP again. You didn't > > > mention how often these DHCP requests are re-ocurring, so I can't say for > > sure > > > whether this is what is happening. But if your lease time is set low, it > > > > > would be normal for the client to ask for an IP fairly often. > > > > > > As for who is responsible for holding the IP, it is the client PC. It > > holds > > > the IP address, and it asks for a new one when the lease is up. The > > Airbridge > > > doesn't have anything to do with any of this. > > > > > > The question I have is, why does the customer care how often it's > > requesting > > > an IP? I don't think it would cause a problem, aside from a little extra > > > > > traffic from the dhcp requests. > > > > > > Craig > > > > > > > > > Quoting Sam <[EMAIL PROTECTED]>: > > > > > > > Hi Smart People > > > > > > > > Hi smart people! > > > > > > > > I have a simple question: Who is responsible for "holding onto" an ip > > > > address from a dhcp server? > > > > > > > > I have a customer (about 12 miles from my ap) who constantly requests a > > > > new ip address. He is given one by the dhcp server, but not long after > > > > that he's back asking for another one. My customer is convinced it's > > the > > > > Airbridge (indoor) that is bad. > > > > > > > > I don't think it's the ABI's responsibility to hold the ip. I think > > it's > > > > his PC's, but then I'm not positive. > > > > > > > > He has good LQ and RSSI. > > > > > > > > (I can post a portion of the dhcp logs if it will help.) > > > > > > > > Thanks > > > > Sam > > > > > > > > > > > > ----------ANNOUNCEMENT---------- > > > > Don't forget to register for WISPCON IV > > > > http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm > > > > > > > > The PART-15.ORG smartBridges Discussion List > > > > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe > > smartBridges > > > > <yournickname> > > > > To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe > > > > smartBridges) > > > > Archives: http://archives.part-15.org > > > > > > > > > > > > > > > > > ----------ANNOUNCEMENT---------- > > > Don't forget to register for WISPCON IV > > > http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm > > > > > > The PART-15.ORG smartBridges Discussion List > > > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe > > smartBridges <yournickname> > > > To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe > > smartBridges) > > > Archives: http://archives.part-15.org > > > > > > > ----------ANNOUNCEMENT---------- > > Don't forget to register for WISPCON IV > > http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm > > > > The PART-15.ORG smartBridges Discussion List > > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges > > <yournickname> > > To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe > > smartBridges) > > Archives: http://archives.part-15.org > > > > > > > ----------ANNOUNCEMENT---------- > Don't forget to register for WISPCON IV > http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm > > The PART-15.ORG smartBridges Discussion List > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges > <yournickname> > To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) > Archives: http://archives.part-15.org > ----------ANNOUNCEMENT---------- Don't forget to register for WISPCON IV http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
