(Please trim inclusions from previous messages)
_______________________________________________
can someone please volunteer to add this to the wiki?
On Sun, May 11, 2014 at 7:00 AM, <44net-request@hamradio.ucsd.edu> wrote:
> Send 44Net mailing list submissions to
> 44net@hamradio.ucsd.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://hamradio.ucsd.edu/mailman/listinfo/44net
> or, via email, send a message with subject or body 'help' to
> 44net-request@hamradio.ucsd.edu
>
> You can reach the person managing the list at
> 44net-owner@hamradio.ucsd.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of 44Net digest..."
>
>
> Today's Topics:
>
> 1. Re: 44Net Digest, Vol 3, Issue 89 (David Ranch)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 10 May 2014 09:22:32 -0700
> From: David Ranch <amprgw@trinnet.net>
> To: AMPRNet working group <44net@hamradio.ucsd.edu>
> Subject: Re: [44net] 44Net Digest, Vol 3, Issue 89
> Message-ID: <536E5248.2020404@trinnet.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> > Do we need a standard ruleset, and documentation to use it, and have this
> > in the wiki? iptables or iproute2? Does anyone HAVE a working iproute2
> > setup?
>
> There are tons of example iptables examples out there though I always
> recommend people to review and tailor the ruleset for their own needs.
> One such non-AMPR example is the IP Masquerade HOWTO example:
>
>
> http://www.tldp.org/HOWTO/IP-Masquerade-HOWTO/stronger-firewall-examples.html#RC.FIREWALL-IPTABLES-STRONGER
>
> The above example is distribution agnostic so it should work on your
> preferred flavor but there can be benefits of adapting it to either your
> distribution's native firewall syntax or to some higher level tool that
> incorporates features like QoS, etc (shorewall, etc). I'm willing to
> take a stab at putting a baseline config into the Wiki but give me a bit
> to troll through the archives, review various people's submitted
> configs, etc. and hopefully come up a config that will work for most
> base deployments.
>
> --David
> KI6ZHD
>
>
>
> ------------------------------
>
> _______________________________________________
> 44Net mailing list
> 44Net@hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
>
>
> End of 44Net Digest, Vol 3, Issue 96
> ************************************
>
--
Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
+64 21 040 5067
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20140512/47612572/attachment.html>
_________________________________________
44Net mailing list
44Net@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net