Okay, this is kinda awesome :-), I got my geek on 🙂
My application is connecting to a cluster of external servers but my application can configure hostname but can’t configure port.
So I wanted to connect to a remote cluster using SSH tunneling, but I was unable to forward everything because the port binding to localhost (127.0.0.1) can only be used once.
Then I saw that you can use multiple loopback addresses! See this page: https://en.wikipedia.org/wiki/Loopback
Basically you can bind the portforward to 127.0.0.2, 127.0.0.3 till 127.255.255.254, that should provide enough addresses, right!? 🙂
So I can use multiple port forwards from my localhost(s) to the six remote hosts like this:
Wow, talk about a crappy post title, but I just got this working on my corporate network and was quite happy about it.
Reason for this post; Every time I start a new assignment at a (rather big) corporation, I need to follow these steps to be able to access the internet from my vm’s.
(and I keep forgetting the steps, I’m getting old..)
What we’ll use to get this working:
Cygwin : https://www.cygwin.com/
Vagrant : https://www.vagrantup.com/
Virtualbox : https://www.virtualbox.org/
Cntlm : http://cntlm.sourceforge.net/
I’m running CentOS vm’s inside Vagrant with Virtualbox provisioning on Cygwin on Windows 7. I’m running Cntlm to create a local proxy for all stuff what I’m doing through cygwin, because I don’t like putting clear text passwords in bashrc or in Win / Bash variables.
Get your corporate proxy URL (Via Google Chrome)
Use teh interwebs from your VM, practicing ninja turtle coding skillz and be instantly awesome!!1!
I’ve been struggling to get Fedora working on my new laptop (Dell XPS 13 Skylake 9350) since I got it a couple of months ago. It was quite frustrating to have a working LiveCD (LiveUSB) but my laptop kept failing to boot Fedora.
Today I’ve found the problem and the fix was easy.
After the installation the EFI boot partition contains a fedora directory
( /boot/efi/EFI/fedora ) Contents of the fedora directory:
│ └── unicode.pf2
├── shim.efi <<<< This is the one!!
The solution was to create a new Boot entry in the BIOS, this wasn’t done automatically by Fedora.
Configure the UEFI boot manager to point to the shim.efi file.
When that’s done, reboot your laptop and start using Fedora.
I encountered this error last week and it was quite a headache to find out what the source of the problem was.
I thought the BEA-010213 error and the rollback log entries meant that we had a database problem. This was a wrong assumption, there’s another storage type in weblogic domains which use transactions (or state transitions?), which are JMS queues, which live in persistent stores in the managed servers. That was the source of our problem; our persistent stores became corrupted because of storage problems. Continue reading “BEA-010213, Message-Driven EJB: MyProcessMDB's transaction was rolled back”
I’ve been quite busy this whole day with a partially complete database dump and wanted to prepare for tomorrow with some ninja bash voodoo shizzle. I’m doing a braindump here because I know I’ll have forgotten this when I wake up tomorrow 🙂
The command stated below was the first working example I’ve gotten together, please let me know if you know a neater / better solution!
The title of this post is a bit misleading. I will not outline the use of pip without internet but I will suspect most people will search for this search string, thus coming here for an alternative.
I’ve been blessed with a very thorough security officer, who decided that CLI internet access is not permitted, even using CNTLM (1)is blocked.
The easiest way to install packages is via pip, but it’s also possible to install them via the commandline.
Using the example of Django, we will first download the tarball from the Django site;
On the right side there’s a link to the latest release.
Unzip and untar the tarball and open a Prompt in that directory.
Then run the following command: python setup.py install
This post will mostly serve as a reference for future posts, the goal is to create the simplest HTTPS webserver possible, which will serve to test certificates, authentication via private keys and in the end; configure SSL offloading to an Apache HTTPD, which will act as a proxy between your client and the secure endpoint. GOAL: At the end of this article, you will have a running secure web server which you can access via your web browser and/or via an SSL client. Continue reading “Create a simple HTTPS server with OPENSSL S_SERVER”