public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: openvpn configuration
Date: Thu, 14 May 2009 21:35:53 -0600	[thread overview]
Message-ID: <BF99B461FB68474FAD8D4FD3BD981FA5@tdsdev> (raw)
In-Reply-To: <9DE2BE714A544A09823B37759770E443@kazam>

It's fine. kids have exploits they run on the servers, but I'm not that 
stupid. vpn is a lot more um, quiet, so I doubt they'll care as much over 
the kids running exploits when they want to log to facebook. Not like I'm 
looking at porn, just want to be able to do research. Anything with phpbb is 
blocked, and I'm frequently reading articles.
When I try to set up tun, I need to use ifconfig to set up the tunnel; I 
won't always have the same IP, though.


Thanks,
Tyler Littlefield
Web: tysdomain.com
email: tyler@tysdomain.com
My programs don't have bugs, they're called randomly added features.

----- Original Message ----- 
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, May 14, 2009 9:22 PM
Subject: Re: openvpn configuration


> Firstly:
> understand the difference between tun and tap.
> You must use the *same* on both ends, tun for routed vpn, tap for bridged.
>
> decide whether you want routed or bridged and set up accordingly.
> Info on openvpn.net on which is bbest, routed is more scalable and there 
> are tricks to hand out a default gateway on a bridged setup.
>
> these tricks may or may not work with Windows openvpn client see faq 
> files.
>
> I'd set up dev tun on both ends and make sure you can see the other end of 
> your tunnel.
> Best to make connectivity work before you mess with default routes etc.
>
> Is it worth noting here that you are probably violating policy by punching 
> holes through a firewall?
> be aware in case admin comes down on you.
>
> Regards, Kerry.
>
>
>
> ----- Original Message ----- 
> From: "Tyler Littlefield" <tyler@tysdomain.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Friday, May 15, 2009 3:08 AM
> Subject: openvpn configuration
>
>
>> Hello list,
>> I'm currently trying to get openvpn going. I have the port open, but it's 
>> not letting me forward all traffic through, for some reason. Any ideas? 
>> I've provided my configs below
>> #server:
>> dev tun
>> secret static.key
>> keepalive 10 60
>> ping-timer-rem
>> persist-tun
>> persist-key
>> user nobody
>> group nobody
>> daemon
>> plugin /usr/share/openvpn/plugin/lib/openvpn-auth-pam.so login
>> push "redirect-gateway def1"
>> #client:
>> dev tap
>> remote tds-solutions.net
>> secret C:/static.key
>> keepalive 10 60
>> ping-timer-rem
>> persist-tun
>> push "redirect-gateway def1"
>> resolv-retry infinite
>> nobind
>> proto udp
>> I want to be able to connect from multiple sources, so I used dev tap.
>>
>> Thanks,
>> Tyler Littlefield
>> Web: tysdomain.com
>> email: tyler@tysdomain.com
>> My programs don't have bugs, they're called randomly added features.
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Kerry Hoath
   ` Tyler Littlefield [this message]
     ` Kerry Hoath
       ` Tyler Littlefield
         ` Kerry Hoath
           ` Tyler Littlefield
             ` Kerry Hoath
               ` Tyler Littlefield
                 ` Kerry Hoath
 ` Alex Snow

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=BF99B461FB68474FAD8D4FD3BD981FA5@tdsdev \
    --to=tyler@tysdomain.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).