Folks, I have a situation that needs clarification. I am able to get the wired side of my network running just fine, however, the wireless access point that I have set up is malfunctioning.
According to the docs for Adding a Wireless Segment to your Two-Interface Firewall (http://www.shorewall.net/two-interface.htm) The only changes that needed to be made were to add a line to the interfaces file and one to the masq file. The entries I have are: the interfaces entries - net eth0 detect dhcp,tcpflags,routefilter,nosmurfs,logmartians loc eth3 detect tcpflags,nosmurfs loc eth4 detect dhcp the masq entries - eth0 eth3 eth0 eth4 The eth4 lines were the ones I added when I set up the wireless access point last year. I was running Shorewall 4.0.6 then. Now I am running Shorewall 4.4.6, are they still valid or should they be the ones below? 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 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 The behavior that I am getting is when the firewall system is first booted I am able to get to everything but after some period of time the wireless (eth4) part quits, even with NO ACTIVITY. I thing that is a leases problem, since I can reset the wireless access point and all is well again... for a while. -- 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
