Author Archive
That’s the kind of performance we’re looking for!
by dhammans on May.14, 2010, under Cisco
N7K-CORE-02# ping 4.2.2.4
PING 4.2.2.4 (4.2.2.4): 56 data bytes
64 bytes from 4.2.2.4: icmp_seq=0 ttl=52 time=2.525 ms
64 bytes from 4.2.2.4: icmp_seq=1 ttl=52 time=1.991 ms
64 bytes from 4.2.2.4: icmp_seq=2 ttl=52 time=2.053 ms
64 bytes from 4.2.2.4: icmp_seq=3 ttl=52 time=2.138 ms
64 bytes from 4.2.2.4: icmp_seq=4 ttl=52 time=2.218 ms
— 4.2.2.4 ping statistics —
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 1.991/2.185/2.525 ms
N7K-CORE-02#
Snow Leopard on Asus
by dhammans on Nov.27, 2009, under Apple
I’ve been working on getting Snow Leopard up and running on my Core i7 system for a few days now. Given that these things aren’t exactly trivial I thought I would post up some instructions for people to accomplish this given that the Asus Rampage II Extreme motherboard isn’t very well documented on the Hackintosh websites.
Hardware
Asus Rampge II Extreme Motherboard (Intel X58 / ICH10R)
Intel Core i7 920 CPU
Corsair Dominator TR3X661600C9 6GB (3 x 2GB)
EVGA GeForce GTX 285 (also tested with GTX 260)
Seagate ST31500541AS 1.5TB SATA
Seagate ST31000528AS 1.0TB SATA
Plextor SATA DVD burner
Method
My installation method was to make an image of the Snow Leopard install DVD and restore it to an external USB hard drive. From there I installed Chameleon 2.0 RC3 (required for hard disks > 1TB) RC2 produced kernel panics on my system) and booted it as the primary hard disk. Unfortunately this requires a working Mac of some sort, be it Hackintosh or other.
(continue reading…)
Warcraft vs. Mario
by dhammans on Nov.18, 2009, under WoW
While this isn’t exactly new, it is the quintessential guide to understanding the World of Warcraft. Please visit Cracked.com to read Understanding the World of Warcraft using Super Mario Brothers. Here’s a quick quote to get you started:
The first thing you should know is that most people playing World of Warcraft are terrible at video games, especially World of Warcraft. Every Nintendo owner has encountered the following scenario: You hand over the controller to a friend and then watch them clumsily murder Mario with the same bottomless pit until he stops coming back to life. World of Warcraft is an entire society of these people.
Cisco IOS to VPN client configuration
by dhammans on Nov.15, 2009, under Cisco
I recently had the need to configure an IOS router to accept VPN connections from the Cisco VPN client. I know it’s easier to use PPTP with Windows, but I wanted a configuration that would support anything the CVPN client could run on, and to be honest I’m just not a very big fan of Microsoft. Being that Cisco is trying to force people to use Anyconnect/SSL VPN these days it’s convenient that none of their instructions on Cisco.com actually work with up to date software revisions.
aaa new-model
!
!
aaa authentication login userauthen local
aaa authorization network groupauthor local
!
!
username acme privilege 15 secret 5 .
!
crypto isakmp policy 5
encr aes
hash md5
authentication pre-share
group 2
!
crypto isakmp client configuration group cvpnclient
key acme
domain acme-labs.net
pool vpnpool
acl 110
!
!
crypto ipsec transform-set acmeset esp-3des esp-sha-hmac
!
crypto dynamic-map dynmap 10
set transform-set acmeset
!
!
crypto map acmemap client authentication list userauthen
crypto map acmemap isakmp authorization list groupauthor
crypto map acmemap client configuration address respond
crypto map acmemap 10 ipsec-isakmp dynamic dynmap
!
!
!
!
interface FastEthernet0/0
description Public Internet
ip address 1.2.3.4 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
crypto map acmemap
!
interface FastEthernet0/1
description Internal LAN
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
!
ip local pool vpnpool 192.168.50.20 192.168.50.100
ip route 0.0.0.0 0.0.0.0 1.2.3.1
!
!
ip nat inside source list 100 interface FastEthernet0/0 overload
ip nat inside source static 192.168.0.7 65.16.102.187
!
access-list 100 deny ip 192.168.0.0 0.0.0.255 192.168.50.0 0.0.0.255
access-list 100 permit ip 192.168.0.0 0.0.0.255 any
access-list 110 permit ip 192.168.0.0 0.0.0.255 192.168.50.0 0.0.0.255
!
!
end
To configure the Cisco VPN client, use the group name as defined in your config (in this case it’s cvpnclient) and the password is what you set the key to in the above config. Take a close look at access-list 100, that’s what allows this to function correctly with NAT applied. You first have to deny the packet to the tunnel endpoints in the NAT statement, so that it can go to the encryption process and traverse the tunnel. Without that first deny, your tunnel endpoints will get a packet with a source address of your public overload interface. That would be bad.
