Julie S. Lin wrote: > Hi All, > > I'm still having trouble with the DHCP, and I'm hoping someone can point > me in the right direction > I'm running a dhcp server on my 192.168.30.0/wireless network out of > dhcpd.lrp. If I have > a wireless card, everything works fine. > > I then added a wireless bridge, which sees the AP fine and allows > connectivity to my test machine (MAC 00:0d:88:1c:03:b7) > provided it has a static ip. The mac filtering on the AP allows the MAC > address of the bridge ( 00:02:67:07:85:FE ) and does not > require allowing the mac address of the test machine > > However, when I set my test machine to use DHCP, i get the following > behavior: > my machine connected to the wirless bridge tries to get an address via > DHCP and my firewall/dhcp server responds appropriately > however, the test machine never sees the ip address that is offered. > what do I need to change? my Bering 1.2 dhcp config was somehow able to > do this, so I'm pretty sure I'm missing some > simple configuration somewhere. i'm hoping to get the bridge to > essentially turn any ethernet device into a wireless device > (like its supposed to) through use of a hub. > > below is some info I hope you all will find helpful. I can use cloning > to force the DHCP requests to go back to the right > MAC address, which works, but limits me greatly as guests can not simply > plug into our wireless network and borrow internet > access (which is what we want). > > (from daemon.log) > Nov 28 22:41:50 sid dhcpd: DHCPDISCOVER from 00:0d:88:1c:03:b7 via eth4 > Nov 28 22:41:50 sid dhcpd: DHCPOFFER on 192.168.30.100 to > 00:0d:88:1c:03:b7 via eth4 > (from tcpdump ) > 22:49:13.299525 0:2:6f:7:85:fe Broadcast ip 342: 0.0.0.0.bootpc > > 255.255.255.255.bootps: xid:0xe23dd08 secs:2816 flags:0x8000 ether > 0:d:88:1c:3:b7 [|bootp] > 22:49:13.300325 0:2:b3:39:57:47 0:d:88:1c:3:b7 ip 342: > 192.168.30.1.bootps > 255.255.255.255.bootpc: xid:0xe23dd08 secs:2816 > flags:0x8000 Y:192.168.30.100 S:192.168.30.1 [|bootp] [tos 0x10]
To me this looks like this is another address offering dhcp. Above you have 192.168.30.100 and here 192.168.30.1 Could you explain this? cheers Erich ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
