Sorry to spam the list with repeated questions but I am still having no luck with E2B and a private DMZ network. I guess this functionality is just supposed to work out of the box and I must have misconfigured something.
I have tried the same setup on two different firewalls with pretty much the same results: services advertised in the DMZ are not accessible from the local or external networks. Could someone please just have a quick look at the following questions? - could you please confirm that the DMZ network must be part of the defined 'internal' network. - in a DMZ_SERVERn entry, should the extended port forward definition be in double quotes? Or is this irrelevant? DMZ_SERVER0=tcp_150.101.234.2_www_192.168.2.10_www DMZ_SERVER1="udp_150.101.234.2_www_192.168.2.10_www" - if the DMZ is working, there should be some extra rules in the ipchains list. Could one of you please provide one example rule that is private-DMZ specific so that I can check that this is working. To date, switching on (or off) the DMZ and then /etc/init.d/network restart seems to have no effect on ipchains definitions (as reported in an email yesterday). - and finally (and sorry for the newbie question) when accessing services in the DMZ from the local network(s), should the actual IP address of the server on the DMZ network or the external IP address of the LRP box be used? Thanks for your patience. :-) matt _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
