FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 02-24-2009, 03:12 AM
"Ashley M. Kirchner"
 
Default VPN

Craig White wrote:

rather than vpn, you might just want to use freenx which is a type of
remote desktop that communicates via ssh and a free client for Linux,
Macintosh or Windows is available from http://www.nomachine.com

yum install freenx-server
copy /etc/nxserver/client.id_dsa.key to your computer running nomachine
client - et voila
Errr, I need to access the Windows network that is BEHIND the FC10,
which is acting as the firewall and DHCP server for the network. So,
I'm sitting at home on a WinXP machine, and I need to access our Windows
Server at the office, which sits behind an FC10 firewall (iptables).


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 03:53 AM
Craig White
 
Default VPN

On Mon, 2009-02-23 at 21:12 -0700, Ashley M. Kirchner wrote:
> Craig White wrote:
> > rather than vpn, you might just want to use freenx which is a type of
> > remote desktop that communicates via ssh and a free client for Linux,
> > Macintosh or Windows is available from http://www.nomachine.com
> >
> > yum install freenx-server
> > copy /etc/nxserver/client.id_dsa.key to your computer running nomachine
> > client - et voila
> Errr, I need to access the Windows network that is BEHIND the FC10,
> which is acting as the firewall and DHCP server for the network. So,
> I'm sitting at home on a WinXP machine, and I need to access our Windows
> Server at the office, which sits behind an FC10 firewall (iptables).
----
and your point is ?

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 03:57 AM
"Ashley M. Kirchner"
 
Default VPN

Craig White wrote:
Errr, I need to access the Windows network that is BEHIND the FC10,
which is acting as the firewall and DHCP server for the network. So,
I'm sitting at home on a WinXP machine, and I need to access our Windows
Server at the office, which sits behind an FC10 firewall (iptables).


----
and your point is ?

Does installing freenx on the FC10 firewall allow me, sitting
outside the network, to connect to the internal network then?


-- A

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 04:00 AM
Craig White
 
Default VPN

On Mon, 2009-02-23 at 21:12 -0700, Ashley M. Kirchner wrote:
> Craig White wrote:
> > rather than vpn, you might just want to use freenx which is a type of
> > remote desktop that communicates via ssh and a free client for Linux,
> > Macintosh or Windows is available from http://www.nomachine.com
> >
> > yum install freenx-server
> > copy /etc/nxserver/client.id_dsa.key to your computer running nomachine
> > client - et voila
> Errr, I need to access the Windows network that is BEHIND the FC10,
> which is acting as the firewall and DHCP server for the network. So,
> I'm sitting at home on a WinXP machine, and I need to access our Windows
> Server at the office, which sits behind an FC10 firewall (iptables).
----
actually, if it's Windows server, then all you really need to do is to
use Remote Desktop Protocol on your Windows system and port forward 3389
to the server (or better yet, pick another 'high' numbered port and
forward that to 3389 on your server using iptables on your F10 firewall.

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 04:10 AM
Craig White
 
Default VPN

On Mon, 2009-02-23 at 21:57 -0700, Ashley M. Kirchner wrote:
> Craig White wrote:
> >> Errr, I need to access the Windows network that is BEHIND the FC10,
> >> which is acting as the firewall and DHCP server for the network. So,
> >> I'm sitting at home on a WinXP machine, and I need to access our Windows
> >> Server at the office, which sits behind an FC10 firewall (iptables).
> >>
> > ----
> > and your point is ?
> >
> Does installing freenx on the FC10 firewall allow me, sitting
> outside the network, to connect to the internal network then?
----
well, assuming that this F10 firewall is actually 2 network cards, 1
with public ip address and 1 with private lan address and providing NAT
for the lan, yes, it would.

Of course running any type of GUI on this firewall is a bad idea in
terms of security.

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 04:16 AM
"Ashley M. Kirchner"
 
Default VPN

> actually, if it's Windows server, then all you really need to do is to
> use Remote Desktop Protocol on your Windows system and port forward 3389
> to the server (or better yet, pick another 'high' numbered port and
> forward that to 3389 on your server using iptables on your F10 firewall.

One server is an NT2000, another is Server 2003. Our remote employees need
to be able to get to their files on those servers.

-- A

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 04:35 AM
Craig White
 
Default VPN

On Mon, 2009-02-23 at 22:16 -0700, Ashley M. Kirchner wrote:
>
> > actually, if it's Windows server, then all you really need to do is to
> > use Remote Desktop Protocol on your Windows system and port forward 3389
> > to the server (or better yet, pick another 'high' numbered port and
> > forward that to 3389 on your server using iptables on your F10 firewall.
>
> One server is an NT2000, another is Server 2003. Our remote employees need
> to be able to get to their files on those servers.
----
Choices

VPN
PPTP
OpenVPN
L2TP (probably need the Win2K3 Server to do that)

Remote Desktop
Terminal Server (requires purchase of licenses)

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 04:41 AM
Michael Cronenworth
 
Default VPN

Ashley M. Kirchner wrote:


One server is an NT2000, another is Server 2003. Our remote employees need
to be able to get to their files on those servers.



I'll share my working OpenVPN server config with you. I have mine set to
use PAM authentication (meaning they'd need an account on your F10
server, LDAP or otherwise) and ignores client certificates, which could
be bad, but it's just me and it's passworded with the user account access.


It should be a few simple changes to use client certs so you don't have
to use PAM. You'll have to generate them yourself.


#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:Program FilesOpenVPNconfigfoo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert cchtml.com.crt
key cchtml.com.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh dh1024.pem

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# the TUN/TAP interface to the internet in
# order for this to work properly).
# CAVEAT: May break client's network config if
# client's local DHCP server packets get routed
# through the tunnel. Solution: make sure
# client's local DHCP server is reachable via
# a more specific route than the default route
# of 0.0.0.0/0.0.0.0.
;push "redirect-gateway"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user openvpn
group openvpn

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "Program FilesOpenVPNlog" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

plugin /usr/lib/openvpn/plugin/lib/openvpn-auth-pam.so login
client-cert-not-required
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 08:42 AM
Agile Aspect
 
Default VPN

Craig White wrote:

On Mon, 2009-02-23 at 22:16 -0700, Ashley M. Kirchner wrote:


actually, if it's Windows server, then all you really need to do is to
use Remote Desktop Protocol on your Windows system and port forward 3389
to the server (or better yet, pick another 'high' numbered port and
forward that to 3389 on your server using iptables on your F10 firewall.


One server is an NT2000, another is Server 2003. Our remote employees need
to be able to get to their files on those servers.


----
Choices

VPN
PPTP
OpenVPN
L2TP (probably need the Win2K3 Server to do that)

Remote Desktop
Terminal Server (requires purchase of licenses)

Craig



And Putty if you need method which you can implement
in less than hour.

I'm assuming that some where in the mix there's Linux machine
running either SSHD or OpenL2TP which the Putty clients or Windows
VPN clients can connect to.

--
Article. VI. Clause 3 of the constitution of the United States states:

"The Senators and Representatives before mentioned, and the Members of
the several State Legislatures, and all executive and judicial Officers,
both of the United States and of the several States, shall be bound by
Oath or Affirmation, to support this Constitution; but no religious Test
shall ever be required as a Qualification to any Office or public Trust
under the United States."



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 
Old 02-24-2009, 06:26 PM
Dan Koehler
 
Default VPN

At 11:42 PM 2/23/2009, you wrote:

----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Feb 2009 20:22:14 -0700
From: "Ashley M. Kirchner" <ashley@pcraft.com>
Subject: VPN
To: "Community assistance, encouragement, and advice for using
Fedora." <fedora-list@redhat.com>
Message-ID: <49A367E6.4040500@pcraft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


At the office I have an FC10 server that acts as our firewall for
our internal network. Eth0 is a public IP, and Eth1 is private.
Connections are handled by iptables. The internal network consists of
private IPs being handed out by a DHCP server running on that same FC10
server. Can someone give me some pointers or links on how I can
configure something that allows me, sitting at home using Windoze, to be
able to connect and access our internal network?

Thanks!


I use OpenSwan and xl2tp for this. Then you can make a new network
connection in Windows at home, to your F10 box, and have access to
the network behind it. http://www.openswan.org/. They also have a
nice mailing list similar to this Fedora list, which is very helpful.


Dan Koehler


--
SCANNED for viruses and
dangerous content by MailScanner.
Believed to be clean.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
 

Thread Tools




All times are GMT. The time now is 06:45 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org