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.


Messages - ahenning

Pages: 1 2 [3] 4 5 ... 42
31
Yes, trial licenses for v.4 are available

32
Troubleshooting / Re: Support
« on: November 10, 2017, 12:20:29 PM »

33
Troubleshooting / Re: Support
« on: November 10, 2017, 12:17:09 PM »
More info on what Bypass (Fail-to-wire) is and how it works:
http://wanos.co/docs/docs/knowledgebase/bypass-fail-to-wire/

34
Troubleshooting / Re: Support
« on: November 10, 2017, 12:09:43 PM »
All support questions answered. Please provide the supporting info as soon as possible to ensure a quick resolution.

35
Troubleshooting / Re: Support
« on: November 10, 2017, 12:02:49 PM »
Hi Olivier,

Your support requests have been received, please kindly give us a few minutes to process them.

36
Troubleshooting / Re: Bridge Mode in Virtual Enviroment
« on: October 25, 2017, 12:47:33 PM »
http://wanos.co/docs/docs/wanos-admin-guide/installation/esxi/

Please see promiscuous mode and forged transmits. Enable on both port groups.

37
Troubleshooting / Re: Tunnel mode and HTTPS
« on: October 04, 2017, 10:03:30 AM »
Hi Kris,

Yes, no traffic policies are needed, since the default 0.0.0.0 would listen to all traffic over the tunnel and would optimize the TCP traffic that flows both ways over the tunnel.

On the 100 tunnel rules, yes, this limit can easily be increased.
One way is to edit the tunnel_policies rules directly:

1000=0.0.0.0/0,-,Default
111=11.0.0.0/8,1,Lab-3-24,10.10.3.24,
112=10.0.0.0/8,1,Lab-3-24,10.10.3.24,


That said, the result of this would be the same as setting a default rule to use Azure (Tunnel 0.0.0.0/0) and using the batch script to add the routes on the host or using Policy based routing to redirect only the interesting routes to the tunnel.

38
Troubleshooting / Re: Tunnel mode and HTTPS
« on: October 03, 2017, 10:11:48 AM »
Hi Kris,

Yes, this is a known and expected behavior:
The local subnets are tunneled to the AWS/Azure private network, so private communications works as expected.
When all traffic is sent out of the AWS/Azure side the security rules don't allow the EU private networks to use the gateway (or NAT at least).
It makes sense from the provider perspective that they don't want any remote IP to exit the VPC/Private subnets.

The quick and simple way around it is to enable TCP-X and set:
PEP_TCP_FULL_TRANSPARENT=false

Also the DNS servers needs to be reachable locally or on the Azure/AWS VPC.

The right way is probably to use a NAT Gateway and configure it to allow the EU private subnets to be NATted out the public IP.

39
Troubleshooting / Re: Tunnel mode and HTTPS
« on: September 28, 2017, 10:53:54 AM »
Hi Kris,

A couple things that stand out:
The Azure side needs a tunnel rule for the return traffic back to EU pointing to the EU local subnets.
Webcache only needs to be enabled on the EU side.
Disable Webcache completely until the whole setup works perfectly.
0.0.0.0/0 for SSL caching is definitely going to break some SSL sites.

40
Troubleshooting / Re: Tunnel mode and HTTPS
« on: September 27, 2017, 01:49:38 PM »
Hi Kris,

Some questions to help troubleshoot:

Are both sides running v.4? If on v3, then HTTPS is bypassed from the tunnel, only optimized traffic is tunneled.

Is standard HTTP working fine over the tunnel?

Does the issue exist only when the webcache is enabled and HTTPS server ip configured in the SSL servers list?


41
Hi Fernando,

Is the traffic you are expecting to see registering on the lan0/wan0 interface graphs?
This would indicate whether it is a case of  "nothing to see" rather than "not seeing" the traffic.

42
Quote
when I go to network / protocols I have graphs on both wan and lan, but seems to be a very small amount of it

That does not sound right. Even with bypass traffic, all the traffic will be graphed. E.g. a 10 Mbps bypass transfer will show 10 Mbps on the bypass and lan/wan stats. This would indicate that the traffic is not flowing over the bridge as intended.

The configs looks fine. Just check the traffic flow.

43
Hi,

It all sounds ok. What traffic policies are configured, can you attach a screenshot?

Also what protocol are you testing with?

If the traffic policy is only matching 172.0.10.0/24 and 172.0.20.0/24 and default #99 bypass, try setting UDP encapsulation and then switching the lan0/wan0 port roles. If the rest is as you say, I see no reason for TCP traffic e.g. HTTP, CIFS, FTP etc not to be optimized.

44
Installation / Re: Free Express throughput
« on: September 11, 2017, 12:01:14 PM »
We'll generate trial keys for the temporary hardware and then the free keys for the production hardware.

45
Deployment / How to deploy on Azure
« on: September 05, 2017, 07:21:27 PM »
While work is in progress to establish the Azure MarketPlace image, in the meantime for those that asked for steps to deploy on Azure, here is a comprehensive powershell guide and script. Theoretically it can be automated, but it is recommended to run each command manually, at least for the first couple of deployments.

How to deploy on Azure:
http://wanos.co/docs/docs/wanos-admin-guide/installation/microsoft-azure/

Pages: 1 2 [3] 4 5 ... 42