From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Re: Should this be included in the wiki?
Date: Thu, 13 Feb 2014 13:18:18 -0600 [thread overview]
Message-ID: <52FD1A7A.20206@dailydata.net> (raw)
In-Reply-To: <CAO6L5t8EJySN8r+3tYnog-kK9WyRw_VRDz-b+92TiqBR7+6y8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2881 bytes --]
Ok, I'm happy to put it out there (I think it should reside on the
IPFire site, not just have a link to my site). The second question is,
where do I put it. It doesn't seem to fit in any of the existing
categories at http://wiki.ipfire.org/en/start.
I guess what I'm asking now is, should we have a new category "Tips and
Tricks" or "How To" or something, or should this go into something
completely different. Guess what I'm asking is where should we document
how to do things once the firewall/router is set up and running.
I actually have a few things I think would be good on the site; one is
installation and configuration of the OpenVPN GUI client for various
operating systems
(http://wiki.linuxservertech.com/index.php?action=artikel&cat=5&id=65)
and another is setting up OpenVPN on an Android and/or iPad
(http://wiki.linuxservertech.com/index.php?action=artikel&cat=5&id=169)
though both need to be redone before I actually moved them.
Anyway, I have no problem keeping them on my site; I just feel people
should get used to looking at the IPFire site. I'd create links to the
IPFire site in my site once it was done.
Rod
On 02/13/2014 01:50 AM, hilmar sandfuehr wrote:
> good morning rod,
> i cant check your wiki, as it is under construction.
>
> but in my personal opinion sharing knowledge is always a good idea
> and even if it doesnt find a place in our wiki, we at least should
> insert a link to your page
>
> cheers
> hilmar
>
>
> 2014-02-12 22:21 GMT+01:00 R. W. Rodolico <rodo(a)dailydata.net
> <mailto:rodo(a)dailydata.net>>:
>
> I ran into a problem with a client running an IPFire firewall, where
> they had employees using teamviewer.com <http://teamviewer.com> to
> access their workstations
> after hours, effectively bypassing the security of the router.
>
> I came up with a solution. Possibly not the best one as it requires
> building a separate name server, but it at least works. I wrote a "How
> To" on one of my sites, but if you think it would be useful, let me know
> where I should put it.
>
> http://wiki.linuxservertech.com/index.php?action=artikel&cat=5&id=198
>
> Feel free to tell me there are better ways to do it or there are better
> uses of the web site.
>
> Rod
> --
> R. W. "Rod" Rodolico
> Daily Data, Inc.
> POB 140465
> Dallas TX 75214-0465
> http://www.dailydata.net
> 214.827.2170 <tel:214.827.2170>
>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org <mailto:Documentation(a)lists.ipfire.org>
> http://lists.ipfire.org/mailman/listinfo/documentation
>
>
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rodo.vcf --]
[-- Type: text/x-vcard, Size: 233 bytes --]
begin:vcard
fn:R. W. Rodolico
n:Rodolico;R. W.
org:Daily Data, Inc.
adr:;;POB 140465;Dallas;TX;75214-0465;US
email;internet:rodo@dailydata.net
title:President
tel;work:214.827.2170
url:http://www.dailydata.net
version:2.1
end:vcard
next parent reply other threads:[~2014-02-13 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO6L5t8EJySN8r+3tYnog-kK9WyRw_VRDz-b+92TiqBR7+6y8A@mail.gmail.com>
2014-02-13 19:18 ` R. W. Rodolico [this message]
2014-02-12 21:21 R. W. Rodolico
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=52FD1A7A.20206@dailydata.net \
--to=rodo@dailydata.net \
--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