Udgivet i Skriv en kommentar

Installing a Netgear WG111 v2 USB 2.0 wireless card

>>From the docs on this page:


In the freshly unzipped Netgear WG111 software directory,
I have these files:


According to the “2. Install your Windows driver” section,
I am to concern myself with these files:


# ndiswrapper -i netwg111.inf

should create /etc/ndiswrapper/netwg111/, copy all
the necessary files, and create a configuration (.conf) file.
For me, I get this:


No .sys or .conf files to be found. Of course, the next guess
is to manually copy over the .sys files…


# modprobe ndiswrapper
# dmesg

generates this:

ndiswrapper: unsupported module, tainting kernel.
ndiswrapper version 0.8 loaded
Unknown symbol: USBD.SYS:_USBD_CreateConfigurationRequestEx@8
Unknown symbol: USBD.SYS:_USBD_ParseConfigurationDescriptorEx@28
Unknown symbol: ntoskrnl.exe:IoBuildDeviceIoControlRequest
Unknown symbol: ntoskrnl.exe:IoAllocateIrp
Unknown symbol: ntoskrnl.exe:IoFreeIrp
Unknown symbol: ntoskrnl.exe:IoCancelIrp
Unable to prepare driver

(Perhaps errors are related to the lack of a .conf file?)

According to the docs, it should, instead, read something like

ndiswrapper: unsupported module, tainting kernel.
ndiswrapper version 0.8 loaded
ndiswrapper: driver netwg111 added
wlan0: ndiswrapper ethernet device xx:xx:xx:xx:xx:xx

Udgivet i Skriv en kommentar

Setting up an SSL secured Webserver

This guide will explain how to set up a site over https. The tutorial uses a self signed key so will work well for a personal website or testing purposes. This is provided as is so proceed at your own risk and take backups!

1. Getting the required software

For an SSL encrypted web server you will need a few things. Depending on your install you may or may not have OpenSSL and mod_ssl, Apache’s interface to OpenSSL. Use yum to get them if you need them.

yum install mod_ssl openssl

Yum will either tell you they are installed or will install them for you.

2. Generate a self-signed certificate

Using OpenSSL we will generate a self-signed certificate. If you are using this on a production server you are probably likely to want a key from Trusted Certificate Authority, but if you are just using this on a personal site or for testing purposes a self-signed certificate is fine. To create the key you will need to be root so you can either su to root or use sudo in front of the commands

# Generate private key
openssl genrsa -out ca.key 1024 

# Generate CSR
openssl req -new -key ca.key -out ca.csr

# Generate Self Signed Key
openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

# Move the files to the correct locations
mv ca.crt /etc/pki/tls/certs
mv ca.key /etc/pki/tls/private/ca.key
mv ca.csr /etc/pki/tls/private/ca.csr

Then we need to update the Apache SSL configuration file

vi +/SSLCertificateFile /etc/httpd/conf.d/ssl.conf

Change the paths to match where the Key file is stored. If you’ve used the method above it will be

SSLCertificateFile /etc/pki/tls/certs/ca.crt

Then set the correct path for the Certificate Key File a few lines below. If you’ve followed the instructions above it is:

SSLCertificateKeyFile /etc/pki/tls/private/ca.key

Quit and save the file and then restart Apache

/etc/init.d/httpd restart

All being well you should now be able to connect over https to your server and see a default Centos page. As the certificate is self signed browsers will generally ask you whether you want to accept the certificate. Firefox 3 won’t let you connect at all but you can override this.

3. Setting up the virtual hosts

Just as you set VirtualHosts for http on port 80 so you do for https on port 443. A typical VirtualHost for a site on port 80 looks like this

<VirtualHost *:80>
        <Directory /var/www/vhosts/yoursite.com/httpdocs>
        AllowOverride All
        DocumentRoot /var/www/vhosts/yoursite.com/httpdocs
        ServerName yoursite.com

To add a sister site on port 443 you need to add the following at the top of your file

NameVirtualHost *:443

and then a VirtualHost record something like this:

<VirtualHost *:443>
        SSLEngine on
        SSLCertificateFile /etc/pki/tls/certs/ca.crt
        SSLCertificateKeyFile /etc/pki/tls/private/ca.key
        <Directory /var/www/vhosts/yoursite.com/httpsdocs>
        AllowOverride All
        DocumentRoot /var/www/vhosts/yoursite.com/httpsdocs
        ServerName yoursite.com

Restart Apache again using

/etc/init.d/httpd restart

4. Configuring the firewall

You should now have a site working over https using a self-signed certificate. If you can’t connect you may need to open the port on your firewall. To do this amend your iptables rules:

iptables -A INPUT -p tcp --dport 443 -j ACCEPT
/sbin/service iptables save
iptables -L -v