1) On this page: http://www.shorewall.net/Manpages6.html
there is no snat link. However, the man page does exist:
http://www.shorewall.net/manpages6/shorewall6-snat.html
2) For the SNAT ACTION on the snat man page, there is an example using IPv4
addresses:
Example: 206.124.146.177-206.124.146.
Hi Bill,
On Thu, Nov 21, 2019 at 02:00:31PM -0500, Bill Shirley wrote:
> 1) On this page: http://www.shorewall.net/Manpages6.html
> there is no snat link. However, the man page does exist:
> http://www.shorewall.net/manpages6/shorewall6-snat.html
>
> 2) For the SNAT ACTION on the snat man page,
On Thu, 21 Nov 2019 14:00:31 -0500
Bill Shirley wrote:
> 1) On this page: http://www.shorewall.net/Manpages6.html
> there is no snat link. However, the man page does exist:
> http://www.shorewall.net/manpages6/shorewall6-snat.html
Ok. I have answers for you. On shorewall 5.2 man pages for shore
So for #2 below, at https://shorewall.org/manpages/shorewall-snat.html which
documents IPv4 & IPv6
For SNAT, it would be nice to have a IPv6 example also:
[2001:470:a:227::2-2001:470:a:227::10]
For #3, at https://shorewall.org/4.6/manpages6/shorewall6-masq.html
The example uses ']-[' to
I forgot to mention the proxyndp link on https://shorewall.org/Manpages.html
gives https://shorewall.org/manpages6/shorewall-proxyndp.html which is *404
Not Found*
The working link is https://shorewall.org/manpages/shorewall-proxyndp.html
Note: no six in manpages.
Bill
___
On Fri, 20 Dec 2019 03:45:18 -0500
Bill Shirley wrote:
> So for #2 below, at
> https://shorewall.org/manpages/shorewall-snat.html which documents
> IPv4 & IPv6 For SNAT, it would be nice to have a IPv6 example also:
>
>[2001:470:a:227::2-2001:470:a:227::10]
Refused. Reason: We must not docu
I guess I should have said a *correct* IPv6 example along with the IPv4
example because that document covers both IPv4 and IPv6.
Bill
On 12/20/2019 4:50 AM, Tuomo Soini wrote:
On Fri, 20 Dec 2019 03:45:18 -0500
Bill Shirley wrote:
So for #2 below, at
https://shorewall.org/manpages/shorewall-
On Fri, Dec 20, 2019 at 10:05:04AM +0200, Tuomo Soini wrote:
> On Thu, 21 Nov 2019 14:00:31 -0500
> Bill Shirley wrote:
>
> > 2) For the SNAT ACTION on the snat man page, there is an example
> > using IPv4 addresses: Example: 206.124.146.177-206.124.146.180
> > This example should probably use IP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/22/19 4:23 PM, Roberto C. Sánchez wrote:
> On Fri, Dec 20, 2019 at 10:05:04AM +0200, Tuomo Soini wrote:
>> On Thu, 21 Nov 2019 14:00:31 -0500 Bill Shirley
>> wrote:
>>
>>> 2) For the SNAT ACTION on the snat man page, there is an
>>> example
On Sun, Dec 22, 2019 at 08:20:47PM -0800, Tom Eastep wrote:
>
>
> On 12/22/19 4:23 PM, Roberto C. Sánchez wrote:
> > On Fri, Dec 20, 2019 at 10:05:04AM +0200, Tuomo Soini wrote:
> >> On Thu, 21 Nov 2019 14:00:31 -0500 Bill Shirley
> >> wrote:
> >>
> >>> 2) For the SNAT ACTION on the snat man pa
On 12/23/19 6:23 AM, Roberto C. Sánchez wrote:
> On Sun, Dec 22, 2019 at 08:20:47PM -0800, Tom Eastep wrote:
>>
>>
>> On 12/22/19 4:23 PM, Roberto C. Sánchez wrote:
>>> On Fri, Dec 20, 2019 at 10:05:04AM +0200, Tuomo Soini wrote:
On Thu, 21 Nov 2019 14:00:31 -0500 Bill Shirley
wrote:
>>
On Thu, 19 Dec 2019 22:38:48 -0500
Roberto C. Sánchez wrote:
> Hi Bill,
>
> On Thu, Nov 21, 2019 at 02:00:31PM -0500, Bill Shirley wrote:
> > 1) On this page: http://www.shorewall.net/Manpages6.html
> > there is no snat link. However, the man page does exist:
> > http://www.shorewall.net/manpag
On Mon, Dec 23, 2019 at 09:53:00AM -0800, Tom Eastep wrote:
> On 12/23/19 6:23 AM, Roberto C. Sánchez wrote:
> >
> > I'd like to see if we can exercise the merge request process. Would you
> > be willing to submit your proposed change as a merge request?
> >
>
> Roberto,
>
> I certainly can --
On 12/25/19 7:00 AM, Roberto C. Sánchez wrote:
> I favor including the documentation changes in the same MR as the code
> changes. I don't have a strong feeling on if the documentation changes
> should be in the same commit as the code changes or if code and
> documentation are changed in separat
On 12/25/19 8:41 AM, Tom Eastep wrote:
> On 12/25/19 7:00 AM, Roberto C. Sánchez wrote:
>
>> I favor including the documentation changes in the same MR as the code
>> changes. I don't have a strong feeling on if the documentation changes
>> should be in the same commit as the code changes or if c
15 matches
Mail list logo