From: Reading, UK
quote:1.) I would like to fix some outbound traffec to one ISP (ie. SMTP), and some traffice to another (ie. ftp).
RainConnect can do this. Within RainConnect it is possible to define a set of rules that control how traffic is handled. For example, you can fix FTP to ISP1, SMTP to ISP2, and HTTP to ISP3 then specify if ISP3 fails as well, HTTP uses ISP1.
quote:2.) If connection to one ISP is broken, I would like that all traffic would pass through another ISP automatically.
RainConnect can do this. This is what RainConnect is primarily designed to do.
quote:3.) I would also like to do some definitions for inbound traffic. I would like to access to one web server through first ISP and another Web server through the second ISP.
RainConnect can do this. RainConnect has a built in DNS engine, simply register RainConnect as the 'source of authority' for your DNS and it'll give out the necessary IP addresses when people make DNS lookup requests to your domain.
quote:4.) I would also like to have automatic failover for inbound connection automatically (ie mail could be received from anywhere without any intervention).
RainConnect can do this. Because RainConnect is in control of the DNS replies (IP addresses) it can change to another ISP if a line fails. With mail you could use MX preferences to achieve a similar effect but for A records RainConnect is the only way to do it.
quote:5.) I would like to reserve bandwith for certain traffice (ie for VPN clients there always should be 20 % of all)
RainConnect can't do this! Sorry, 4 out of 5 isn't bad. You could use RainConnect to dedicate a particular ISP line just for VPN, but it is not possible to 'shape', 'throttle' or 'guarantee' bandwidth for a protocol.