Saturday, April 15, 2017

IPsec capture with decryption information

This is a capture I did from a StrongSwan net-to-net IPsec VPN I setup for testing.

Packet capture :

Phase 1 main mode - IKEv1 

Initiator cookie : 751b83775c20d140
Encryption key : d38c64bef9facf441f8ad9080e2bb157

Phase 2 quick mode 

Src IP :
Dest IP :
SPI : 0xc04af751
Encryption : AES-CBC
Encryption key : 0x7c60aad1e87addb04ce8030de87c95aa
Authentication : HMAC-SHA-1
Authentication key : 0x7d46f88c672d660d7a36d5a1a756f4e10ba6c29d

Src IP :
Dest IP :
SPI : 0xce38569e
Encryption : AES-CBC
Encryption key : 0x9b6eeff11d56d9e7e658d9b09c78d19a
Authentication : HMAC-SHA-1
Authentication key : 0x8ff0d9ff940d81198d555e3574e51a6354f9d7f6

If you want to do this your self follow the steps below to capture encryption keys from StrongSwan.

Edit /etc/sysctl.conf and uncomment "net.ipv4.ip_forward=1"  to enable routing

enter the command "ipsec up net-net" to start the IPsec tunnel

1) To get the two values to decrypt ISAKMP (IKE phase 1 and 2 )

Initiator cookie : can be found in the first pkt sent.

Edit  /etc/ipsec.conf and add debug level 4 for IKE

# /etc/ipsec.conf - strongSwan IPsec configuration file

config setup
        charondebug="ike 4,enc 4"

conn %default

conn net-net


Restart the IPsec session and check /var/log/syslog file for the encryption key

2) To get keys data to decrypt the ESP data payload enter the command "ip xfrm state". You need enter data for the two security association.

root@ubuntu-1-ipsec:/home/ruwanindika# ip xfrm state
src dst
proto esp spi 0xc39e664b reqid 1 mode tunnel
replay-window 32 flag af-unspec
auth-trunc hmac(sha1) 0x6cd0b2f0fa5a81642150b059b6333a3919426da7 96
enc cbc(aes) 0x392c130f3fc8b82c7552e12746cfcf36
anti-replay context: seq 0x0, oseq 0x1f8, bitmap 0x00000000

src dst
proto esp spi 0xc2709853 reqid 1 mode tunnel
replay-window 32 flag af-unspec
auth-trunc hmac(sha1) 0xf9f4ab8729ce3f844f5d59de64ba30b24a99ca92 96
enc cbc(aes) 0x63ce266892721d11301631c504d63979

anti-replay context: seq 0x1f8, oseq 0x0, bitmap 0xffffffff

Sunday, April 9, 2017

OSPF adjacency not forming ?

Router ID ( and router ID ( is not forming adjacency. I was thinking how to troubleshoot this.

Then I did a packet capture and saw that both routers are sending OSPF hello pkts

So why are they not forming adjacency ???  Let's look in to the hello pkts to see whether there is any obvious  difference between the hellos 

Then I corrected the configuration

R4#show running-config | section ospf
router ospf 1
 area 172 stub
 redistribute eigrp 1 subnets
 network area 172

R4#configure terminal 
Enter configuration commands, one per line.  End with CNTL/Z.
R4(config)#router  ospf 1 
R4(config-router)#no area 172 stub 
R4(config-router)#area 172 nssa 
*Apr  9 11:42:17.315: %OSPF-5-ADJCHG: Process 1, Nbr on FastEthernet0/0 from LOADING to FULL, Loading Done
*Apr  9 11:42:18.311: %SYS-5-CONFIG_I: Configured from console by console
R4#show ip ospf neighbor 

Neighbor ID     Pri   State           Dead Time   Address         Interface           1   FULL/BDR        00:00:38      FastEthernet0/0

Wednesday, April 5, 2017

Microwave oven interference

I visited this site because they were complaining about connectivity issues in a staff common area. I was sitting there looking at the spectrum analyser and someone came in and started the microwave oven. This is what I saw in the spectrum analyser.

Wednesday, March 29, 2017

Packet capture samples

Some times I want to quickly look at a sample packet capture of some protocol but its not readily available somewhere in internet to download. So I thought of making a list.

1) BGP packet capture

2) RADIUS packet capture

3) IPsec - isakmp - ESP  capture

4) Wifi 4-way handshake

5) RSTP synchronization proposal and root election -

6) OSPF-with-LSA-types-1, 3, 4 and 5 -

7) multiple spanning tree (MST) -

Monday, January 30, 2017

Aerohive HMNG API "Refreshing a Token"

based on :

1)  Using endpoint


Content-Type : application/x-www-form-urlencoded
Authorization : Basic OTU4NzY4NDE6ODY0OTM4MA4YTU3NzlkNzEwY2QwNDdjNmIxMTlkZTg=

2) [NOT recommended] Using endpoint : 


X-AH-API-CLIENT-ID : 9587841
X-AH-API-CLIENT-SECRET : 86493008a5779d710cd047c6b119de8
X-AH-API-CLIENT-REDIRECT-URI : https://apache.testneta.local