16
General Discussion / Re: Wanos hosting companies/partners?
« on: July 08, 2017, 11:05:03 AM »
What Faisal needs sounds like a desktop mobile client like the riverbed steelhead mobile client
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
17
Configuration / Re: [v.4 MultiSite] Where to add peers?
« on: July 07, 2017, 08:49:46 PM »
FEC, TCP Acceleration, PLR sounds like what you need so v.4 is probably the way to go
18
Configuration / Re: [4.0.3] Datastore on KVM /dev/vda3 not showing in panel
« on: July 07, 2017, 08:39:48 PM »
Lew confirmed VIRTIO drives are listed in v.4.1.2. I think that was just for you 
19
Configuration / Re: [v.4 MultiSite] Where to add peers?
« on: July 07, 2017, 08:36:39 PM »
As far as I know there are no UI changes from v.4 to v.4.1.1
BTW Why don't you use the Production images?
BTW Why don't you use the Production images?
20
General Discussion / Re: Wanos hosting companies/partners?
« on: July 07, 2017, 08:34:24 PM »
Why don't you use the Amazon image?
21
Configuration / Re: [v.4 MultiSite] Where to add peers?
« on: July 06, 2017, 11:59:26 AM »
Worth pointing out that if peers can't be detected on default settings and just IP changes, then there is something wrong with the way the traffic flows or a firewall is stripping tcp options. In this case forcing peering will lead to another issue, traffic will be passed through. Take a look at the Peer Down doc, it has some tips on what normally leads to the peers not showing up or showing down
22
General Discussion / Re: Home network benefit?
« on: June 29, 2017, 10:20:26 AM »
Depending on link conditions (latency+loss), Packet Loss Recovery & TCP Acceleration is expected to improve throughput in this scenario. Probably some ports like 443 will need to be removed from bypass groups to benefit HTTPS Internet traffic.
23
Features / Re: Peer Detect
« on: May 12, 2017, 09:05:09 AM »
Router mode is not supported in Express.
Read the section in the admin guide about RDP:
http://wanos.co/docs/docs/frequently-asked-questions/remove-encrypted-protocols-from-interactive-bypass-group/
Read the section in the admin guide about RDP:
http://wanos.co/docs/docs/frequently-asked-questions/remove-encrypted-protocols-from-interactive-bypass-group/
24
Features / Re: Peer Detect
« on: May 10, 2017, 08:49:44 AM »
In my experience this is the same behaviour as the riverbed steelhead RiOS
(config) # tcp connection send pass-reset source-addr 1.2.3.4 source-port 45344 dest-addr 9.8.7.6 dest-port 445
Silver Peak is the same as well. When testing in the lab the TCP sessions needs to be resetted when enabling Boost.
(config) # tcp connection send pass-reset source-addr 1.2.3.4 source-port 45344 dest-addr 9.8.7.6 dest-port 445
Silver Peak is the same as well. When testing in the lab the TCP sessions needs to be resetted when enabling Boost.
25
General Discussion / Re: Very high latency link
« on: May 07, 2017, 12:21:14 PM »
In tests with TCP Acceleration disabled/enabled over 900Kbps, 800ms satellite link:
a. 100%[==============================>] 28,409,880 52.8KB/s in 10m 10s
b. 100%[==============================>] 28,409,880 100KB/s in 5m 47s
With all optimizations disabled, then testing with moderately contested bandwidth load and congestion, with only TCP Acceleration enabled, test time were consistently better up to 50%.
Since we know TCP Acceleration helps in Long Fat Networks, the objective of this test was to see what TCP Acceleration benefits are provided in congested, long *thin* links for example to reach max link bandwidth quicker and recover faster after congestion events.
a. 100%[==============================>] 28,409,880 52.8KB/s in 10m 10s
b. 100%[==============================>] 28,409,880 100KB/s in 5m 47s
With all optimizations disabled, then testing with moderately contested bandwidth load and congestion, with only TCP Acceleration enabled, test time were consistently better up to 50%.
Since we know TCP Acceleration helps in Long Fat Networks, the objective of this test was to see what TCP Acceleration benefits are provided in congested, long *thin* links for example to reach max link bandwidth quicker and recover faster after congestion events.
26
Deployment / Re: How to Deploy WANOS on AWS
« on: May 07, 2017, 11:55:28 AM »
Hi
I'd like to add some additional info as discovered:
Elastic IP is only required when direct tunnels are used over public internet.
Elastic IP is not required when peering on private address e.g. over IPsec handled by routers
To tunnel traffic over Wanos out to the Internet e.g. for Office 365 acceleration, then the router in the VPC needs to NAT the traffic out
I'd like to add some additional info as discovered:
Elastic IP is only required when direct tunnels are used over public internet.
Elastic IP is not required when peering on private address e.g. over IPsec handled by routers
To tunnel traffic over Wanos out to the Internet e.g. for Office 365 acceleration, then the router in the VPC needs to NAT the traffic out
Pages: 1 [2]