Re: [leaf-user] Problem with home firewall.
Hi Rick Tibbs, Richard wrote: ACCEPT netloc:192.168.10.0 255.255.255.0 udp 500 // for office firewall ACCEPT netloc:192.168.10.0 255.255.255.0 udp 4500 ACCEPT netloc:192.168.10.0 255.255.255.0 net 50 ACCEPT netloc:192.168.10.0 255.255.255.0 net 51 ACCEPT loc:192.168.1.0 255.255.255.0 net 50 // for home firewall ACCEPT loc:192.168.1.0 255.255.255.0 net 51 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 500 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 4500 So what I did is comment out with # the lines above and home fw now connects to the internet Some questions: Is upper case required for UDP? What else is wrong with the lines above? Not sure, but the comments look suspicious Erich - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Problem with home firewall.
I agree, shouldn't the comments be on a line by themselves with a # in front? I always separate anything I add by making it really obvious i.e.: # for office ACCEPT net loc:192.168.10.0 255.255.255.0 udp 500 # Tony Erich Titl wrote: Hi Rick Tibbs, Richard wrote: ACCEPT net loc:192.168.10.0 255.255.255.0 udp 500 // for office firewall ACCEPT net loc:192.168.10.0 255.255.255.0 udp 4500 ACCEPT net loc:192.168.10.0 255.255.255.0 net 50 ACCEPT net loc:192.168.10.0 255.255.255.0 net 51 ACCEPT loc:192.168.1.0 255.255.255.0 net 50 // for home firewall ACCEPT loc:192.168.1.0 255.255.255.0 net 51 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 500 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 4500 So what I did is comment out with # the lines above and home fw now connects to the internet Some questions: Is upper case required for UDP? What else is wrong with the lines above? Not sure, but the comments look suspicious Erich - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
[leaf-user] Problem with home firewall.
Hi list. In the old days (Bering 1.2) the following lines would work for access to ipsec in etc/shorewall/rules: ACCEPT net loc:192.168.10.0 255.255.255.0 udp 500 // for office firewall ACCEPT net loc:192.168.10.0 255.255.255.0 udp 4500 ACCEPT net loc:192.168.10.0 255.255.255.0 net 50 ACCEPT net loc:192.168.10.0 255.255.255.0 net 51 ACCEPT loc:192.168.1.0 255.255.255.0 net 50// for home firewall ACCEPT loc:192.168.1.0 255.255.255.0 net 51 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 500 ACCEPT loc:192.168.10.0 255.255.255.0 UDP 4500 So what I did is comment out with # the lines above and home fw now connects to the internet Some questions: Is upper case required for UDP? What else is wrong with the lines above? TIA Rick - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/