Hi, Now I'm sure my earlier reply is relevant > Ok, after watching Windows reboot for 30 minutes, here's what I have found: Sorry if this is granny/eggs (or maybe I'm missing something) but you can use ipconfig /renew to get a new lease or simply disable/enable network connection
> 1) The only way to the ABO is if I'm in the same net block as it is (that's the reason for all the reboots). Thats true but the client PC does not need to be able to see the ABO, only the dhcp server on the wired network, and your gateway. You can have the ABO static in one subnet (192.168.100.nnn), and the client getting its IP info from the dhcp server on another (192.168.50.nnn). As far as I can tell, you only really need to see your AB's and other sB kit from the single PC required to manage them - give that pc two (fixed) IP addresses, one in each subnet (worked for me). > 2) I still have not got the DHCP response back through the ABO. Sounds like the dhcp server is not responding "correctly" for the AB to pass the lease on to the client pc. Described in my last mail > 3) I stuck an Orinoco silver in my laptop, and got the DHCP response. Went surfing just fine. .... and not passing through an AB to get a dhcp lease ?? > 4) Orinoco cards are not good for sniffing wireless traffic :( (I'm using Ethereal in Linux) Some recommendations are needed. For this investigation you can see the relevant traffic on your wired network near to the dhcp server. Close Ethereal right down to see just dhcp traffic. If you are getting what I described you will see several retries at getting a lease (say 12+ messages total). When you achieve a successful lease you will see only about 4 messages if I remember correctly - and the world will be a wonderful place once more :) > I have turned off encryption, set the ABO to open, no MAC authentication, > basically it's wide open for anyone to connect to, but I'm still not > getting the DHCP response :( Yup, thats right too. Suspect your dhcp server - perhaps start up another one from your Linux box as a test (turn off the first one). I think Suse Linux recommends that the param to do this (range dynamic-bootp) is NOT set - that could be your problem ? bw ----- Original Message ----- From: "Homer Parker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 21, 2003 11:06 PM Subject: Re: [smartBridges] Clients can't DHCP > On Tue, 21 Oct 2003 11:00:21 -0600 > "Kevin Proctor" <[EMAIL PROTECTED]> wrote: > > > The normal cause for this is that the primary port is not set correctly. > > Here is how it should be set for the link below. > > > > dhcp server - switch - appo (backhaul) appo - switch - appo - abo > > ethernet wireless ethernet - > > wireless > > Ok, after watching Windows reboot for 30 minutes, here's what I have > found: > > 1) The only way to the ABO is if I'm in the same net block as it is > (that's the reason for all the reboots). > > 2) I still have not got the DHCP response back through the ABO. > > 3) I stuck an Orinoco silver in my laptop, and got the DHCP response. > Went surfing just fine. > > 4) Orinoco cards are not good for sniffing wireless traffic :( (I'm using > Ethereal in Linux) Some recommendations are needed. > > I have turned off encryption, set the ABO to open, no MAC authentication, > basically it's wide open for anyone to connect to, but I'm still not > getting the DHCP response :( > > --- > Homer Parker ----------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
