I was getting a sporadic error with SSO signon to the vCSA Web Client. The error was "The authentication server returned an unexpected error: ns0:RequestFailed: Operations error. The error may be caused by a malfunctioning identity source." When viewing users for the domain in the SSO configuration on the vCSA Web user interface, I would get this error. "Error: Idm client exception: Operations error" Another symptom of the issue was nslookup was pausing when returning the results of a “nslookup ”.
Because I can never leave well enough alone, I have bricked yet another device and had to spend a few hours figuring out how to recover it. This time around was a Bufflo WZR-HP-AG300H. It is what I am hoping will be a wireless router to replace my aging WRT54GL. So the AG300H comes with 2 firmware choices. A rebranded DD-WRT labeled “Professional” and a Buffalo some-such-junk labeled “Friendly”. The device ships with the Pro firmware.
Being consistent with my preferences in life, this is not a simple task. At least, figuring it out was not a plug-and-play activity we are all used to in the VMWare world of virtualization. I want: A KVM Windows Server 2008 R2 guest installed on an LVM logical volume utilizing the VirtIO drivers for storage. The LVM portion was pretty straight forward. Create an LVM out of the free space in my PV.
Firewalls are only capable of reading header information and limiting packets based on source/desitnation qualities. This allows for abuse by running any service on any port. While not much of a problem with IPv4 since there are strict rules for public address assignments, it will become a reality with IPv6. When every user is issued a /64 of their own, they can assign as many public IPs to a device as they need/want.
In the WiFi setup I discussed in my previous post, I use DD-WRT as the OS of choice. With that choice, I was looking for a tool to help build iptables rules to make my life easier. In my search for a tool I came across by the name of fwbuilder from fwbuilder.org. The latest version is 4.0. The goal of the of fwbuilder is to manage your firewall rules faster through the use and reuse of objects and a nice GUI.
A few weeks ago, the owner of my favorite bar asked me about setting up free WiFi. Being a geek and a fan of beer, I told him I would look into it. The requirements were: Free WiFi, ~$300 budget, prevent leeching, and isolate store network from the wireless. The existing network was a DSL Modem/Router + 8 port hub. An executive decision by me to remove hub was made. Physically, the building has a LOT of brick and steel which means the AP portion could not be sitting in an office.
I have this fantastic server which redirects console output to its serial port and I wanted to take advantage of it. I went through the process of setting up inittab and grub to work and then I started testing the configuration. In Windows using Putty, everything worked fine. As soon as I moved the cable over to the serial port of an OSSIM box, I kept getting this error. /dev/ttyS0 is not a tty Googl’ing around returned nothing helpful which is why I am posting this here.
Lurking in the depths of the internet is a problem. A problem so large that it is going to cost billions to fix. It will effect every device connected to the internet without exception. Every cell phone, every game console, every computer, every router/modem, EVERYTHING. And it is a secret. Well, not really a secret, just not something anyone talks about. The problem is the language that the internet speaks, is running out of unique names.
Another VMWare issue I started having is Unity mode wouldn’t start. Click the button, the unity menu pops up and the VMWare window minimizes, but the unity app never displays. This is also a common problem with a very simple fix. Apparently, sometime in the past, I added a line to my /etc/vmware/config file to problem fix or enable some other feature. This line and Unity just don’t mix. The fix, per this thread and ultimately this blog post, is to remove the following line from your /etc/vmware/config file.