juniper ssg 550m
Posted: March 23rd, 2011 | Author: micha | Filed under: it, juniper, networking, pics | Tags: juniper, network, pics, security | No Comments »sweet !
sweet !
say hello little sweet juniper 5gt for testing purposes; got her on 6.2.0r8 – not recommend by juniper but by now she runs stable 🙂
finally got it working: building a bidirectional ipsec tunnel between a juniper ssg5 and openswan@debian, both sites got static ip adresses
openswan config:
conn juniper_ssg5_01
type=tunnel
authby=secret
auth=esp
pfs=yes
rekey=yes
auto=start
keylife=8h
keyingtries=0
keyexchange=ike
ike=aes256-sha1-modp2048
esp=aes256-sha1
# Linux openswan
leftid=1.1.1.1
left=1.1.1.1 # expernal ip
leftsubnet=10.1.10.0/24
leftsourceip=10.1.10.1
# SSG 5
rightid=2.2.2.2
right=2.2.2.2 # untrust interface
rightsubnet=192.168.10.0/24
juniper screenos config / route based config
set interface "tunnel.2" zone "Untrust"
set ike p1-proposal "g14-esp-aes256-sha" preshare group14 esp aes256 sha-1 second 28800
set ike p2-proposal "g14-esp-aes256-sha" group14 esp aes256 sha-1 second 3600
set ike gateway "Gateway for 10.1.10.0/24" address 1.1.1.1 Main local-id "2.2.2.2" outgoing-interface "ethernet0/0" preshare "mysecretpsk" proposal "g14-esp-aes256-sha"
set ike gateway "Gateway for 10.1.10.0/24" nat-traversal
set ike gateway "Gateway for 10.1.10.0/24" nat-traversal udp-checksum
set ike gateway "Gateway for 10.1.10.0/24" nat-traversal keepalive-frequency 0
set ike accept-all-proposal
set ike respond-bad-spi 1
set ike ikev2 ike-sa-soft-lifetime 60
unset ike ikeid-enumeration
unset ike dos-protection
unset ipsec access-session enable
set ipsec access-session maximum 5000
set ipsec access-session upper-threshold 0
set ipsec access-session lower-threshold 0
set ipsec access-session dead-p2-sa-timeout 0
unset ipsec access-session log-error
unset ipsec access-session info-exch-connected
unset ipsec access-session use-error-log
set vpn "VPN for 10.1.10.0/24" gateway "Gateway for 10.1.10.0/24" replay tunnel idletime 0 proposal "g14-esp-aes256-sha"
set vpn "VPN for 10.1.10.0/24" id 0x3 bind interface tunnel.2
set vpn "VPN for 10.1.10.0/24" proxy-id local-ip 192.168.10.0/24 remote-ip 10.1.10.0/24 "ANY"
set policy id 34 from "Trust" to "Untrust" "Any" "10.1.10.0/24" "ANY" permit log count
thinking about the differences between ssg and srx juniper firewall devices. my main focus is on stability and usual features like VPN stuff. srx devices might deliver some more and better features (on the other hand i.e. lack of ipv6 support (but announced)); for me it seems like the ssg devices are more stable and i know that they can do what i need to do. ssg5 i.e. has been started last year, the end of life of ssg series is far away (hope so). the administration stuff (console, web) has changed completely in junOS – another reason to stay on ssg devices. anyway: i`m pretty sure in a few years junOS will be the choice …
right now i`m using a SSG550M / planning to replace several linux VPN gateways with SSG5 boxes
copied vm centos 5 machines with fixed ip settings to a different esxi server. put the machines in a vm net with an active dhcp server. the centos machines switched at boot-time to dhcp and automatically disabled the fixed ip settings. centos creates a new interface configuration file with dhcp settings. the old config file is backed. why ? the mac adress has changed ! (vmware moving). to prevent this you should probably configure the mac adresses from the old esxi system or adjust the network cfg files on centos.
traffic map after one day … one the left side my machine 🙂