I'm trying to create a HTTP 1/1 compliant date header using standard unix date(1) in order to post this to a RESTful server using curl or similar.
Any ideas what format to pass to date(1) to get this to be RFC 1123 compliant?
Many thanks
I have 2 networks
HOSTED: 10.0.1.0/24 (hosted server infrastructure (web-apps, databases, etc))
OFFICE: 10.0.2.0/24 (office infrastructure (file & print, databases))
Each has an ubuntu (NAT+Proxy) based firewall at 10.0.[12].1. (10.04 LTS server).
Each firewall has a second interface to the Internet (Internet-routable static IP presented on a standard ethernet interface).
Server infrastructure on both HOSTED and OFFICE is VMware ESXi-based.
Networks are not heavily used - it's a 35-person company, so we're not needing a full, enterprise-class solution here.
Workstations are MacOSX, Windows, Linux, and Windows VPN clients, in particular, need to be idiot-proof.
I want do the following:
Connect both these networks together over a VPN (routed rather than bridged, I guess(?)) such that all hosts in the HOSTED and OFFICE networks can readily communicate with hosts on the other network (N2N VPN) regardless of where the connection was initiated from.
Provide generic VPN services to mobile users such that these users can access both the HOSTED and OFFICE network once their VPN clients have logged in. (CLIENT-VPN).
Question: Using free or cheap technologies, how should I best set this up? My thoughts so far have been:
- OpenVPN VMWare images, one on each network - this looks affordable and looks impressive, but seems to be CLIENT-VPN centric, rather than N2N centric. Also, it looks as if the VPN software needs to run on my firewall hosts in order to do the N2N VPN. I'm not keen to replace my firewalls with these OpenVPN virtual machines.
- Hand-roll only the N2N VPN (how?) on my existing firewall machines, and then deploy the OpenVPN VMware image on my OFFICE network behind my current firewall, and have this manage only the CLIENT VPN traffic (via port forwarding on the OFFICE firewall).
- Use DD-WRT or similar?
I don't have a view on the relative benefits of PPTP, IPSec, SSL-VPN although I think the latter is probably best (gut-feel). I don't run WINS or anything other than IP on the networks, so I don't think bridging is needed. I will probably set up some kind of split-brain DNS infrastructure on the 2 networks to provide name services on the 10.x.x.x networks.
I'd welcome any suggestions on network architecture, VPN platform selection and solution design.
Thanks
Simple question -- I'm trying to run a slave DNS server on zoneedit.com, with a primary serving runnning on my own bind9 instance on an Ubuntu server.
Zoneedit does not provide any support/how-to docs for configuring their servers as slaves to mine.
I'm interested in hand-rolling a SAN solution on Linux with the following technologies:
- iscsi
- mdadm raid
- lvm
- multipath
- xfs/gfs/???
- teamed NICs
Hardware-wise, I'm thinking of 2 x gigE (or better) switches with multiple gigE NICs on both the targets and the initiators.
What recommendations do people have on how to configure this, ideally, on the presumption of full n+1 (min) redundancy?
Also, do I need a set of aggregator hosts in the middle of the iSCSI "fabric"? Something like this:
targets (with mdadm) <-gigE-> aggregator host (lvm) <-gigE-> initiators
or is it better to do something like this:
targets (no mirroring) <-gigE-> aggregator host (mdadm) <-gigE-> initiators (lvm)
There are many ways to design this and I'd be interested in what experience others may have had in doing something similar?
The SAN will be used for VMware images and generic file services (plus a few databases, if viable).