Archive | Vyatta

Vyatta VPN User Management

By leerb on January 12, 2014 in Vyatta

Here are the basic commands needed for managing VPN users on the Brocade Vyatta vRouter available in RackSpace Cloud.

Add New User

config
set vpn l2tp remote-access authentication local-users \
username [USERNAME] password [PASSWORD]
commit
save
exit

config

set vpn l2tp remote-access authentication local-users \

username [USERNAME] password [PASSWORD]

commit

save

exit

Remove A User

config
delete vpn pptp remote-access authentication local-users username [USERNAME]
commit
save
exit

config

delete vpn pptp remote-access authentication local-users username [USERNAME]

commit

save

exit

Change User Password

Same as adding a new user.

config
set vpn l2tp remote-access authentication local-users \
username [USERNAME] password [PASSWORD]
commit
save
exit

config

set vpn l2tp remote-access authentication local-users \

username [USERNAME] password [PASSWORD]

commit

save

exit

Error 850 When Connecting to Vyatta VPN With Windows 8

By leerb on January 12, 2014 in Vyatta, Windows

While setting up a Windows 8 workstation to connect to a Brocade Vyatta firewall on RackSpace Cloud, I got the following error:

Error 850: The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer.

Turns out the fix is pretty simple – on the Connections Properties -> Security tab we need to explicitly set the authentication protocols as shown in this image:

Credit goes to Brendan at SysadminSpot for providing this solution:

https://sysadminspot.com/server-administration/error-connecting-to-virtual-private-network-pptp-error-850-the-extensible-authentication-protocol-type-required-for-authentication/

Configure Vyatta To Allow Incoming MySQL Connections

By admin on November 14, 2013 in Vyatta

This article demonstrates how to configure a Vyatta firewall to allow incoming requests from a group of clients to an internal MySQL server.

Assuming that you have three external MySQL clients with IPv4 addresses:

[A:y.y.y.y]
[B:y.y.y.y]
[C:y.y.y.y]

We’ll put these addresses in a group called [clientgroup]. You can name the group appropriately for your installation.

The external address of the firewall is [x.x.x.x] and the internal address of the MySQL server is [z.z.z.z].

# enter config mode
config

# create address group
set firewall group address-group [clientgroup] address [A:y.y.y.y]
set firewall group address-group [clientgroup] address [B:y.y.y.y]
set firewall group address-group [clientgroup] address [C:y.y.y.y]

# select "untrusted" firewall - this it firewall rule set that controls
# traffic passing through the device
edit firewall name untrusted

# allow the mysql traffic from the source address group
set rule 505 action accept
set rule 505 destination port '3306'
set rule 505 protocol 'tcp'
set rule 505 source group address-group [clientgroup]

# add nat rules
set nat destination rule 15 inbound-interface eth0
set nat destination rule 15 destination address [x.x.x.x]
set nat destination rule 15 destination port mysql
set nat destination rule 15 protocol tcp
set nat destination rule 15 translation address [z.z.z.z]

# enter config mode

config

# create address group

set firewall group address-group [clientgroup] address [A:y.y.y.y]

set firewall group address-group [clientgroup] address [B:y.y.y.y]

set firewall group address-group [clientgroup] address [C:y.y.y.y]

# select "untrusted" firewall - this it firewall rule set that controls

# traffic passing through the device

edit firewall name untrusted

# allow the mysql traffic from the source address group

set rule 505 action accept

set rule 505 destination port '3306'

set rule 505 protocol 'tcp'

set rule 505 source group address-group [clientgroup]

# add nat rules

set nat destination rule 15 inbound-interface eth0

set nat destination rule 15 destination address [x.x.x.x]

set nat destination rule 15 destination port mysql

set nat destination rule 15 protocol tcp

set nat destination rule 15 translation address [z.z.z.z]

Secure Hosting On RackSpace Cloud

By leerb on August 23, 2013 in Vyatta

We’re going to build a highly secure hosting environment on RackSpace Cloud using Cloud Networks and the new Brocade Vyatta vRouter image. The diagrams shows the target configuration:

There are 4 networks:

Public – this is the RackSpace Public Cloud/Internet network. The vRouter connects via eth0 to this network with public address of 1.1.1.1

LocalPrivate – this is a private Cloud Network that connects the vRouter and the servers. This network uses the private 192.168.3.0/24 subnet.

DBPrivate – this is a private Cloud Network that connects the web and database servers. This network uses the private 192.168.4.0/24 subnet.

Service – this is RackSpaces multi-tenent management network. This network is not being used and is not shown in the diagram.

On these networks are three servers:

Brocade Vyatta vRouter – this device provides a router, firewall and VPN termination point

Web Server – provides hosting for the web application.

Database Server – provides hosting for MySQL database used by web application

The Web and Database servers are not directly connected to the Internet. Instead all traffic passes through the vRouter. The vRouter provides a stateful inspection firewall to control access. There is also a private network (DBPrivate) between the web and database server.

Part 1 – Create Networks & Servers

To get started, login to your RackSpace Cloud account.

1. Verify that your account is enable for Cloud Networks and Brocade Vyatta vRouter. Go to Servers and click the Add Server button. Look in the list of available images and find the Brocade Vyatta vRouter. If it is not listed then open a support ticket and request access. Look towards the bottom of the New Server form and find the Cloud Networks section. If you don’t see this section then open a support ticket requesting access to Cloud Networks. Once you have verified that both Cloud Networks and Brocade Vyatta vRouter are available on your account then you can proceed to the next step.

2. Create a new server using the Brocade Vyatta vRouter image. The minimum size for the server should be 1GB. You can resize up later on as needed. You can not resize down. In the Cloud Networks section at the bottom of the form, add a new network named “LocalPrivate”.

3. Create the new database server using the latest CentOS 6.x image with at least 1GB of memory. In the Cloud Networks section, create a new network named “DBPrivate”. Also add the database server to the previously created “LocalPrivate” network.

4. Create the new web server using the latest CentOS 6.x image with at least 1GB of memory. In the Cloud Networks section, add the web server to the previously created “DBPrivate” and the “LocalPrivate” networks.

Take note the root passwords and IP addresses assigned to each server as they are created.

Part 2 – Configure vRouter

Connect to the vRouter with SSH. The login will be username “vyatta” and the password set when the server was created.

Execute the following commands in order. Be careful to replace bracketted items with your actual configuration values. Most lines can be copied and pasted to the vRouter including the comments.

# enter config mode
config

# ***********************
# *** FIREWALL CONFIG ***
# ***********************

# activate stateful inspection
set firewall state-policy established action 'accept'
set firewall state-policy related action 'accept'

# global firewall rules
set firewall all-ping 'enable'
set firewall broadcast-ping 'disable'
set firewall ipv6-receive-redirects 'disable'
set firewall ipv6-src-route 'disable'
set firewall ip-src-route 'disable'
set firewall log-martians 'enable'
set firewall receive-redirects 'disable'
set firewall send-redirects 'enable'
set firewall source-validation 'disable'
set firewall syn-cookies 'enable'

# Create new firewall named 'protect-vyatta' that will be applied 
# to local traffic destined for the vRouter.
edit firewall name protect-vyatta

# drop all by default
set default-action 'drop'

# allow IKE and ESP for IPsec
set rule 100 action 'accept'
set rule 100 destination port '500'
set rule 100 protocol 'udp'
set rule 200 action 'accept'
set rule 200 protocol 'esp'

# allow LT2P over IPsec
set rule 210 action 'accept'
set rule 210 destination port '1701'
set rule 210 ipsec 'match-ipsec'
set rule 210 protocol 'udp'

# NAT traversal
set rule 250 action 'accept'
set rule 250 destination port '4500'
set rule 250 protocol 'udp'

# deter SSH brute force
set rule 300 action 'drop'
set rule 300 destination port '22'
set rule 300 protocol 'tcp'
set rule 300 recent count '3'
set rule 300 recent time '30'
set rule 300 state new 'enable'

# Allow SSL to vRouter
# You might also want to add source IP restrictions to this rule.
set rule 310 action 'accept'
set rule 310 destination port '22'
set rule 310 protocol 'tcp'

# Allow HTTPS to vRouter web interface
# Consider adding source IP restrictions or leaving this rule
# out completely if you're not going to use the web interface.
set rule 502 action 'accept'
set rule 502 destination port '443'
set rule 502 protocol 'tcp'

# allow icmp
set rule 900 action 'accept'
set rule 900 description 'allow icmp'
set rule 900 protocol 'icmp'

# return to base config level
exit

# assign local firewall to interface
set interfaces ethernet eth0 firewall local name 'protect-vyatta'

# setup firewall for public interface
set firewall name untrusted default-action 'drop'
set firewall name untrusted description 'deny traffic from internet'

edit firewall name untrusted

# allow http to web server
# needed in conjunction with destination NAT rules
set rule 502 action 'accept'
set rule 502 destination port '80'
set rule 502 protocol 'tcp'
exit

# Assign 'untrusted' firewall to incoming packets on eth0
set interfaces ethernet eth0 firewall in name 'untrusted'

# ******************
# *** NAT CONFIG ***
# ******************

# Masquerade private network behind public interface
# Replace [y.y.y.y] with network address of 
# LocalPrivate (192.168.0.3 in this example)
set nat source rule 10 outbound-interface 'eth0'
set nat source rule 10 protocol 'all'
set nat source rule 10 source address '[y.y.y.y]/24'
set nat source rule 10 translation address 'masquerade'

# Destination NAT for external port 80 to internal web server
# Replace [x.x.x.x] with the public address of the vRouter
# Replace [z.z.z.z] with LocalPrivate address of web 
# server (192.168.3.3 in this example)
# Add rules as necessary for additional ports.
set nat destination rule 10 inbound-interface eth0
set nat destination rule 10 destination address [x.x.x.x]
set nat destination rule 10 destination port http
set nat destination rule 10 protocol tcp
set nat destination rule 10 translation address [z.z.z.z]

# ******************
# *** VPN CONFIG ***
# ******************

# assign ipsec to eth0
set vpn ipsec ipsec-interfaces interface eth0

# turn on nat traversal on all networks
set vpn ipsec nat-traversal enable
set vpn ipsec nat-networks allowed-network 0.0.0.0/0

# Replace [x.x.x.x] with the public address of the vRouter
set vpn l2tp remote-access outside-address [x.x.x.x]

# We draw addresses for VPN clients from the LocalPrivate subnet. This allows 
# VPN clients to do split tunneling without adding static routes
set vpn l2tp remote-access client-ip-pool start 192.168.3.100
set vpn l2tp remote-access client-ip-pool stop 192.168.3.200

# Replace [PRESHARED SECRET] with your own preshared secret
set vpn l2tp remote-access ipsec-settings authentication \
   mode pre-shared-secret
set vpn l2tp remote-access ipsec-settings authentication \
   pre-shared-secret [PRESHARED SECRET]

# Users will be authenticated against a local database stored on the vRouter.
set vpn l2tp remote-access authentication mode local

# Replace [USERNAME] and [PASSWORD] with the username/password for your 
# first remote user. Repeat to add additional users.
set vpn l2tp remote-access authentication local-users \
   username [USERNAME] password [PASSWORD]

# commit and save changes
commit
save

# return to operational mode
exit

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

# enter config mode

config

# ***********************

# *** FIREWALL CONFIG ***

# ***********************

# activate stateful inspection

set firewall state-policy established action 'accept'

set firewall state-policy related action 'accept'

# global firewall rules

set firewall all-ping 'enable'

set firewall broadcast-ping 'disable'

set firewall ipv6-receive-redirects 'disable'

set firewall ipv6-src-route 'disable'

set firewall ip-src-route 'disable'

set firewall log-martians 'enable'

set firewall receive-redirects 'disable'

set firewall send-redirects 'enable'

set firewall source-validation 'disable'

set firewall syn-cookies 'enable'

# Create new firewall named 'protect-vyatta' that will be applied

# to local traffic destined for the vRouter.

edit firewall name protect-vyatta

# drop all by default

set default-action 'drop'

# allow IKE and ESP for IPsec

set rule 100 action 'accept'

set rule 100 destination port '500'

set rule 100 protocol 'udp'

set rule 200 action 'accept'

set rule 200 protocol 'esp'

# allow LT2P over IPsec

set rule 210 action 'accept'

set rule 210 destination port '1701'

set rule 210 ipsec 'match-ipsec'

set rule 210 protocol 'udp'

# NAT traversal

set rule 250 action 'accept'

set rule 250 destination port '4500'

set rule 250 protocol 'udp'

# deter SSH brute force

set rule 300 action 'drop'

set rule 300 destination port '22'

set rule 300 protocol 'tcp'

set rule 300 recent count '3'

set rule 300 recent time '30'

set rule 300 state new 'enable'

# Allow SSL to vRouter

# You might also want to add source IP restrictions to this rule.

set rule 310 action 'accept'

set rule 310 destination port '22'

set rule 310 protocol 'tcp'

# Allow HTTPS to vRouter web interface

# Consider adding source IP restrictions or leaving this rule

# out completely if you're not going to use the web interface.

set rule 502 action 'accept'

set rule 502 destination port '443'

set rule 502 protocol 'tcp'

# allow icmp

set rule 900 action 'accept'

set rule 900 description 'allow icmp'

set rule 900 protocol 'icmp'

# return to base config level

exit

# assign local firewall to interface

set interfaces ethernet eth0 firewall local name 'protect-vyatta'

# setup firewall for public interface

set firewall name untrusted default-action 'drop'

set firewall name untrusted description 'deny traffic from internet'

edit firewall name untrusted

# allow http to web server

# needed in conjunction with destination NAT rules

set rule 502 action 'accept'

set rule 502 destination port '80'

set rule 502 protocol 'tcp'

exit

# Assign 'untrusted' firewall to incoming packets on eth0

set interfaces ethernet eth0 firewall in name 'untrusted'

# ******************

# *** NAT CONFIG ***

# ******************

# Masquerade private network behind public interface

# Replace [y.y.y.y] with network address of

# LocalPrivate (192.168.0.3 in this example)

set nat source rule 10 outbound-interface 'eth0'

set nat source rule 10 protocol 'all'

set nat source rule 10 source address '[y.y.y.y]/24'

set nat source rule 10 translation address 'masquerade'

# Destination NAT for external port 80 to internal web server

# Replace [x.x.x.x] with the public address of the vRouter

# Replace [z.z.z.z] with LocalPrivate address of web

# server (192.168.3.3 in this example)

# Add rules as necessary for additional ports.

set nat destination rule 10 inbound-interface eth0

set nat destination rule 10 destination address [x.x.x.x]

set nat destination rule 10 destination port http

set nat destination rule 10 protocol tcp

set nat destination rule 10 translation address [z.z.z.z]

# ******************

# *** VPN CONFIG ***

# ******************

# assign ipsec to eth0

set vpn ipsec ipsec-interfaces interface eth0

# turn on nat traversal on all networks

set vpn ipsec nat-traversal enable

set vpn ipsec nat-networks allowed-network 0.0.0.0/0

# Replace [x.x.x.x] with the public address of the vRouter

set vpn l2tp remote-access outside-address [x.x.x.x]

# We draw addresses for VPN clients from the LocalPrivate subnet. This allows

# VPN clients to do split tunneling without adding static routes

set vpn l2tp remote-access client-ip-pool start 192.168.3.100

set vpn l2tp remote-access client-ip-pool stop 192.168.3.200

# Replace [PRESHARED SECRET] with your own preshared secret

set vpn l2tp remote-access ipsec-settings authentication \

mode pre-shared-secret

set vpn l2tp remote-access ipsec-settings authentication \

pre-shared-secret [PRESHARED SECRET]

# Users will be authenticated against a local database stored on the vRouter.

set vpn l2tp remote-access authentication mode local

# Replace [USERNAME] and [PASSWORD] with the username/password for your

# first remote user. Repeat to add additional users.

set vpn l2tp remote-access authentication local-users \

username [USERNAME] password [PASSWORD]

# commit and save changes

commit

save

# return to operational mode

exit

Part 3 – Configure VPN Client

Next you can configure a client workstation. Here’s the procedure to configure a Windows client to connect to the VPN:

http://blogs.reliablepenguin.com/2013/08/22/windows-l2tpipsec-client-config

These instructions include an optional step to enable split tunneling. You’ll most likely want to complete this step so that only traffic for the secure hosts is routed on the VPN.

Part 4 – Configure Web Server

Initially the web server will not have a viable default gateway so it will not be accessible from the Internet or the VPN. So you’ll need to SSH to the vRouter and then SSH again into the web server. Open an SSH terminal to the vRouter and login as user “vyatta”. Now ssh from here to the web server:

ssh -l root 192.168.3.3

1	ssh -l root 192.168.3.3

We need to set a default gateway pointing to the vRouter. So edit /etc/sysconfig/network-scripts-ifcfg-eth2 and add this line to the bottom:

GATEWAY=192.168.3.1

1	GATEWAY=192.168.3.1

If you addresses or interfaces are numbered differently then you’ll need to adjust accordingly. The key issue is that the webserver needs to point to the internal LocalPrivate interface on the vRouter for it’s default gateway in order to route to the Internet.

Part 5 – Configure Database Server

We need to set a default gateway pointing to the vRouter. So edit /etc/sysconfig/network-scripts-ifcfg-eth1 and add this line to the bottom:

GATEWAY=192.168.3.1

1	GATEWAY=192.168.3.1

If you addresses or interfaces are numbered differently then you’ll need to adjust accordingly. The key issue is that the database server needs to point to the internal LocalPrivate interface on the vRouter for it’s default gateway in order to route to the Internet.

Notes

For database access from the webserver, make sure you use the DBPrivate network. I like to add an entry to the /etc/hosts file on the webserver that maps a name to the correct address on the database server like this:

192.168.4.1 db01

1

192.168.4.1 db01

References

Windows L2TP/IPSec Client Config

By leerb on August 22, 2013 in Vyatta, Windows

Here’s the procedure to configure a Windows client to connect to a L2TP/IPsec VPN server. You’ll need to know:

VPN Server Address
IPSec Pre-shared Secret
Username
Password

To get started:

1. Open the “Start” menu, enter “setup a vpn” in the search box and hit Enter. The “Create a VPN connection” dialog will open. You can also get to this dialog by going to:

Start -> Control Panel -> Network and Sharing Center -> “Setup a new connection or network” -> “Connect to a workplace” -> Next -> “Use my Internet connection (VPN)”

2. Enter the VPN Server Address in the “Internet Address” field. Enter a name for the VPN connection like “My VPN” in the “Destination Name” field. Click the “Don’t connect now…” checkbox. Click the Next button.

3. Enter the username and password. Click the Create button. Click the Close button.

4. Open the network connections dialog by clicking the network icon among the status icons in the tool bar or by going to:

Start -> Control Panel -> Network and Sharing Center -> “Connect or disconnect”

You should see your newly created VPN connection listed by the name that you gave it.

Right click on the connection and select Properties. The Properties dialog will open.

4. Go to the Security tab and change VPN Type to “Layer 2 Tunneling Protocol with IPsec (L2TP/IPSec)”.

Click the “Advanced Settings” button. Select “Use preshared key for authentication” and enter your Pre-shared Secret. Click the OK button.

5. OPTIONAL – If you want to allow split routing then select the Networking tab. Now select “Internet Protocol Version 4 (TCP/IPv4)” and click the Properties button. Click the Advanced button. Uncheck the “Use default gateway on remote network” checkbox and click OK. Click OK.

6. Click Ok to save modified properties.

Setup is now complete. You can start the connection from the network connections dialog which can be reach by clicking on the network status icon in the toolbar or by going to:

Start -> Control Panel -> Network and Sharing Center -> “Connect or disconnect”

Select the connection and then click on the Connect button.

Later you can disconnect by repeating the process and clicking the Disconnect button.

Need help immediately?

$100/hour
Satisfaction Guaranteed

Top Nav

Navigation

Archive | Vyatta

Vyatta VPN User Management

Add New User

Remove A User

Change User Password

Error 850 When Connecting to Vyatta VPN With Windows 8

Configure Vyatta To Allow Incoming MySQL Connections

Secure Hosting On RackSpace Cloud

Part 1 – Create Networks & Servers

Part 2 – Configure vRouter

Part 3 – Configure VPN Client

Part 4 – Configure Web Server

Part 5 – Configure Database Server

Notes

References

Windows L2TP/IPSec Client Config