We was waiting for 3G version of this Android tablet,
so today I've called Toshiba presales support and they told me that unfortunatelly they will not put on the market this version (also advertised on their site).
They told me that approximatively in June they'll launch another similar product with wifi+3G connectivity, but at the moment is only an "internal" announce so the guy have no technical specs.
Stay tuned for news about.
My friend Francesco (www.flussiliberi.it) was hosted on a free service without having a domain ,so, after buying a domain name and space, ask me a way to redirect all vistors that point direct to a post or page in the old WordPress blog to the corresponding page on new site.
I don't know if exist a plugin, but with a few php lines it's possible:
<?php $url="http://www.hacksandmore.com"; if (($_GET["p"] === null) and ($_GET["page_id"] === null) and ($_GET["feed"]=== null) and ($_GET["cat"]=== null)) { $url=$url; } else { if(isset($_GET["cat"])) $url=$url."/?cat=".$_GET["cat"]; if(isset($_GET["feed"])) $url=$url."/?feed=".$_GET["feed"]; if(isset($_GET["p"])) $url=$url."/?p=".$_GET["p"]; if(isset($_GET["page_id"])) $url=$url."/?page_id=".$_GET["page_id"]; } echo" <fieldset> <h1>Site transferred, redirect in a few seconds...</h1> <h3>WP redirect by: Umberto Bernardi <a href="http://www.hacksandmore.com">www.hacksandmore.com</a></h3> </fieldset> <script type="text/javascript"><!--mce:0--></script> "; ?>
You can download the script in the right panel in Downloads section
The new Qnap nas has also NFS service onboard, so I want try to use it as "addon datastore" for my VMware infrastructure.
I know poor performance but I'll use it to keep CD/DVD images, test virtual machines an why not, backup.
First of all we have to check if our esx hosts can reach the NAS, I mean the VMKERNEL, not the management, so ssh into your ESX and try with
root@esxhost# vmkping your.nas.ip
If you get response you are done, if not you have 2 solutions:
I've added another vmkernel, because we use the first for Vmotion and I want keep this separate.
So, open VI client, from inventory view choose "Hosts and Clusters" select the first Esx host and go to "configuration tab.", select "Networking" then "Add Networking".
Using the Wizard, select VMkernel and click Next. According with your network configuration, select the VSwitch that can communicate with your NAS
Give a name, IP Address and netmask (on the same netwok of NAS) to the new interface
Click Next and finish.
Try to "vmkping" and you should see response.
Now repeat these steps for all ESX hosts you have
Instruction From QNAP to use NFS on with VMware are not correct, because ESX is able to use NFS only over TCP; unforntunatley Qnap nas use NFS over UDP.
So we have to "force" the QNAP to use TCP instead of UDP...
In the configuration page on NAS there's no way to change this; so we have to connect in SSH and edit this file:
/etc/init.d/nfs
the line to change is #132
NO_V4="-N 4 --no-udp"
Reload the NFS service
/etc/initd/nfs restart
Now through the web management we can set permission to the share we want use
I permit full access from both esx hosts to this share
So, open VI client, from inventory view choose "Hosts and Clusters" select the first Esx host and go to "configuration tab.", select "Storage" then "Add Storage".
Follow the wizard for configuration:
Select "Network File System"
Fill with ip address or name of your NAS, in the Path field put the name of the share you previously defined on the NAS
Click Next and finish.
Repeat this step with same data for all ESX hosts and you are done.
N.B.
this how to require you know what are you doing.
I'm not responsible if you destroy your production machine following my instruction.
This powerful NAS (linux core inside) have 2 NICs that you can use in various mode.
I've choose to aggregate these 2 NICs to have load balance and failover.
Through the web page go to System administration, then to network; here flag "Enable port trunking" option.
in the dropdown menu ou have to choose "IEEE 802.3ad". and apply settings.
Let's go to the cisco switch ( I have Cisco IOS, not CAT OS)
i'm assuming the two NICs are connectet to Gi1/1 and Gi1/2 (adapt to you)
interface GigabitEthernet1/1 description to NAS switchport access vlan 10 switchport mode access speed 1000 duplex full channel-protocol lacp channel-group 64 mode active end interface GigabitEthernet1/2 description to NAS switchport access vlan 10 switchport mode access speed 1000 duplex full channel-protocol lacp channel-group 64 mode active end interface Port-channel64 description Connessione NAS switchport switchport access vlan 10 switchport mode access end
With this configuration on the switch, when you disconnect one NIC you will not loose connection to the NAS even if you are transferring data.
After year working with Mailscanner installed I've decided to try another way;
So, in our servers room (after server consolidation) I had an IBM x226 configured with
I know this is too to do this job, but in future I don't know if will be sufficient.
Installed Centos 5.5 final; purged and updated; next installed postfix, postgrey, and after enable (only this time ) rpmforge repo I've installed clamav-milter.
Next I've configured postfix to act as mailgateway for our internal mailserver, and I've enabled some controls on sender, look my posfix.conf:
smtpd_recipient_restrictions = reject_invalid_hostname,
reject_non_fqdn_hostname,
reject_non_fqdn_sender,
reject_unauth_destination,
reject_unauth_pipelining,
check_sender_access hash:/etc/postfix/whitelist
reject_rbl_client zen.spamhaus.org,
reject_rbl_client dnsbl.njabl.org,
reject_unknown_recipient_domain,
reject_unverified_recipient
in "check_sender_access" I've Whitelists some sender that use blacklisted mailservers.
Now It's time to setup postgrey, so in "smtpd_recipient_restrictions" section of main.cf add this line at the end of the section:
check_policy_service inet:127.0.0.1:10025
In /etc/sysconfig/postgrey you have to set options. This is mine:
OPTIONS="--greylist-text=\"You are greylisted...try again later. \" --inet=127.0.0.1:10025 --user=postfix --group=postfix"
You can also use unix socket instead of tcp socket It's your choice.
Clamav-milter need to be configured, his configuration file is in /etc/clamav-milter.conf,
I've changed these parameter:
MilterSocket unix:/var/clamav/clmilter.socket User clamav AllowSupplementaryGroups yes ClamdSocket unix:/var/run/clamav/clamd.sock LogFile /var/log/clamav/clamav-milter.log LogSyslog yes LogFacility LOG_MAIL LogInfected Basic
To instruct postfix to use clamav-milter, add these two lines in /etc/postfix/main.cf after "smtpd_recipient_restrictions" section:
smtpd_milters = unix:/var/clamav/clmilter.socket non_smtpd_milters = unix:/var/clamav/clmilter.socket
With this settings we have no false positive, and we can catch 99 % of spam.
English
Italiano 
