On Wed, 17 May 2006 15:13:40 +1200 Christopher Sawtell wrote: > > to each end. ipcop gui, firewall->firewall options->disable ping > > response: set to no. > > Bug 1: it never accepts pings from internal, server, > > or outside (just logs and dumps). > But you have just turned off ping response, so I wouldn't expect any. > It all depends on your precise meaning of the word "accept", I wonder if > you would be so kind as to elucidate.
Disable ping response=no == enable ping response. so it should work, note the double negative. > If they are correct, I'm sure your patches would be very welcome. Please > note that _I_ trust the IPCOP team completely, What I'd really like to see > is the facility to run the hostap driver for the Prism 2.5 Wavelan > chipset, but I believe that mandates a kernel update to the 2.6 series. > Whether or not that's a good idea is highly debatable. What do you think? My access point has been running hostap on kernel 2.4 until last weekend when I upgraded pebble distro to voyage distro. Very nice it is too. I've offered to demonstrate voyage at the next GNuz meeting, but Rik is still to get back to me. Whether it is a good idea to implement your access point on the same machine that is protecting your newtwork is debateable. Wireless is insecure, and gives you a pretty major leap in cracking the ipcop firewall I would have thought. My setup has two boxes, AP and IPCOP separate. The AP is an old laptop with two PCMCIA cards - one wired and one wireless. -- Nick Rout <[EMAIL PROTECTED]>
