From: Carlo Fusco <fusco.carlo@gmail.com>
To: documentation@lists.ipfire.org
Subject: Re: broken link
Date: Sun, 21 Oct 2018 15:41:45 +0200 [thread overview]
Message-ID: <CAK9whhwLpoE7aV2p4x5dCnH+FVGbp7tBF9X9OxS=iZDFMd_0Wg@mail.gmail.com> (raw)
In-Reply-To: <CAK9whhyCEQU6O0xB5VcvUPcRGV+FfNJWB8WWGx7dkitwgLGxdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
There are also several broken links here:
https://wiki.ipfire.org/configuration/services/openvpn/config
as well as various spelling mistakes spread around the OpenVPN section
of the wiki. The most common one is the german "und". I repeat my
offer to help cleaning up the wiki, as in the past I also did some
work on it. However my credentials are not valid anymore. Should I ask
somewhere else?
On Fri, Oct 19, 2018 at 11:43 AM Carlo Fusco <fusco.carlo(a)gmail.com> wrote:
>
> Hello,
>
> the following page:
>
> https://wiki.ipfire.org/configuration/services/openvpn/extensions/addconf
>
> has this broken link:
>
> https://wiki.ipfire.org/en/configuration/services/openvpn/config/advanced_set#dhcp_und_route_push_optionen
>
> If I can get an account on the wiki, I can correct it myself.
>
> I would like also to update a bit the instructions concerning setting
> the iOS client for OpenVPN. Finally, since it was very confusing for
> me as a newbie, I would like to write somewhere that setting a client
> for using a proxy behind OpenVPN (dhcp-option PROXY_HTTP) is not the
> same thing as connecting to the vpn through a proxy (http-proxy
> directive).
>
> Please let me know if this is acceptable and how should I proceed.
>
> Thanks
>
> --
> Carlo Fusco
--
Carlo Fusco
next prev parent reply other threads:[~2018-10-21 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 9:43 Carlo Fusco
2018-10-21 13:41 ` Carlo Fusco [this message]
2018-10-21 14:41 ` Tom Rymes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK9whhwLpoE7aV2p4x5dCnH+FVGbp7tBF9X9OxS=iZDFMd_0Wg@mail.gmail.com' \
--to=fusco.carlo@gmail.com \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox