In the Windows world, I configure putty to log all of my sessions for a variety of reasons. When on a linux client, Putty isn’t a decent solution anymore, so I started exploring how to replicate this functionality. Google indicated the “script” command is what I was looking for. However, the script command by itself would require quite a bit of extra typing to pass the ssh command and the log directory.
Windows will happily IPv6 address with static, dhcp, and SLAAC at the same time (not to mention all of the transition techs). To control this behavior, there are two netsh commands for managing SLAAC and DHCPv6 addressing. The first will disable SLAAC addressing and the second will disable DHCPv6 addressing. Important side note, “routerdiscovery=disabled” disables learning the gateway for DHCPv6 addressing too. You have to routerdiscovery enabled for DHCPv6 to function.
Running an AD joined Samba server and trying to setup home directories for users per these instructions. https://wiki.samba.org/index.php/Setting_up_a_home_share I got the error: # net rpc rights grant "HOME\Domain Admins" SeMachineAccountPrivilege SePrintOperatorPrivilege SeAddUsersPrivilege SeDiskOperatorPrivilege SeRemoteShutdownPrivilege -Uadministrator Enter administrator's password: Failed to grant privileges for HOME\Domain Admins (NT_STATUS_ACCESS_DENIED) Which led to these instructions and a hour of searching for an answer. https://wiki.samba.org/index.php/Setup_and_configure_file_shares_with_Windows_ACLs#SeDiskOperatorPrivilege The fix is, the instructions on that second link are no longer accurate for the combination of 2012R2 and Samba4.
I am playing with a bin called Haste. Very cool, very usable. It is internal, so I don’t have a link for you. However, you can use the developers http://hastebin.com/ [haste-client](https://github.com/seejohnrun/haste-client) [haste-server](https://github.com/seejohnrun/haste-server) It was an interesting journey getting this working. It is based on node.js, something I have never worked on before. Installation started with the basics listed on the haste-server page above. It wasn’t until much later that I discovered the wiki.
I was doing a little cleanup on my webserver and started looking in to the state of TLS and forward security on my site. Between the Calomel Fx plugin and SSL Test at SSL Labs, I found quite a few shortcomings in today’s standards. The first hurdle was getting good TLS1.2 support. This meant upgrading to Apache httpd 2.4. Annoying, but not painful. After some research, I came across this article by SSL Labs for a starting point for configuring the TLS cipher list.
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 ”.
I am moving somethings around on my network and part of which was moving my existing smokeping master to a new system. ERROR: This RRD was created on another architecture Little did I know that RRD graphs are architecture specific.. Meaning, moving a rrd graph made on a 32bit system to a 64bit system doesn’t work. Seriously? Anyway. Thanks to Askar Ali Khan’s blog, I was able to do the migration.
First off, credit due where credit deserved. ipv6_twit over at ipcalypse provided most of the original insight for this. Relevant man pages. http://manpages.ubuntu.com/manpages/lucid/man5/dhcp6c.conf.5.html http://www.huge-man-linux.net/man5/radvd.conf.html Building on the material by ipv6_twit over at ipcalypse, here is an example of DHCPv6-PD for multiple subnets. Basics: eth0 is WAN/upstream eth1 is LAN eth2 is WLAN eth3 is DMZ The ISP offers addresses for the ptp link from 2001:db8:88:100::/64 The ISP offers /48 delegations out of 2001:db8:ff00::/40.
Last weekend, I purchased a Samsung Series 5 all-in-one PC which happened to be running Window 8. Up till that point, my experience with Windows 8 had been dissatisfying, but I was willing to give it a go on a proper touch screen device that it is touted to be great for. In my first week of using it, I have concluded that it is OK for a touch screen device, but there is no way in hell I would use it on a keyboard+mouse only system.