<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networks on technocracy</title><link>https://www.ericsimmerman.com/tags/networks/</link><description>Recent content in Networks on technocracy</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 05 Mar 2010 00:00:00 +0000</lastBuildDate><atom:link href="https://www.ericsimmerman.com/tags/networks/index.xml" rel="self" type="application/rss+xml"/><item><title>Connecting to Netscreen Series (NetScreen-5) VPN with Mac OS X (Snow Leopard)</title><link>https://www.ericsimmerman.com/blog/2010/03/05/connecting-to-netscreen-series-netscreen-5-vpn-with-mac-os-x-snow-leopard/</link><pubDate>Fri, 05 Mar 2010 00:00:00 +0000</pubDate><guid>https://www.ericsimmerman.com/blog/2010/03/05/connecting-to-netscreen-series-netscreen-5-vpn-with-mac-os-x-snow-leopard/</guid><description>&lt;div class='post'&gt;
(Followup to my &lt;a href="http://www.ericsimmerman.com/connecting_to_netscreen_series_netscreen/45/"&gt;NetScreen-5 from Ubuntu article&lt;/a&gt;) I recently struggled through the details of establishing a VPN connection from my Mac OS X desktop to a Juniper Networks Netscreen-5. Here's how I solved it. My Netscreen-5 was configured with some typical settings:Phase 1Pre-shared key "your-pre-shared-key-here"Encryption "pre-g2-aes128-sha"Phase 2 Encryption "g2-esp-3des-sha"To configure the client-side using an Ubuntu desktop, I used Racoon and KVpnc but didn't have the luxury of KVpnc on my Mac desktop so I had to manually edit my racoon.conf:&lt;div class="CodeRay"&gt; &lt;div class="code"&gt;&lt;pre&gt;log debug2;path pre_shared_key &amp;quot;/etc/racoon/psk.txt&amp;quot;;path certificate &amp;quot;/etc/racoon/certs&amp;quot;;timer{ natt_keepalive 10 sec;}remote VPN.GATEWAY{ exchange_mode aggressive; nat_traversal on; ike_frag on; peers_identifier asn1dn; proposal_check obey; my_identifier user_fqdn &amp;quot;YOUR.EMAIL.ADDRESS&amp;quot;; proposal { encryption_algorithm aes; hash_algorithm sha1; authentication_method pre_shared_key; dh_group modp1024; }}sainfo address DESKTOP.IP.ADDRESS/32 any address VPN.GATEWAY/28 any{ pfs_group modp1024; encryption_algorithm 3des; authentication_algorithm hmac_sha1; compression_algorithm deflate;}listen{ adminsock &amp;quot;/var/run/racoon.sock&amp;quot; &amp;quot;root&amp;quot; &amp;quot;operator&amp;quot; 0660;}&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description></item><item><title>Linksys WET54G bridge to Verizon FiOS ActionTec wireless access point</title><link>https://www.ericsimmerman.com/blog/2009/01/19/linksys-wet54g-bridge-to-verizon-fios-actiontec-wireless-access-point/</link><pubDate>Mon, 19 Jan 2009 00:00:00 +0000</pubDate><guid>https://www.ericsimmerman.com/blog/2009/01/19/linksys-wet54g-bridge-to-verizon-fios-actiontec-wireless-access-point/</guid><description>&lt;div class='post'&gt;
So my upgrade to Verizon FiOS included swapping my Linksys WRT54G access point for the Verizon branded ActionTec device that came with the FiOS install. This swap wasn't strictly necessary, but the ActionTec doubles as both the router and access point so I decided I might as well make use of the wireless capabilities since I have to keep it plugged in either way.The only problem I encountered was that my Linksys WRT54G bridge couldn't play nice with the ActionTec. Through trial and error I found that setting both devices to encrypt using WPA2-PSK using AES only (not the default TKIP+AES) resolved my issues.&lt;/div&gt;</description></item></channel></rss>