Hi Julie, Did you also try dnsmasq as dhcpd?
Eric > Hi, > > > thanks to all who have tried to assist with this matter of DHCP through a > wirless Bridge (esp Erich & Tom) i'm having a hard time just giving up on > this since i know it's possible! In fact I have reverted to my Bering 1.2 > firewall and DHCP through my wireless bridge magically works again. the > only thing different ( i think) is using the current dhcpd.lrp (doens't > work) vs dhcpd3.lrp (works). > > perhaps theres some difference in these dhcp daemons? some other package > that i also need to run for some reason? ( ex. i am running snmp under > Bering 1.2 firewall but not > under Bering 2.3) can I run dhcpd3.lrp with Bering 2.3 ? yes, i'm reaching > for a usable work-around. I'd appreciate any useful feedback/comments that > might help me work this out. > > when I do the tcpdump on my firewall and dhcp works, i never see the MAC > address of the client machines, just the bridge. The client sees the > response and gets the address just fine. the daemon.logs show the request > being honored just fine. > > this has been clearly diagnosed as the problem (works when I force > cloning). when it does not work, i see the bridge forwarding the request > out to the firewall but when the dhcp server tries to send the reply to the > MAC address of > the client, it's blocked at the bridge. > > p.s. I also made sure that dhcp was an option on my eth4 shorewall > interface that serces the wireless. > > Tom Eastep wrote: > > >> On Monday 28 November 2005 15:53, Julie S. Lin wrote: >> >> >> >> >>> 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. >>> >>> >> >> FWIW, I see the same results. I'm unable to get DHCP to work through a >> WET11 >> Linksys bridge (see http://www.shorewall.net/myfiles.htm). >> >> >> -Tom >> >> >> > > > > ------------------------------------------------------- > 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: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > ------------------------------------------------------- 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: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
