Alex/AT Blog

Patch description:

When using Apache 2.4 behind a load balancer or proxy along with mod_remoteip, it may be handy for underlying scripts or configuration to know which IP address the direct client (balancer/proxy itself) making the request has. Alas, due to mod_remoteip replacing the IP with the real client IP, this may come tricky. Adding this on balancer is also not always possible because the source IP for connection to HTTP server is not known to balancer at the moment of header mangling.

Also, sometimes it may be handy to make underlying scripts/configuration know about the IP HTTP server accepted connection at, i.e. for multihomed servers.

This small and inobtrusive patch adds two % options to RequestHeader value parser along with the existing ones:

%a - this is substituted with the connecting client IP address, and if used in combination with early option, it provides IP before mod_remoteip does its job.
%A - this is substituted with the IP address of local socket accepting the connection, it provides server IP that the connection is landing onto.

Example:

RequestHeader set X-Balancer-IP %a early
RequestHeader set X-Local-IP %A early

Download:

httpd-2.4-headers-local-remote-ip.patch

Tested against Apache 2.4.27 in production, compatible with Apache 2.4.28.

Recently I have visited Chaos Constructions 2017 demoscene party, held in Saint-Petersburg.

Knowing almost nobody from there, I was just capturing things from both the public and scenic parts of it.

It's may be not a good show for outsider, but those who like demoscene, retro PC coding and stuff should definitely visit it at least once.

Hello everyone

After a while of silence, the site is back. I will fill it with content and projects again with time.

The site is completely in English to stay international, so if you need Russian or some other translation, just use Google Translate.

This is post copied from the old blog that seems to be relevant even now. Basically, those using P400/P400i on ESXi usually hit the major issue: cciss driver provided by ESXi does not support LUNs >2Tb in size while controller itself (with newer firmwares) does. Alas, it's not only driver problem but essentially the ESXi SCSI emulation layer issue is involved and so directly patching cciss driver was impossible.

What's provided there is pair of drivers for ESXi 5.1 (both VIBs must be installed for support to work) that make hpsa driver claim the P400(i) controller and cciss driver to ignore it. Of course, you should have driver support level set to 'third-party' for this to work, effectively making your ESXi system unsupported.

These VIBs were tested for years by multiple people with ESXi 5.5 and even 6.0, and found working. Nevertheless, they are obsolete AF now and always should be used at your own risk only. I hereby propose they come without any warranties and I cannot be made liable for any data loss, broken extremities, major traffic accidents or whatever resulting from your use of this driver set. It is provided only because people still search for it and find it useful.

Download:  esxi-510-cciss-hpsa.zip