It appears that the problem is not with bering at all but with the linux router that connects to the internet and is the default gateway for all boxes in the 192.168.0 subnet. The bering firewall has IP 192.168.0.250. I have a route on the linux firewall connected to the internet that says
192.168.100.0/24 via 192.168.0.250 dev eth2 I would think this would send a redirect back to the systems in the 192.168.0 range telling them to send to the 192.168.0.250 address as the gateway for the 192.168.100 range. This is not happening and I think that that is the problem. Thanks for all the suggestions as they helped me get to this point. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
