Tom, Thanks for the reply. I will use the V 4.4 versions of masq and interfaces that I currently am using.
The FW provides the DHCP server functionality. I didn't think that Shorewall was at fault, however, I was concerned that the configuration files I was using were not correct and were therefore somehow involved. After some investigation of the DHCP3 logs (daemon.log) it may be something in there. I will snip most of the prior message. Cheers, Jay On 03/13/2011 09:24 AM, Tom Eastep wrote: > Jay, > > On 3/13/11 3:11 AM, Jay Ridgley wrote: > -- snip -- >> According to the //http:www.shorewall.net/LennyToSqueeze.html the masq >> entries >> should now read: >> eth0 192.168.139.0/28 >> eth0 192.168.139.32/28 > > That is preferable to what you had previously. You can also just have: > > eth0 0.0.0.0/0 > >> >> and the interfaces entries should be: >> net eth0 detect dhcp,tcpflags,nosmurfs,routefilter,logmartians >> loc eth3 detect tcpflags,nosmurfs,routefilter,logmartians >> loc eth4 detect dhcp >> > > Either interfaces config is fine. > -- snip -- > > Which box runs the DHCP server for the wireless segment? The AP or the > Shorewall box? If it is the Shorewall box, then the DHCP server's log > should tell you if clients are renewing their leases or not. When it > stops working, can you still ping the AP? I can ping the APs fixed ip (192.168.139.33). Cheers, Jay -- Jay Ridgley [email protected] Registered Linux User ID - 9115 Registered Ubuntu User ID - 23320 ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
