Hi,

Bit of a novice just setting up first clients, but I have spent the weekend
on a similar problem.  I am confused that you have another APT facing the
APP and working, but perhaps there is something different about the way
clients are connected beyond the APT ?   FWIW heres how I solved mine.

AP and AB behave differently when attempting to get a dhcp lease.  I used AP
'til now successfully with dhcp working well.  When I added my first AB I
eventually discovered that the dhcp server was not behaving as expected.
Its a little complex but you can see whats going on with Ethereal if you
look carefully.  For me it transpired that the dhcp server was responding to
the unicast address - seen by the AB but not by the client on the other
side.  To work correctly the dhcp server must respond to the broadcast
address (Broadcast flag set 0x8000) and the AB will pass this through to the
client to recognise its own mac address in the BootP part of the offer (the
message containing the dhcp lease info).  At first glance with Ethereal it
looks as if the reply is directly to the client address - this will not
work - it won't get past the AB.

The key to this is in the very informative FAQ for the latest AirBridge
software on sB site http://www.smartbridges.com/new/support/faq_ab.php#36
Item 7 entitled How to make sure the client computers behind airBridge can
get IP address automatically from DHCP server with firmware 0.01.04 or
newer?   It has a brief description of how DHCP Discover and Offer packet
work


My dhcp server is (was) part of the "value added" stuff that comes "free"
with Aramiska satellite kit.  I added another firewall with its own proper
dhcp server facing the radio network (Netscreen 5XP - brilliant kit) and
everything is working just fine.

I have also decided to use fixed IP for the infrastructure kit (all sB) as
this is the only sensible option with the way SimpleNMS operates (a really
painful piece of useful software), whilst having all client PCs use dhcp on
a different subnet. Grateful for others ideas / experiences.

Hope this helps.  Even if you don't have ABs it might help someone else !!
bw



----- Original Message ----- 
From: "Kirk Gildroy" <[EMAIL PROTECTED]>
To: "smartBridges" <[EMAIL PROTECTED]>
Sent: Tuesday, October 21, 2003 5:23 PM
Subject: [smartBridges] Clients can't DHCP


> I have a new APT that I'm having trouble with my clients not being able to
> hit the DHCP server.  I have one other APT setup exactly the same way
> associated with the same APP and the clients connected to it have no
problem
> with DHCP.  I am currently searching the archives to see if this has
already
> been answered but these folks needed to be set up like yesterday (as
usual)
> so please forgive me if this has already been addressed.  By the way, with
> IP's setup static I have no problem hitting the IP address of the DHCP
> server or anything else for that matter.  I'm pulling my hair out...please
> help.
>
> Kirk Gildroy

----------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  

Reply via email to