03-11-2009 06:17 PM
If I hook up a desktop PC (set to a static IP 192.168.1.21) to the Bullet's ethernet port, it, too, can ssh and surf to the Bullet on 192.168.1.20, so I know all cables, connectors, wireless links, etc. are working properly.
From our AP, I can ping both the Bullet at 192.168.1.20, and the desktop PC at 192.168.1.21.
However, if I change the desktop ethernet port to try to obtain a DHCP address from the AP using the Bullet as a bridge, the desktop never gets an IP address. If I change the Bullet to obtain an IP from the AP (instead of leaving it at 192.168.1.20) it will obtain a new IP, so I know the DHCP server on my linux AP is working.
How can I configure the Bullet so the desktop PC hooked to its ethernet port, gets its DHCP address from my AP? I thought just setting it to bridge mode should do that - what am I missing? Thanks...
03-12-2009 08:52 AM
I encountered similar symptom with PS2 and other APs:
However, I don't have another DHCP server to test if it is timing problem.
03-12-2009 10:36 PM
03-13-2009 12:39 AM
Have you tried to sniff traffic to analize DCHP requests?
Can you setup WDS on Linux box?
03-16-2009 08:28 AM
Also, the lease expiry time seen from the DHCP server is exceptionally short (2 mins).