OpenConnect VPN & SSH

Recently got into a requirement where in I need to connect to cisco VPN using anyconnect to access our client environment.
OSS already has a replacement for Cisco Anyconnect in the form of OpenConnect.

We were able connect to client environment by below

# sudo openconnect <client gateway>

However after successful connection establishment, there were connectivity issues like no response to the packets sent by ssh, http, etc. The problem is eradicated now by reducing the MTU for the  network interface from 1500 to 768.

# ip li set mtu 768 dev enp0s3

Advertisements

Leave a comment

WhatsApp Theme – Ubuntu Colors

New theme for my gbwhatsapp

2016-05-17-05-18-18

2016-05-17-05-23-00

Download:

Ubuntu-colors

,

Leave a comment

Connectify Dispatch – Short review

I have been into frequent intermittent internet disconnection and in the recent days the connection reliability has gone far down. I do have few standby network connections in the form of USB data card and a 3G connection.

I heard about this product long time ago but did not care to install or try that time. Now the unstable connectivity forced me to try this option. The product has 2 utilities, 1-  hotspot which can create a soft wifi out of your  available internet connections and share them across your surroundings 2- the dispatch which allows to dynamically aggregate the available internet connections whenever they are available and also facilitate load balancing when one or the other connection drops.

In my case, the dispatch works perfect when it comes to aggregating the connection but the load balancing as promised is not instantaneous and it takes a while to transfer all the ongoing socket connections to the functioning sockets.

The aggregation is very much beneficial for download and torrents but not a right option for video streaming or gaming. Also some network adapters are not discovered by the dispatch software which is another factor that the software need to address. Another issue was the DNS routing that the requests are not routed properly all the time. This would be very good package only if it could fix the few niggles here and there otherwise a good product for download buffs.

Overall it does the work but not practical for my use.

Leave a comment

A Solution to Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE

Ever since I upgraded to Windows 8.1, the system started misbehaving on hibernation. There were many proposed workaround and fixes but most of them do not work on all cases. I started with analyzing the minidump that’s been generated every time hibernate was invoked.
The WinDBG utility gave me a clear picture of which device causing the trouble. In my case it was the onboard Realtek PCIe Gigabit Ethernet card.

Below is the crash dump analysis

*******************************************************************************
 * *
 * Bugcheck Analysis *
 * *
 *******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
 A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
 Arguments:
 Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
 Arg2: ffffe00001720060, Physical Device Object of the stack
 Arg3: fffff80159fe4cb0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
 Arg4: ffffe0000439f430, The blocked IRP
Debugging Details:
 ------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f837
MODULE_NAME: pci
FAULTING_MODULE: fffff800004e9000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF80159FE4FB0
STACK_TEXT:
 fffff801`59fe4c78 fffff801`588158d2 : 00000000`0000009f 00000000`00000003 ffffe000`01720060 fffff801`59fe4cb0 : nt!KeBugCheckEx
 fffff801`59fe4c80 fffff801`588157f2 : ffffe000`01381770 fffff780`00000014 00000000`00000000 fffff801`5869fdbc : nt!PopIrpWatchdogBugcheck+0xde
 fffff801`59fe4ce0 fffff801`5869e6e2 : 00000000`00000000 fffff801`59fe4e30 ffffe000`013817a8 ffffe000`01929c98 : nt!PopIrpWatchdog+0x32
 fffff801`59fe4d30 fffff801`5876e1d5 : 00000000`00000000 fffff801`5890c180 fffff801`58df1900 ffffd000`2a6d2000 : nt!KiRetireDpcList+0x6b2
 fffff801`59fe4fb0 fffff801`5876dfd9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`5876cea8 : nt!KxRetireDpcList+0x5
 ffffd000`275b1930 fffff801`58770245 : ffffc13a`d6ed2177 fffff801`5876cf13 00000000`00000000 00001f80`00000002 : nt!KiDispatchInterruptContinue
 ffffd000`275b1960 fffff801`5876cf13 : 00000000`00000000 00001f80`00000002 ffffd000`2a6d2000 00000000`ffffffff : nt!KiDpcInterruptBypass+0x25
 ffffd000`275b1970 fffff801`58826058 : 00000000`00000000 fffff6e8`00153688 00000000`00000103 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x173
 ffffd000`275b1b00 fffff801`58825ade : ffffd000`2a6d1000 fffffa80`009321c0 ffffd000`275b1c40 00000000`ffffffff : nt!RtlpGenericRandomPatternWorker+0x94
 ffffd000`275b1b30 fffff801`5881510e : ffffd000`2a6d1000 ffffd000`275b1c40 fffffa80`009321c0 fffffa80`009321c0 : nt!RtlScrubMemory+0x10e
 ffffd000`275b1b70 fffff801`58814fb0 : ffffd000`275b1c40 fffffa80`009321c0 ffffe000`0015ce98 fffffa80`009321d0 : nt!MiScrubPage+0x76
 ffffd000`275b1ba0 fffff801`58c19c3c : ffffe000`00000000 ffffe000`00000000 00000000`00000000 00000000`00000000 : nt!MiScrubNode+0x110
 ffffd000`275b1c20 fffff801`586573cd : fffff801`58c19bfc ffffe000`032300e0 00000000`00000000 ffffe000`02540880 : nt!MiScrubMemoryWorker+0x40
 ffffd000`275b1c90 fffff801`58702664 : ffffe000`02540040 ffffe000`02540880 ffffe000`02540880 ffffe000`001653c0 : nt!ExpWorkerThread+0x2b5
 ffffd000`275b1d40 fffff801`587716c6 : ffffd000`201d5180 ffffe000`02540880 ffffe000`02540040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
 ffffd000`275b1da0 00000000`00000000 : ffffd000`275b2000 ffffd000`275ac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_Rt630x64_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_Rt630x64_IMAGE_pci.sys

The driver upgrade didn’t resolve the issue so I had to disable the device to have successfull hibernation. This becomes quite annoying that I have to disable/enable the particular device every time to hibernate the system.

So what if this could be automated – disabling/enabling device on every hibernate and resume? Here is what I have done to get the same result.

Required Tools/Utilities:
DevmanView
Elevated Shortcut

Both are freewares and can be obtained direct from the author’s site.

  • Initially run DevmanView and get the device name that you want to disable.
  • Created a batch script containing the following code which will disable the device before the actual hibernate starts.

D:\Drivers\DevmanView-x64\DevManView.exe /disable "Realtek PCIe GBE Family Controller"
C:\Windows\System32\shutdown.exe /h

  • Create a elevated shortcut for the batch script (This is only optional but it will disable the annoying UAC prompt when you run the batch script)
  • Now create a scheduled task to enable the device back after resuming from the suspended state. (Win+Run -> “mmc” -> Add Snapin ->Task Scheduler)

Give a name for the scheduled task and add below triggers
On workstation unlock – Ignores first log on, but will start after unlock.
On connection to user session – Every log on, can be local or remote connection.
On an event – In the system log, the “Power-Troubleshooter” Source will log an event code of 1 when you wake up from a sleep state.

This has resolved my long time Win 8.1 buried issue. Please do let me know if it helps someone 🙂

Leave a comment

Veritas Cluster HA for Solaris – Test Environment Setup

Video posted on youtube by myself on configuration items to consider while setting up vcs on home/personal computers. Watch in HD full screen for clarity.

Leave a comment

Configuring Hotmail for Zimbra Desktop Client

Unlike Thunderbird (the email client which I was using before) I had to feed manual configuration for my hotmail account in the case of Zimbra Client. I posted here a screen which display the important configuration inputs that should go in.

2012-02-06_00-58-49

4 Comments

Installing or Booting Fedora 16 Live from Network(PXE)

For this project, I did setup a fog based deployment environment which is very effective in distributing OS images across network. We will use Ubuntu as the base server(fog does support fedora/rhel/centos) on which fog will run.

Upon setting up fog, any client system connected on the same network will have the scope to get network boot(tftp) image of fog which in turn will provide OS images. In this demo, we downloaded an ISO copy of fedora 16 x64 live boot image from fedora site which will be used as the source installation/live boot image for our secondary server where we are going to install the fedora operating system.

We can add as many as ISO images to the FOG boot menu but for this time, I will let the menu to have an additional single entry which allows us to boot the fedora live image. Additional boot entries(in this case we add a label Install Fedora 16) to the default fog boot menu can be performed as follows.

2012-02-05_23-52-10

2012-02-05_23-52-57

Next start the client host and set the bios boot to boot from network. At this time the client should auto detect fog boot image from dhcp request. We will  now have the new option to boot/install fedora 16.

2012-02-05_23-54-01

2012-02-05_23-54-54

2012-02-05_23-55-21

Do note that fedora 16 recommends a minimum of 768MB ram to install from live cd. There is a simple workaround to bypass this restriction. Perform changes to live install configuration file as below and start the installater /usr/sbin/liveinst.

2012-02-05_23-59-20

2012-02-06_00-01-05

2012-02-06_00-01-51

Well obviously here we have the advantage saving media’s when it comes give a try any new linux flavours or rescue cds or other bootable images. I saved atleast a few burning process in last we months, I hope many will get this on for their testing environment.

, ,

Leave a comment